Channel
Ӿanadu | بِهِشـتــ 🪽
@xanaduda
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,347subscribers
-56 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002172892521 |
|---|---|
| Type | Channel |
| Username | @xanaduda |
| Description | برای حال خوب 🤍✨ @Aidarezv لینک ناشناس برای آهنگاتون : https://t.me/chat_hidebot?start=sec-ejidjefbh |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 October 2026 |
| Last confirmed live | 1 October 2026 |
| Measurements held | 12 |
| On Telegram | t.me/xanaduda |
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 1 October 2026 and assigned it the closest of 31 fixed categories, at 88% 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 |
|---|---|---|
| 1 Oct 2026, 02:57 | 1,347 | no change |
| 26 Sept 2026, 05:42 | 1,347 | -13 |
| 17 Sept 2026, 14:01 | 1,360 | -9 |
| 13 Sept 2026, 17:38 | 1,369 | -3 |
| 9 Sept 2026, 21:20 | 1,372 | -10 |
| 4 Sept 2026, 22:20 | 1,382 | -3 |
| 1 Sept 2026, 02:27 | 1,385 | -2 |
| 29 Aug 2026, 12:25 | 1,387 | -4 |
| 26 Aug 2026, 05:45 | 1,391 | -4 |
| 23 Aug 2026, 02:43 | 1,395 | -4 |
| 16 Aug 2026, 16:05 | 1,399 | -4 |
| 15 Aug 2026, 07:21 | 1,403 | 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.
@moodsgraphy · 27,958
Telegram ranks this channel #8 of 53 here — alongside 52 others — read 11 September 2026
@Ghofliyamon · 42,459
Telegram ranks this channel #17 of 62 here — alongside 61 others — read 28 August 2026
@arome_Delam · 49,363
Telegram ranks this channel #35 of 79 here — alongside 78 others — read 28 August 2026
@yalitilmiss · 102,755
Telegram ranks this channel #39 of 67 here — alongside 66 others — read 15 August 2026
@Nbz_Morde · 28,273
Telegram ranks this channel #52 of 68 here — alongside 67 others — read 9 September 2026
@BritishEnglishforall · 329,852
Telegram ranks this channel #58 of 64 here — alongside 63 others — read 24 August 2026
This channel appears in 6 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 1 October 2026 — this entry's latest reading, not the date you are reading this.
“Ӿanadu | بِهِشـتــ 🪽” (@xanaduda), 1,347 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/xanaduda.
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.