Channel
@zhest_tambov
On this record: Topic · Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
176subscribers
-7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001802819698 |
|---|---|
| Type | Channel |
| Username | @zhest_tambov |
| Created | Between 1 September 2022 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/zhest_tambov |
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 24 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 22:26 | 176 | -1 |
| 31 Oct 2026, 07:26 | 177 | -4 |
| 18 Oct 2026, 05:18 | 181 | -1 |
| 29 Sept 2026, 21:01 | 182 | -1 |
| 19 Sept 2026, 14:22 | 183 | no change |
| 14 Sept 2026, 21:39 | 183 | -1 |
| 28 Aug 2026, 23:07 | 184 | -1 |
| 22 Aug 2026, 13:34 | 185 | +2 |
| 7 Aug 2026, 09:21 | 183 | first reading |
1 post held, back to 5 September 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 1 post for this entry, the most recent from 5 September 2026. An engagement rate over an empty window would be a number about nothing.
Друзья, если у вас возникают проблемы с использованием Telegram через мобильный интернет, мы рады предложить вам VPN, который решит эту проблему. Используйте наш бот — https://t.me/globus_vpn_bot первые 2 недели БЕСПЛАТНО.
Showing the 1 most recent of 1 post we hold for @zhest_tambov. 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“Жесть Тамбов” (@zhest_tambov), 176 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/zhest_tambov.
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.