Channel
podslushano_v_dobrom
@podslushano_v_dobrom
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,029subscribers
+97 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001649866875 |
|---|---|
| Type | Channel |
| Username | @podslushano_v_dobrom |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 5 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/podslushano_v_dobrom |
Topic
Other / unclassifiable — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Nov 2026, 00:44 | 4,029 | +2 |
| 4 Nov 2026, 04:15 | 4,027 | +4 |
| 31 Oct 2026, 20:08 | 4,023 | -1 |
| 28 Oct 2026, 14:40 | 4,024 | -3 |
| 25 Oct 2026, 21:30 | 4,027 | -9 |
| 22 Oct 2026, 11:19 | 4,036 | -1 |
| 19 Oct 2026, 01:17 | 4,037 | +29 |
| 16 Oct 2026, 07:35 | 4,008 | +21 |
| 13 Oct 2026, 10:49 | 3,987 | +21 |
| 7 Oct 2026, 12:42 | 3,966 | -4 |
| 30 Sept 2026, 07:54 | 3,970 | +10 |
| 16 Sept 2026, 06:58 | 3,960 | +1 |
| 12 Sept 2026, 14:40 | 3,959 | +1 |
| 8 Sept 2026, 09:39 | 3,958 | -2 |
| 5 Sept 2026, 22:39 | 3,960 | no change |
| 3 Sept 2026, 10:03 | 3,960 | +2 |
| 30 Aug 2026, 18:35 | 3,958 | +1 |
| 27 Aug 2026, 11:43 | 3,957 | +5 |
| 24 Aug 2026, 12:44 | 3,952 | +5 |
| 20 Aug 2026, 14:42 | 3,947 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Appears in Telegram’s recommendations for other channels
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.
@Vladimir_podslushal · 36,022
Telegram ranks this channel #2 of 79 here — alongside 78 others — read 23 September 2026
@incident33 · 48,329
Telegram ranks this channel #8 of 26 here — alongside 25 others — read 5 September 2026
@smi_vladimir · 37,770
Telegram ranks this channel #10 of 59 here — alongside 58 others — read 5 September 2026
@rusvladimir · 31,250
Telegram ranks this channel #41 of 95 here — alongside 94 others — read 5 September 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“podslushano_v_dobrom” (@podslushano_v_dobrom), 4,029 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/podslushano_v_dobrom.
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.