Telegram RegisterThe public register of Telegram
Telegram profile photo for Город 📸 на бегу

Channel

Город 📸 на бегу

@gorod_na_begu

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

98subscribers

+1 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002740405616
TypeChannel
Username@gorod_na_begu
CreatedBetween 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live16 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/gorod_na_begu

Topic

Local community — 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 27 September 2026 and assigned it the closest of 31 fixed categories, at 46% 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

979897.59 August 2026 — 97 subscribers9 August 2026 — 97 subscribers16 September 2026 — 98 subscribers9 August 202616 September 2026
3 measurements spanning 38 days, net +1. 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 97–98 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 12:5998+1
9 Aug 2026, 12:0097no change
9 Aug 2026, 10:1597first reading

Engagement

3 posts held, back to 2 August 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 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 3 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

29 reactions across 3 posts, in 5 distinct kinds. The most used accounts for 41.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1241.4%
💘1137.9%
❤‍🔥26.90%
💔26.90%
😍26.90%

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

Measured over the 3 most recent posts we hold, published 2 August 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, 20:47 UTC38 views11 reactionsread 9 August 2026
Photo

Пару недель назад съездили попрощаться с Элекрозаводом на всякий случай... Я не знаю, как можно принимать такие законы, которые перестают считать памятником архитектуры то, что очевидно им является... я не знаю, как можно спать спокойно, когда подписываешь документы на снос таких сооружений... я не знаю, как можно считать, что возводя бетонные копии, ты сохраняешь историю... я не знаю, что ждет и 31 станцию метро и …

❤5💘3💔2❤‍🔥1

4 Aug 2026, 14:57 UTC47 views10 reactionsread 9 August 2026
Photo

Моя Москва на Казанскую ч/б плëнку ТАСМА ТИП-42л iso400 🖤 Последний кадр-половинка - конец плëнки)) аж 39 кадр вместо 36))) ТАСМА Выпускается в Казани с 1936 года! ТАСМА- это акроним от "татарские светочувствительные материалы" и перевод на татарский слова "лента" (плëнка) 📍м. Трубная, м. Сокольники, м. Китай-город, м. Электрозаводская

💘4❤3😍2❤‍🔥1

2 Aug 2026, 21:59 UTC36 views8 reactionsread 9 August 2026
Photo

Ну и вот еще одно место, которое обещает вскоре снова стать интересным после периода запустения- Левобережье озера Кабан 🐗 (на древнетюркском кабан- "водоем", но знаю, вы тоже мысленно хрюкнули )) В 1855 году тут был основан мыловаренный завод Братьев Крестовниковых (фото 1-4), а в 1867 рядышком открылся пивоваренный завод Петцольда (фото 6,7) 🍺 Первый находится в процессе реконструкции под апартаменты (увы!) посл…

❤4💘4

Showing the 3 most recent of 3 posts we hold for @gorod_na_begu. 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 1 registered channel — 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.

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

“Город 📸 на бегу” (@gorod_na_begu), 98 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/gorod_na_begu.

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.