Channel
@S95_Valday
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
159subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002682700964 |
|---|---|
| Type | Channel |
| Username | @S95_Valday |
| Description | Официальный канал парковых пробежек в Валдае. 🔹 В 09:00 каждую субботу бежим 5 км Бот для регистрации - @sat9am5kmbot Чат для общения - https://t.me/s95_valday_chat 💬 По возникшим вопросам обращайтесь @Spartak1589 @vkurbanova18 |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/S95_Valday |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 17:31 | 159 | no change |
| 6 Aug 2026, 18:34 | 159 | first reading |
13 posts held, back to 10 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.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 13 (10 July 2026 – 7 August 2026) |
| Views total | 659 |
| Reactions total | 83 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 17:31 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.
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
157 reactions across 13 posts, in 21 distinct kinds. The most used accounts for 16.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5255742658252415272 | 26 | 16.6% | |
| ❤ | 22 | 14.0% | |
| custom 5449523005598210324 | 21 | 13.4% | |
| custom 5305336095863485125 | 12 | 7.64% | |
| custom 5429363803500338694 | 12 | 7.64% | |
| 🎉 | 12 | 7.64% | |
| custom 5240214706504886076 | 11 | 7.01% | |
| custom 5420315771991497307 | 11 | 7.01% | |
| custom 5328190879565889580 | 6 | 3.82% | |
| custom 5294528609527015674 | 4 | 2.55% | |
| custom 5416068173889810564 | 4 | 2.55% | |
| custom 5415768256323531445 | 3 | 1.91% | |
| custom 5415796229445529713 | 3 | 1.91% | |
| custom 5294238076464277766 | 2 | 1.27% | |
| 👍 | 2 | 1.27% | |
| custom 5312315739842026755 | 1 | 0.637% | |
| custom 5323508033773391344 | 1 | 0.637% | |
| custom 5359370246190801956 | 1 | 0.637% | |
| custom 5416014521158349866 | 1 | 0.637% | |
| custom 5416027698118015118 | 1 | 0.637% | |
| 1 further kind | 1 | 0.637% |
Custom emoji. 17 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 13 of the 13 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 157reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 10 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.
План на субботу: кроссовки, свежий воздух, 5 километров счастья и наша команда С95 Валдай 💚 Традиционная пробежка в Соловьевском парке, встречаемся в 9 утра. Опоздавшие будут догонять, но лучше не рисковать 😉 До встречи 🌲
❤6custom 54495230055982103244custom 52557426582524152723
Эта арбузная суббота удалась на славу – сочная, спелая и взрывная! 🍉 Наш забег посетили аж 25 участников 🏃🏻 среди которых 12 личный рекордов, 6 человек впервые на С95, а 2 - впервые в Валдае 💚 За организацию отвечала команда из 9 волонтёров — без вас этот праздник бега просто не случился бы! ❤️ 📸 Ловите мгновения в альбоме, а результаты забега по ссылке. Это арбузное утро добавило летнего настроения, ради которого…
custom 53053360958634851256❤4🎉4custom 53123157398420267551
1 августа – Арбузный забег: заряжаемся сочным летним настроением! 🍉 Друзья, лето в самом разгаре, а это значит, что пришло время для нашей самой вкусной и освежающей традиции – Арбузного забега С95! Это не просто дистанция, а настоящий праздник, где спорт встречается с летним настроением ☀️ 🗓 Когда: 1 августа, суббота, старт в 9:00 📍 Где: живописный Соловьевский парк, наша точка сбора — у легендарной Эйфелевой башн…
custom 53053360958634851256❤3custom 52557426582524152722custom 54203157719914973071
Победители на дистанции Т80 🥳 Девушки: 🥇8506 Ксения Логашова - 09:39:17 🥈8515 Виктория Жукова - 09:41:03 🥉8520 Мария Баруцкова - 09:57:25 Поздравляем наших чемпионок с тяжелейшей гонкой! #GoldenRingUltraTrail #WeAreGRUT #RunningHeroesRussia
custom 54203157719914973074❤2👍1
Наша Мария стала 3-й в абсолюте на дистанции Т-80! От всей души поздравляем ее! Желаем, быстрого восстановления! И новых личных рекордов! 🥳
custom 54203157719914973071
Сегодняшнее утро встретило нас не просто солнцем, а настоящим зарядом бодрости – хватит на все выходные! 💚 Коротко о главном: 6 бегунов, 6 волонтеров, 1 личный рекорд и 1 прекрасный волонтёрский дебют – Настя, поздравляем тебя 🩷 За подробностями – по ссылке, за эмоциями – в альбом с фото 📸 Всем, кто был с нами, – респект. Ну а тех, кто ещё не присоединился к нам, мы очень ждём на С95 Валдай! 💚🎄
custom 52402147065048860765custom 54495230055982103245custom 52557426582524152724
Субботнее утро неизменно начинается в 9:00 в Соловьёвском парке на С95 Валдай 💚 Наберитесь красок, свежего воздуха и хорошего настроения — этого заряда хватит до самого понедельника. До встречи! 🌲
❤3custom 54203157719914973073custom 52557426582524152722
Если у parkrun система градации достижений строилась так: 10 → 25 → 50 → 100 → 250 → 500 → 1000, то в С95 мы обновили систему наград, сделав количество ступеней гораздо больше и чаще 25 → 50 → 100 → 200 → 300 → и далее с шагом 100. Мы отказались от редких наград и сделали более частую лестницу достижений. Участникам и волонтёрам теперь почти всегда видна следующая достижимая цель.
custom 54160681738898105644custom 54157682563235314453custom 54157962294455297133custom 54160145211583498661custom 54160276981180151181custom 54160553233476604291
Вчерашнее утро выдалось очень спортивным, энергичным и позитивным 💚 Делимся итогами: 🟢14 участников забега, 🟢6 волонтёров, 🟢8 личных рекордов, 🟢2 человека впервые на забеге С95. Результаты по ссылке 🌐 Фотографии – в альбоме 📸 Спасибо каждому, кто был с нами! Ждём вас всегда на С95 Валдай 💚🌲
custom 54495230055982103243custom 52402147065048860762custom 52557426582524152722
Отныне влюблены в С95 Люблино! Летний Забег Маяков состоялся. ✨ 497 участников и почти 90 волонтёров в Москве. Передаём луч света в Иваново, Пензу, Великий Новгород, Саранск и Гатчину. Продолжаем светить вместе!
custom 53281908795658895806custom 52557426582524152724custom 52945286095270156744
Кто не едет на Забег Маяков, приходите к нам на С95 Валдай 💚 В эту субботу, 18 июля, ждём вас в Соловьевском парке в 9 утра 🌲 Ждём каждого, кто хочет присоединиться к нам!
🎉8custom 54495230055982103246custom 52557426582524152725custom 52402147065048860763custom 52942380764642777662custom 53593702461908019561custom 54203157719914973071
Благотворительный забег «Ушки на макушке» прошел 🐶 Делимся итогами: 🟢 10 участников и 5 волонтеров собрались в парке; 🟢 2 личных рекорда; 🟢 2 человека впервые на забегах С95. И несколько десятков довольных хвостиков 🐕 Передали волонтерам Ушек полный набор – крупы, мясо и ветошь для подстилок. Результаты по ссылке 🌐 📸 Больше фотографий в альбоме. Если тоже хотите помочь, но не смогли прийти – реквизиты прилагаем 👇…
custom 54293638035003386947custom 52557426582524152724custom 54495230055982103243❤1custom 54203157719914973071
Showing the 12 most recent of 13 posts we hold for @S95_Valday. 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 — 686,682 of 1,549,376entries 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.
Named by 2 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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“С95 Валдай — парковые пробежки” (@S95_Valday), 159 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/S95_Valday.
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.