Channel
"وآله"
@Vaaaaleh
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,698subscribers
-80 since we began measuring on 22 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001578739886 |
|---|---|
| Type | Channel |
| Username | @Vaaaaleh |
| Description | "دارم دیوانه میشوم از حلول، از میلِ حلول در هر چه که هست، در هر چه که نیست، در هر چه که هر چه..." #چی_مَن ارتباط با وآله👇 @vaaaalehchannel «وآله» به معنی شیفته، حیران است. |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 September 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 9 |
| On Telegram | t.me/Vaaaaleh |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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 |
|---|---|---|
| 14 Sept 2026, 00:11 | 2,698 | no change |
| 13 Sept 2026, 06:01 | 2,698 | -17 |
| 9 Sept 2026, 10:19 | 2,715 | -9 |
| 4 Sept 2026, 12:36 | 2,724 | -18 |
| 31 Aug 2026, 17:37 | 2,742 | -14 |
| 28 Aug 2026, 20:24 | 2,756 | -12 |
| 26 Aug 2026, 05:45 | 2,768 | -9 |
| 23 Aug 2026, 06:46 | 2,777 | -1 |
| 22 Aug 2026, 03:15 | 2,778 | 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.
@fazelnazarigram · 39,143
Telegram ranks this channel #27 of 69 here — alongside 68 others — read 31 August 2026
@foroogh_shamloo · 51,906
Telegram ranks this channel #30 of 85 here — alongside 84 others — read 24 August 2026
@mehdidarabichannel · 24,227
Telegram ranks this channel #31 of 41 here — alongside 40 others — read 16 September 2026
@nazaninenshaei · 30,750
Telegram ranks this channel #53 of 77 here — alongside 76 others — read 7 September 2026
@radio_chehraziii · 62,139
Telegram ranks this channel #79 of 94 here — alongside 93 others — read 22 August 2026
@radiolimoo · 36,348
Telegram ranks this channel #81 of 85 here — alongside 84 others — read 1 September 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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“"وآله"” (@Vaaaaleh), 2,698 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/Vaaaaleh.
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.