https://places.moscow/trip/azhurnyy-dom-burova

Channel
Places.Moscow
@PlacesMoscow
On this record: Topic · Growth · Engagement · Posts · Cite this entry
211subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001345265189 |
|---|---|
| Type | Channel |
| Username | @PlacesMoscow |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 4 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 4 October 2026 |
| On Telegram | t.me/PlacesMoscow |
Topic
Travel — 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 24 September 2026 and assigned it the closest of 31 fixed categories, at 53% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 14:59 | 211 | -1 |
| 9 Sept 2026, 16:17 | 212 | -1 |
| 30 Aug 2026, 17:54 | 213 | -2 |
| 8 Aug 2026, 10:48 | 215 | no change |
| 7 Aug 2026, 22:59 | 215 | first reading |
Engagement
20 posts held, back to 19 February 2023 — 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 20 posts for this entry, the most recent from 10 March 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
https://places.moscow/trip/stanciya-metro-pyhtino
https://places.moscow/trip/kupavinskiy-karer
https://places.moscow/trip/kindyakovskiy-kamen
https://places.moscow/trip/gorodskoy-kvartal-iskra-park
https://places.moscow/trip/malenkaya-gollandiya
https://places.moscow/trip/pamyatnik-varanu
https://places.moscow/trip/kinogorod-uralsk
https://places.moscow/trip/50-samyh-poseschaemyh-mest-moskvy
https://places.moscow/trip/usadba-vaskino
https://places.moscow/trip/park-huamin
https://places.moscow/trip/zabroshennoe-kladbische-sela-novorozhdestvenno
Showing the 12 most recent of 20 posts we hold for @PlacesMoscow. 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Places.Moscow” (@PlacesMoscow), 211 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/PlacesMoscow.
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.