Telegram RegisterThe public register of Telegram
Telegram profile photo for Бегом по Золотому кольцу

Channel

Бегом по Золотому кольцу

@goldenring_run

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

8,936subscribers

+138 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001712191098
TypeChannel
Username@goldenring_run
Created12 November 2021measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live9 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/goldenring_run

Growth

8,7938,9368,864.56 August 2026 — 8,798 subscribers7 August 2026 — 8,793 subscribers10 August 2026 — 8,824 subscribers13 August 2026 — 8,827 subscribers16 August 2026 — 8,830 subscribers19 August 2026 — 8,820 subscribers22 August 2026 — 8,830 subscribers25 August 2026 — 8,852 subscribers28 August 2026 — 8,876 subscribers31 August 2026 — 8,883 subscribers4 September 2026 — 8,905 subscribers9 September 2026 — 8,936 subscribers6 August 20269 September 2026
12 measurements spanning 34 days, net +138. 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 8,772–8,957 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 17:218,936+31
4 Sept 2026, 10:378,905+22
31 Aug 2026, 19:288,883+7
28 Aug 2026, 12:028,876+24
25 Aug 2026, 09:488,852+22
22 Aug 2026, 20:268,830+10
19 Aug 2026, 15:128,820-10
16 Aug 2026, 21:048,830+3
13 Aug 2026, 04:358,827+3
10 Aug 2026, 13:478,824+31
7 Aug 2026, 05:578,793-5
6 Aug 2026, 08:178,798first reading

Engagement

58 posts held, back to 30 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 30 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
16.8%
avg views ÷ 8,936 subscribers
Avg views / post
1,500
36 posts measured
Reaction rate
2.26%
reactions ÷ views · ER floor
Posts in window
36
of 58 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
WindowRolling 30 days · latest post in window 28 August 2026
Posts held58 (30 July 202628 August 2026)
Views total54,143
Reactions total1,221
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 16:07 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
1m 17s
Average length
26s

Measured directly from 3 videos 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

1,816 reactions across 56 posts, in 14 distinct kinds. The most used accounts for 39.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
71539.4%
🔥41723.0%
👍25414.0%
❤‍🔥19110.5%
🤩774.24%
😍693.80%
🏆351.93%
😁271.49%
🥰221.21%
🤔30.165%
👌20.11%
💔20.11%
custom 547188347721954900610.055%
🙏10.055%

Custom emoji. One row above is a 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 count beside it is Telegram’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 58 of the 58 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 1,851 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 58 most recent posts we hold, published 30 July 2026 to 28 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.

Telegram Stars

Stars received
2
across the posts below
Posts paid on
1
of 58 we hold a reading for · 2%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @goldenring_run. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 58 most recent posts we hold for this entry, published 30 July 2026 to 28 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

27 Aug 2026, 09:23 UTC≈1,520 views44 reactionsread 28 August 2026

Posted without readable text

👍30❤‍🔥8🤩5🔥1

27 Aug 2026, 07:15 UTC≈1,550 views38 reactionsread 28 August 2026
Photo

💧 Точки питания и освежения на Ярославском полумарафоне Сохраняйте схему, чтобы заранее знать, где на дистанции можно будет пополнить запас воды, освежиться и подкрепиться. На дистанции «ПСБ 5 км» участников ждут 2 пункта освежения с водой и губки, а на «трешке» — вода и губки на финише. И важное напоминание: использованные стаканчики, губки и упаковки от гелей выбрасывайте только в мусорные контейнеры, расположен

🔥323🤩2custom 54718834772195490061

26 Aug 2026, 16:17 UTC≈1,630 views55 reactionsread 28 August 2026
Photo

Ростов Великий, это было красиво! ✨ Яркие моменты полумарафона уже можно найти в репортажном альбоме от фотографа в розовых кроссовках: https://mysport.photo/event/BZK_Rostov_26_rep Скорее погружайтесь в атмосферу старта в Ростове Великом 💙

👍2721🔥7

25 Aug 2026, 14:15 UTC≈1,750 views75 reactionsread 28 August 2026

Posted without readable text

46🔥24🤩5

25 Aug 2026, 12:15 UTC≈1,670 views23 reactionsread 28 August 2026
Photo

Воспоминание о старте, которое можно носить 💛 Худи Ярославского полумарафона – не просто одежда, а памятная вещь, которая будет напоминать о старте, Ярославле и преодоленных километрах. Свободный крой, капюшон и удобный карман-кенгуру. Всё продумано для комфорта. Худи без молнии не сковывает движения и легко вписывается в повседневный гардероб. Наденете его спустя время и вспомните атмосферу Ярославского полумараф

14🔥5🤩4

24 Aug 2026, 14:15 UTC≈1,860 views25 reactionsread 28 August 2026
Photo

⚡️ Программа XIII Ярославского полумарафона «Золотое кольцо» 13 сентября встречаемся в Ярославле на одном из главных стартов сезона серии «Фармэко – Бегом по Золотому кольцу». Публикуем программу события, чтобы вы могли заранее спланировать свой беговой день и свериться со временем старта. ✅ Выдача стартовых пакетов будет проходить: 11 сентября с 12:00 до 20:00 и 12 сентября с 10:00 до 19:00 в культурно-спортивном

15👍8🤩2

24 Aug 2026, 11:35 UTC≈1,830 views21 reactionsread 28 August 2026

Posted without readable text

👍117❤‍🔥3

23 Aug 2026, 18:12 UTC≈1,930 views45 reactionsread 28 August 2026
Photo

📷 Фотографии забега в Ростове Великом на сайте mysport.photo На платформе настроен поиск по лицу и по стартовому номеру, который был у вас на забеге. Приобрести фотографии можно по ссылке: https://mysport.photo/event/BZK_Rostov_26 По техническим вопросам, пожалуйста, пишите на почту [email protected]

🔥259👍9🥰1😁1

23 Aug 2026, 12:33 UTC≈2,090 views98 reactionsread 28 August 2026
Photo

До новых встреч, Ростов Великий Беговой день подошёл к концу, и XII полумарафон «Ростов Великий» завершён. Пусть сегодняшний результат радует, фотографии возвращают в любимые моменты, а знакомство с городом станет поводом сюда вернуться. Спасибо, что провели этот день с нами ❤️

58❤‍🔥21🤩13👍2🔥2😍2

23 Aug 2026, 11:17 UTC≈1,560 views45 reactionsread 26 August 2026
Photo

Результаты «пятёрочки» в Ростове Великом: 🥇 Егоров Дмитрий (16:12) и Токмакова Елена (19:10) 🥈 Горынь Алексей (18:11) и Непанова Александра (19:45) 🥉 Цветников Олег (19:02) и Ушакова Ксения (20:07) Результаты участников дистанции 3 км с хронометражем можно посмотреть на Russia Running.

24🔥16❤‍🔥5

23 Aug 2026, 11:15 UTC≈1,270 views32 reactionsread 25 August 2026
Video

Кто хотел пробежать в дождь? Надеемся, что сегодня поучаствовали.

😁265👍1

Showing the 12 most recent of 58 posts we hold for @goldenring_run. 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.

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 5 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.

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 9 September 2026 — this entry's latest reading, not the date you are reading this.

“Бегом по Золотому кольцу” (@goldenring_run), 8,936 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/goldenring_run.

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.