3 measurements spanning 4 days, net +15. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 2,999–3,018 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
11 Aug 2026, 10:42
3,016
+13
8 Aug 2026, 13:11
3,003
+2
7 Aug 2026, 16:33
3,001
first reading
Engagement
10 posts held, back to 30 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 2 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
35.7%
avg views ÷ 3,016 subscribers
Avg views / post
1,080
10 posts measured
Reaction rate
4.83%
reactions ÷ views · ER floor
Posts in window
10
of 10 held
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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 7 August 2026
Posts held
10 (30 July 2026 – 7 August 2026)
Views total
10,768
Reactions total
520
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
8 Aug 2026, 00:12 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.
What this channel posts
Video runtime
7s
Average length
7s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
520 reactions across 10 posts, in 17 distinct kinds. The most used accounts for 39.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
206
39.6%
❤
161
31.0%
👍
62
11.9%
😁
26
5.00%
🤣
14
2.69%
⚡
8
1.54%
👏
8
1.54%
😱
7
1.35%
custom 5273873368771213150
6
1.15%
custom 5323736474493930664
6
1.15%
🏆
5
0.962%
👎
4
0.769%
☃
3
0.577%
custom 5271534522855336546
1
0.192%
custom 5274079192193973972
1
0.192%
💔
1
0.192%
💩
1
0.192%
Custom emoji. 4 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.
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 10 of the 10 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 520reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 30 July 2026 to 7 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.
8 августа, суббота
🐉 08:30 Московский рынок х КМ
5️⃣ 08:45 5 вёрст
🍰 08:50 Skuratov run club
☕️ 09:00 Mild Run
✌ 09:00 Surf x Nokka
🏞️ 09:00 SHU RUN
💅 09:00 Бегаешь как девчонка
🧕🏻 09:45 Тихая сила
🏃♂➡️ 11:00 run coffee club
9 августа, воскресенье
🤩 08:00 DIE HARD
🌞 09:00 NAZARE
⚽️ 11:00 спортклуб «Рубин»
🎧 18:00 Скрэмбл х Byin club
🌀 по сотрудничеству: @rstmfm
🤩 https://startkazan.ru/
🏃️ «Двигайся – Копи – Пей!» – активный челлендж с призами.
Суть: передвигайтесь любым способом между кофейнями «Ураган Сарай», отмечайтесь в боте @Uragan_Sarai_Challenge_Bot, получайте баллы и выигрывайте призы.
Как участвовать:
1. Зарегистрируйтесь в системе SWIP по QR-коду в любой кофейне.
2. Отмечайтесь на каждой точке маршрута в этом боте (селфи на фоне таблички обязательно!).
3. Делитесь успехами в соцсетях с …
Наконец, мы арендовали стадион для проведения мероприятия, и теперь с полной уверенностью можем сообщить: ТЕМПу быть! 🔥
Встретимся на Центральном стадионе ровно через месяц, чтобы выявить лучшие эстафетные команды, а также самых быстрых участников забега на 1000 метров 🍌
Регистрацию откроем совсем скоро, а пока можно начать собирать команду, с которой выйдете на старт 🏆
Coffee run от клуба Byin Club и кафе-пекарни Скрэмбл
В это воскресенье стартуем от спортивной площадки у озера Нижний Кабан
Темп: 6:30 - 7 / км
На финише участников будут ждать диджей, витаминные шоты и фирменные закуски
[ Как это было в прошлый раз ]
💗Регистрация через спортивную платформу pulsar.club
Skuratov running club добавил ещё одну пробежку на неделе 🙌
Тестовая будничная пробежка состоится уже завтра от Московского рынка (ул. Шамиля Усманова, 1 к1) в 19:00 🔥
На набережной озера Кабан откроется новое пространство, где расположится в том числе и беговой центр 🔥
Павильон будет реализован в рамках благоустройства третьей очереди набережной озера Кабан. Открытие состоится 30 августа.
Здесь будут размещены:
🌟Кофейня
🌟Сувенирный магазин
🌟Зона для проведения мероприятий
🌟Беговой центр с удобными раздевалками, душевыми и локерами
🌟Общественный туалет
Пространство будет располо…
1 августа, суббота
🐉 08:30 Московский рынок х КМ
5️⃣ 08:45 5 вёрст
🍰 08:50 Skuratov run club
☕️ 09:00 Mild Run
✌ 09:00 Surf x Nokka
🏞️ 09:00 SHU RUN
💅 09:00 Бегаешь как девчонка
🧕🏻 09:30 Тихая сила
🏃♂➡️ 11:00 run coffee club
🧔♀️ 12:50 MRC Kazan
2 августа, воскресенье
🤩 08:00 DIE HARD
🌞 09:00 NAZARE
⚽️ 11:00 спортклуб «Рубин»
🌀 по сотрудничеству: @rstmfm
🤩 https://startkazan.ru/
Календарь татарстанских стартов за последние недели претерпел существенные изменения: два старта от Тимермен были отменены, а какие-то старты, напротив, добавились.
Перед вами отредактированная версия календаря беговых стартов на заключительный летний месяц:
🌟Карабаш Фест
🌟Атомный трейл
🌟Держись в Державино
🌟Бугульминский трейл
🌟Камский полумарафон
🌟Туган авылым трейл
Стало известно месторасположение бегового центра ВФЛА в Казани 📍
Быстровозводимое здание с раздевалками, душевыми, тренировочными залами, камерой хранения и кафе, а также тренажерами и детской площадкой появится на территории, прилегающей к жилому комплексу «УНО».
🔥42👍15❤11💩1
Showing the 10 most recent of 10 posts we hold for @startkazan. 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
Citation-graph rank — 120,238 of 1,183,361entries 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Mentions
Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
Cite this entry
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 11 August 2026 — this
entry's latest reading, not the date you are reading this.
“СТАРТ | всё о беге в Казани” (@startkazan), 3,016 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/startkazan.
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.