Channel
🌀 RED_AViATOR_THANOS 🌀
@RED_AViATOR_CRASH
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,468subscribers
-38 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 | -1002082836694 |
|---|---|
| Type | Channel |
| Username | @RED_AViATOR_CRASH |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 September 2026 |
| Last confirmed live | 5 October 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 5 October 2026 |
| On Telegram | t.me/RED_AViATOR_CRASH |
Topic
Gambling & betting — 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 99% 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 |
|---|---|---|
| 5 Oct 2026, 22:15 | 1,468 | -6 |
| 28 Sept 2026, 12:39 | 1,474 | -11 |
| 28 Sept 2026, 03:44 | 1,485 | no change |
| 19 Sept 2026, 06:18 | 1,485 | -5 |
| 14 Sept 2026, 10:02 | 1,490 | -2 |
| 10 Sept 2026, 23:40 | 1,492 | -7 |
| 5 Sept 2026, 20:57 | 1,499 | -1 |
| 1 Sept 2026, 15:27 | 1,500 | -4 |
| 30 Aug 2026, 01:24 | 1,504 | -2 |
| 26 Aug 2026, 16:01 | 1,506 | 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.
@devman07 · 65,342
Telegram ranks this channel #13 of 24 here — alongside 23 others — read 26 August 2026
@crash_egy · 18,957
Telegram ranks this channel #15 of 35 here — alongside 34 others — read 4 October 2026
@itsfst · 54,935
Telegram ranks this channel #61 of 69 here — alongside 68 others — read 26 August 2026
This channel appears in 3 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 October 2026 — this entry's latest reading, not the date you are reading this.
“🌀 RED_AViATOR_THANOS 🌀” (@RED_AViATOR_CRASH), 1,468 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/RED_AViATOR_CRASH.
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.