Channel
Radio_babolsar
@Radio_babolsarrr
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,943subscribers
+484 since we began measuring on 26 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002032117190 |
|---|---|
| Type | Channel |
| Username | @Radio_babolsarrr |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 September 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/Radio_babolsarrr |
Topic
Music — 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 100% 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 |
|---|---|---|
| 3 Nov 2026, 05:26 | 2,943 | +22 |
| 31 Oct 2026, 15:47 | 2,921 | +9 |
| 28 Oct 2026, 23:51 | 2,912 | +82 |
| 25 Oct 2026, 19:38 | 2,830 | +13 |
| 22 Oct 2026, 17:20 | 2,817 | +19 |
| 19 Oct 2026, 06:27 | 2,798 | +16 |
| 15 Oct 2026, 21:04 | 2,782 | +15 |
| 12 Oct 2026, 19:30 | 2,767 | +65 |
| 6 Oct 2026, 03:02 | 2,702 | +29 |
| 28 Sept 2026, 16:40 | 2,673 | +124 |
| 16 Sept 2026, 03:55 | 2,549 | +18 |
| 15 Sept 2026, 14:16 | 2,531 | no change |
| 12 Sept 2026, 10:42 | 2,531 | +17 |
| 8 Sept 2026, 01:01 | 2,514 | +39 |
| 2 Sept 2026, 13:35 | 2,475 | +6 |
| 30 Aug 2026, 11:45 | 2,469 | +10 |
| 26 Aug 2026, 23:45 | 2,459 | 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.
@DjLuna8 · 18,710
Telegram ranks this channel #35 of 65 here — alongside 64 others — read 3 October 2026
@bass_matrix · 57,419
Telegram ranks this channel #49 of 52 here — alongside 51 others — read 26 August 2026
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.
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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“Radio_babolsar” (@Radio_babolsarrr), 2,943 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/Radio_babolsarrr.
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.