Channel
رادیو بهبودی ™
@RecoveryRadio
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,090subscribers
+64 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001005802601 |
|---|---|
| Type | Channel |
| Username | @RecoveryRadio |
| Created | Between 1 September 2015 and 31 December 2015 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 5 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/RecoveryRadio |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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 |
|---|---|---|
| 4 Nov 2026, 17:27 | 4,090 | +8 |
| 1 Nov 2026, 12:19 | 4,082 | +11 |
| 26 Oct 2026, 00:00 | 4,071 | -3 |
| 23 Oct 2026, 09:09 | 4,074 | +1 |
| 20 Oct 2026, 07:17 | 4,073 | +7 |
| 17 Oct 2026, 14:58 | 4,066 | +1 |
| 10 Oct 2026, 19:01 | 4,065 | -3 |
| 5 Oct 2026, 01:38 | 4,068 | +14 |
| 25 Sept 2026, 19:17 | 4,054 | -2 |
| 17 Sept 2026, 05:38 | 4,056 | -1 |
| 13 Sept 2026, 05:36 | 4,057 | -3 |
| 9 Sept 2026, 01:01 | 4,060 | +5 |
| 5 Sept 2026, 12:44 | 4,055 | no change |
| 3 Sept 2026, 20:38 | 4,055 | -4 |
| 31 Aug 2026, 07:57 | 4,059 | +10 |
| 28 Aug 2026, 16:33 | 4,049 | +8 |
| 25 Aug 2026, 20:15 | 4,041 | -1 |
| 22 Aug 2026, 22:22 | 4,042 | +3 |
| 19 Aug 2026, 02:12 | 4,039 | +8 |
| 16 Aug 2026, 04:36 | 4,031 | 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.
@faghatbarayeemruz · 29,446
Telegram ranks this channel #10 of 34 here — alongside 33 others — read 9 September 2026
@soheilsangarzadeh2 · 48,874
Telegram ranks this channel #52 of 86 here — alongside 85 others — read 26 August 2026
@arshiyaniha · 63,521
Telegram ranks this channel #68 of 81 here — alongside 80 others — read 21 August 2026
@AutumnAU · 28,205
Telegram ranks this channel #70 of 90 here — alongside 89 others — read 9 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“رادیو بهبودی ™” (@RecoveryRadio), 4,090 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/RecoveryRadio.
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.