Telegram RegisterThe public register of Telegram
Telegram profile photo for BEG.BELGRADE

Channel

BEG.BELGRADE

@runningbeg

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,479subscribers

+56 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001925197008
TypeChannel
Username@runningbeg
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/runningbeg

Topic

Sports — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 17 September 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

1,4211,4791,4507 August 2026 — 1,423 subscribers7 August 2026 — 1,421 subscribers10 August 2026 — 1,431 subscribers13 August 2026 — 1,436 subscribers16 August 2026 — 1,433 subscribers19 August 2026 — 1,438 subscribers22 August 2026 — 1,443 subscribers25 August 2026 — 1,449 subscribers31 August 2026 — 1,452 subscribers4 September 2026 — 1,459 subscribers10 September 2026 — 1,473 subscribers13 September 2026 — 1,474 subscribers17 September 2026 — 1,479 subscribers7 August 202617 September 2026
13 measurements spanning 42 days, net +56. 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 1,412–1,488 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 18:411,479+5
13 Sept 2026, 19:571,474+1
10 Sept 2026, 02:561,473+14
4 Sept 2026, 09:561,459+7
31 Aug 2026, 22:161,452+3
25 Aug 2026, 23:331,449+6
22 Aug 2026, 23:041,443+5
19 Aug 2026, 17:161,438+5
16 Aug 2026, 18:551,433-3
13 Aug 2026, 09:571,436+5
10 Aug 2026, 11:481,431+10
7 Aug 2026, 19:521,421-2
7 Aug 2026, 05:321,423first reading

Engagement

19 posts held, back to 22 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 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

223 reactions across 19 posts, in 9 distinct kinds. The most used accounts for 46.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
10346.2%
🎉3917.5%
❤‍🔥3515.7%
2410.8%
🔥146.28%
🤝52.24%
custom 525800238228074136010.448%
👍10.448%
🥰10.448%

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 19 of the 19 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 223 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 22 July 2026 to 6 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.

Recent posts

6 Aug 2026, 19:40 UTC158 views28 reactionsread 7 August 2026
Photo

This week is rich with birthdays of our pacers, and today we’re celebrating Oleg @al_orre! 🎉 Did you know Oleg used to play in a rock band? 🤘 And setting a new PB after taking a month off from running? That’s so Oleg. Happy Birthday! Thanks for being an awesome pacer and part of our community. Looking forward to many more fast Friday runs together. Wishing you an amazing year ahead! 🥳

🎉1810

6 Aug 2026, 16:02 UTC195 views9 reactionsread 7 August 2026
Photo

FRIDAY | FUN RUN | NEW LOCATION ⚡️Start: 19:08 📍Location: Rocket Vracar 🗺Distance: 10К/7K Pace: 10K - 5:00/km Kolja @m1kevazovski 10K - 5:45-6:00/km Vova @vladimirAgeev Olga @olgabasarevskaya 7К - 6:30/km Chris @nonchrist Vika @vika_akiv 7K - 5:45-6:00/km Martin @tionesto 🔥 HEAT TIPS 🔥 Hydrate smart by drinking before the run, bring a bottle if you can, wear sunscreen, a lightweight cap or visor, plus light-colou

54

4 Aug 2026, 19:26 UTC285 views69 reactionsread 7 August 2026
Photo

Happy birthday to one of our former pacers - Natasha @callredsquare! You gave so much time, energy, and support to our community! Thank you for everything and for continuing to be an inspiration and a role model to so many of us. Wishing you a wonderful year ahead! 🎉

❤‍🔥35🎉2113

4 Aug 2026, 19:13 UTC269 views4 reactionsread 7 August 2026
Photo

WEDNESDAY | COFFEE RUN Start: 8:08 AM Location: D59B Distance: 5K, 8К Pace: 6:15-6:30/km, 6:00/km Pacers: 🤪 Andrey @a_v_v 😎 Kolya @m1kevazovski 😋 Vika @vika_akiv 🥰 Chris @Nonchrist 🥰 Katya @polykate 🫤 Sergei @shoki_o_0 🔥 HEAT TIPS 🔥 Hydrate smart by drinking before the run, bring a bottle if you can, wear sunscreen, a lightweight cap or visor, plus light-coloured, breathable clothing Rules: We ask you not to over

4

Signed Mari Tretiakova

3 Aug 2026, 17:11 UTC269 views11 reactionsread 7 August 2026
Photo

