5 measurements spanning 15 days, net -20. 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 284–311 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
22 Aug 2026, 10:09
287
-11
15 Aug 2026, 00:46
298
-10
8 Aug 2026, 07:48
308
no change
8 Aug 2026, 03:10
308
+1
7 Aug 2026, 17:05
307
first reading
Engagement
7 posts held, back to 5 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 · 30 days
9.76%
avg views ÷ 287 subscribers
Avg views / post
28.0
1 post measured
Reaction rate
25.0%
reactions ÷ views · ER floor
Posts in window
1
of 7 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 27 July 2026
Posts held
7 (5 July 2026 – 27 July 2026)
Views total
28
Reactions total
7
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
8 Aug 2026, 07:48 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
3m 31s
Average length
35s
Measured directly from 6 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
56 reactions across 7 posts, in 7 distinct kinds. The most used accounts for 33.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
19
33.9%
🔥
17
30.4%
👍
11
19.6%
👌
3
5.36%
🤩
3
5.36%
🤷♂
2
3.57%
🤯
1
1.79%
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 7 of the 7 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 56reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 5 July 2026 to 27 July 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.
Дом российско-китайской дружбы — это экспозиционно-выставочный центр в Благовещенске (Амурская область), который открылся 2 октября 2025 года. Он стал площадкой для диалога культур, сотрудничества регионов и укрепления связей между Россией и Китаем.
📍Благовещенск, Амурская область
#благовещенск #городнаграницескитаем
🦕Про Амурских Динозавров!
Климат в Благовещенске летом какой-то прям тропический: теплый и очень влажный. Неудивительно, что 65 млн.лет назад по территории нынешнего Благовещенска гуляли динозавры!
🦖 Останки древних животных нашли в начале 20вв. В результате раскопок было найдено одно из крупнейших кладбищ в России!
На Набережной города с недавних пор можно в увидеть скульптуру динозавра, которого назвали Амурозавром…
Обман зрения? Мой мозг сломался», памагите!😆
Колесо обозрения находится в городе Хэйхэ в Китае, но с нашей рф стороны кажется, что оно на нашей территории и до него можно дотронуться рукой! Но чем ближе мы к нему подъезжаем , тем оно становиться меньше и в итоге исчезает!
#благовещенск
🍜Зашли в очередной магазин Китайских продуктов «Снеки».
В Благовещенске у них 4 сетевые точки.
За последние 3 года стало особенно много китайской продукции. Видимо санкции повлияли.
А мы не против) Ассортимент большой: и чипсы, газировка, лапша самовар, желе, соевое мясо, сладости. Хороший магазин для покупок как для себя так и на подарки.
Кстати 8 и 28 числа в магазине скидка на все 20% 👍
📍Благовещенск, Кантемиров
🧋«Биба и Бобл» - мини-кофейня в ТРЦ «Острова». Находится рядом с магазином «Купи слона».
Интересный и красивый дизайн, ощущение что попала в какой-то мультик. Захотелось здесь провести время, и я заказала холодный чай с кусочками киви. За свою цену в 300₽ чай по вкусу оказался хорошим. Правда изначально я хотела чай с клубникой, но ее не было в наличии.
Работники кофейни-молодые девочки, мне показались доброжелательн…
👍3🔥3❤2
Showing the 7 most recent of 7 posts we hold for @mos_walk. 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.
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 22 August 2026 — this
entry's latest reading, not the date you are reading this.
“🪆Москва, гуляй! 🪆” (@mos_walk), 287 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/mos_walk.
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.