Channel
RadioRoute66
@RadioRoute66
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,509subscribers
+68 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 | -1001775555535 |
|---|---|
| Type | Channel |
| Username | @RadioRoute66 |
| Created | 19 December 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 28 September 2026 |
| Last confirmed live | 28 September 2026 |
| Measurements held | 15 |
| On Telegram | t.me/RadioRoute66 |
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 28 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Sept 2026, 00:29 | 1,509 | no change |
| 24 Sept 2026, 21:41 | 1,509 | +12 |
| 17 Sept 2026, 03:01 | 1,497 | +2 |
| 12 Sept 2026, 23:40 | 1,495 | +11 |
| 9 Sept 2026, 11:00 | 1,484 | +2 |
| 4 Sept 2026, 12:57 | 1,482 | +8 |
| 29 Aug 2026, 06:29 | 1,474 | +2 |
| 26 Aug 2026, 06:55 | 1,472 | -1 |
| 23 Aug 2026, 07:58 | 1,473 | +6 |
| 19 Aug 2026, 15:34 | 1,467 | +3 |
| 16 Aug 2026, 21:45 | 1,464 | +10 |
| 14 Aug 2026, 00:47 | 1,454 | +8 |
| 10 Aug 2026, 22:42 | 1,446 | +4 |
| 8 Aug 2026, 06:57 | 1,442 | +1 |
| 7 Aug 2026, 16:26 | 1,441 | 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.
@msa3dr · 50,438
Telegram ranks this channel #42 of 59 here — alongside 58 others — read 22 September 2026
@MyCrrush · 19,754
Telegram ranks this channel #50 of 58 here — alongside 57 others — read 29 September 2026
@dialogbeyadmandani · 22,213
Telegram ranks this channel #57 of 76 here — alongside 75 others — read 21 September 2026
@dynatonic · 29,991
Telegram ranks this channel #66 of 76 here — alongside 75 others — read 7 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 28 September 2026 — this entry's latest reading, not the date you are reading this.
“RadioRoute66” (@RadioRoute66), 1,509 subscribers as measured 28 September 2026. Telegram Register, tgregister.com/channel/RadioRoute66.
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.