Channel
Dobrova
@dobrova9
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,604subscribers
-91 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002151023768 |
|---|---|
| Type | Channel |
| Username | @dobrova9 |
| Created | Between 1 May 2024 and 31 October 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/dobrova9 |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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 |
|---|---|---|
| 5 Nov 2026, 19:16 | 2,604 | -6 |
| 3 Nov 2026, 00:56 | 2,610 | -4 |
| 30 Oct 2026, 21:20 | 2,614 | -10 |
| 28 Oct 2026, 03:30 | 2,624 | -1 |
| 25 Oct 2026, 11:54 | 2,625 | -4 |
| 22 Oct 2026, 05:30 | 2,629 | -1 |
| 18 Oct 2026, 23:51 | 2,630 | -4 |
| 15 Oct 2026, 20:41 | 2,634 | -5 |
| 13 Oct 2026, 02:00 | 2,639 | -7 |
| 6 Oct 2026, 07:14 | 2,646 | +5 |
| 29 Sept 2026, 06:21 | 2,641 | -12 |
| 19 Sept 2026, 07:57 | 2,653 | -2 |
| 14 Sept 2026, 13:17 | 2,655 | -5 |
| 14 Sept 2026, 01:22 | 2,660 | no change |
| 11 Sept 2026, 02:42 | 2,660 | -5 |
| 6 Sept 2026, 06:18 | 2,665 | -6 |
| 2 Sept 2026, 00:13 | 2,671 | -2 |
| 30 Aug 2026, 03:43 | 2,673 | -1 |
| 27 Aug 2026, 08:36 | 2,674 | -1 |
| 24 Aug 2026, 16:55 | 2,675 | 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.
@kamilatseitlina · 50,710
Telegram ranks this channel #5 of 76 here — alongside 75 others — read 25 August 2026
@ekaterinalebedevaa · 23,178
Telegram ranks this channel #7 of 64 here — alongside 63 others — read 19 September 2026
@yanamargaryan · 23,337
Telegram ranks this channel #45 of 50 here — alongside 49 others — read 17 September 2026
@vlakut · 43,191
Telegram ranks this channel #61 of 61 here — alongside 60 others — read 28 August 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“Dobrova” (@dobrova9), 2,604 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/dobrova9.
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.