☀TUESDAY RUNS ☀️ EARLY BIRDS ⏰ 6:38 AM 📍 Usće 🗺 7K 🚀 6:10–6:25/km 😎 Pacers: Olga @olgabasarevskaya ☀️MORNING RUN ⏰ 7:38 AM 📍 7AM Roasters 🗺 3K/5K 🚀 6:00–7:00/km 😎 Pacers: Sergei @shoki_o_0 Vova @vladimirAgeev 🌙 ROCKET ⏰ 19:08 📍 Rocket Vračar 🗺 10K 🚀 5:45–6:00/km 😎 Pacers: Tonya @ganiciello Sergei @shoki_o_0 🔥 HEAT TIPS 🔥 Hydrate smart by drinking before the run, bring a bottle if you can, wear sunscreen, a ligh

74

3 Aug 2026, 17:08 UTC252 views6 reactionsread 7 August 2026
Photo

Hey runners! 🏃 Our weekly schedule for August 3-9 is up — check it out above and pick your days! Lots to choose from this week! See you out there! 👟

6

1 Aug 2026, 17:07 UTC313 views3 reactionsread 7 August 2026
Photo

SUNDAY | LONG RUN | 19K 🐌 Start: 7:38 AM 🤩 Start Location: Brankov most (at the embankment) ☕️ Finish: Sonder 🍭 Distance: 19K 🌪️ Route: Strava Pace: 5:45-6:00 Pacers: 🥰 Vova @vladimirAgeev 🤩 Tonya @ganiciello There will be nowhere to leave your belongings early in the morning. We carry everything with us, so leave unnecessary items at home! 🔥 HEAT TIPS 🔥 Hydrate smart by drinking before the run, bring a bottle

21

1 Aug 2026, 13:44 UTC293 views6 reactionsread 7 August 2026
Photo

SUNDAY | SOCIAL RUN | WITH SOME BONUS 🔫 ⏰Start: 9:08 AM 📍Location: Sonder - Gastrosor 🗺️ Distance: 4K/6K ⚡️Pace: 4К - 7:00/km 6K - 6:30/km Pacers: 🐼Anna @ultradoronina 🐰 Vika @vika_akiv 🔫 WATER GUNS WELCOME Bring one along if you’d like — a great way to stay cool and have some fun mid-run! 🔥 HEAT TIPS 🔥 Hydrate smart by drinking before the run, bring a bottle if you can, wear sunscreen, a lightweight cap or viso

3🤝3

31 Jul 2026, 13:20 UTC318 views6 reactionsread 7 August 2026
Photo

SATURDAY | STRETCHING FOR RUNNERS ☀️Start: 9:30 AM 🔒Location: Kultura studio 🧷Level: Beginner 💞Coach: Lena @lenaespacio Rules: • Our classes start exactly at the scheduled time • We recommend bringing your own mat, as we have a limited number available. • You will need a gym uniform for stretching. • We ask you not to disturb participants or argue with the trainer during stretching. • This is an open class, but you

6

Signed Лена

30 Jul 2026, 18:16 UTC307 views5 reactionsread 7 August 2026
Photo

FRIDAY | FUN RUN ⚡️Start: 19:08 📍Location: D59B 🗺Distance: 10К/7K/5K Pace: 10K - 5:00/km Kolja @m1kevazovski 10K - 5:45-6:00/km Vova @vladimirAgeev 10K - 7:00/km Anna @ultradoronina 7К - 6:15-6:30/km Chris @nonchrist 5K - 6:30-7:00/km Maria @maritretyakova 🔥 HEAT TIPS 🔥 Hydrate smart by drinking before the run, bring a bottle if you can, wear sunscreen, a lightweight cap or visor, plus light-coloured, breathable

41

29 Jul 2026, 17:34 UTC312 views6 reactionsread 7 August 2026
Photo

THURSDAY | BERRIES RUN 🫐🍑🍒 Let's go for a run and eat berries! 💵And don’t forget some cash for the market! ⏰Start: 7:28 📍Locations: Brankov Most 🗺️Distance: 6K Brankov–> FUKA 🏃Pace: 6:00-6:30/km Pacers: 🫐 Olga @olgabasarevskaya Rules: We ask you not to overtake the pacers. Our runs start exactly at the set time. We’re not responsible for your physical condition on these runs, so if you notice someone is feeling u

6

28 Jul 2026, 18:56 UTC330 views3 reactionsread 7 August 2026
Photo

WEDNESDAY | COFFEE RUN Start: 8:08 AM Location: D59B Distance: 5K, 8К Pace: 6:15-6:30/km, 6:00/km Pacers: 🫤 Andrey @a_v_v 🐇Kolya @m1kevazovski 😉Masha @maritretyakova 🌟Vika @vika_akiv 🐰Katya @polykate Rules: We ask you not to overtake the pacers. Our runs start exactly at the set time. We’re not responsible for your physical condition on these runs, so if you notice someone is feeling unwell, stop, support them

2custom 52580023822807413601

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

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

“BEG.BELGRADE” (@runningbeg), 1,479 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/runningbeg.

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.