Channel
@kis_pas
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
34subscribers
-1 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003702294991 |
|---|---|
| Type | Channel |
| Username | @kis_pas |
| Created | Between 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/kis_pas |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 15:52 | 34 | -1 |
| 14 Aug 2026, 15:01 | 35 | first reading |
20 posts held, back to 24 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 5 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 13 August 2026 |
|---|---|
| Posts held | 20 (24 July 2026 – 13 August 2026) |
| Views total | 8,881 |
| Reactions total | 47 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Aug 2026, 15:01 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
47 reactions across 5 posts, in 6 distinct kinds. The most used accounts for 38.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 18 | 38.3% | |
| ❤ | 8 | 17.0% | |
| 🥰 | 8 | 17.0% | |
| 👍 | 6 | 12.8% | |
| 💋 | 6 | 12.8% | |
| 🤩 | 1 | 2.13% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 5 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 47reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 24 July 2026 to 13 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Решил пересмотреть нарезки голов с Лусиано Гонду и убедился в одном наблюдении. Почти во всех случаях когда Аргентинец регулярно забивал голы, он играл в два нападающих. Прям отчетливо видно, что ему удобнее находить пространство в полуфлангах. Это было и в Аргентине и в Зените, когда он провел лучший сезон в карьере играя в паре с Кассьерой. Исходя из этого, я своим дилетантским взглядом, считаю, что нам надо по…
🔥10👍6❤5
Что нам делать? Многие после матча с Ростовом пришли к консенсусу, что нам не хватает качества в атаке. Я с этим согласен и вот что предлагаю: 1) Помимо забивного напа (да да, я всё ещё в это верю и надеюсь) нам нужна еще одна настоящая звезда, по меркам РПЛ, в линию атаки, способная делать разницу (вместо ПЗ). Идеальный вариант для такого мува это тот самый Брайан Родригез из «Америки», которым мы уже интересовал…
🥰5🔥4❤3🤩1
Это ужас. После сделанных замен (все 5 за 30 минут до конца матча!!!) и так не выдающаяся игра в центре поля, была разрушена полностью, зачем нужно было убирать одновременно и Баринова и Облякова??? Почему не был заменен только восстановленный Гайич? Команда с нулевой сыгранностью еле отбилась дома от Ростова. Провальные замены Игдисамова второй матч РПЛ подряд, но сегодняшние действия даже сложно объяснимы. Вопросы.…
🔥4🥰3💋2
Как бы страшно это не звучало, но лучший у нас в первом тайме это Лусиано, даже без гола. В целом пока тяжело завязывается игра в центре, Баринов как всегда без мяча, Круг не так активен как Попович в первых 2-х матчах. Ростов хорошо обороняется, подходы возникают только когда у Глебова находится пространство или здорово играет в подыгрыше Лусиано. Сложный матч.
В целом все выглядит довольно логично, только обидно за Поповича, который прекрасно начал сезон, надеюсь выйдет во втором и усилит. А по поводу Торопа успокойтесь, до того как он не начнет серьезно ошибаться, никто его менять не будет, но чуйка подсказывает, что Бориско рано или поздно выиграет конкуренцию.
💋2
Стартовый состав на матч с «Ростовом»
💋2
Предсказуемая ротация. Будет интересно посмотреть на игру Алвеса с первых минут, да ещё и в такой хорошей компании. Ну и конечно дебют Бориско
Состав на сегодня. Ротация.
Классика…
Переход Жуана в ЦСКА может сорваться: по моей информации, турецкая сторона повысила денежные требования, и армейцы готовы выйти из переговоров 🔴🔵⚽️
Отдали абсолютно свой матч, обидно. Было стойкое ощущение, что нас накажут за растрату моментов, так и случилось.
Боже, как же прибавил Попович. И это уже не разовая история, как была в прошлом сезоне с Махачкалой, уже второй матч подряд в полном порядке. Видно, что матереет парень!
Showing the 12 most recent of 20 posts we hold for @kis_pas. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Citation-graph rank — 620,952 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 15 August 2026 — this entry's latest reading, not the date you are reading this.
“Подкат Кисляка | ЦСКА” (@kis_pas), 34 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/kis_pas.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.