
Channel
دوره ایکس
@dorehx
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,399subscribers
+78 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001664980237 |
|---|---|
| Type | Channel |
| Username | @dorehx |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 September 2026 |
| Last confirmed live | 25 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 25 October 2026 |
| On Telegram | t.me/dorehx |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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 |
|---|---|---|
| 25 Oct 2026, 13:56 | 3,399 | +1 |
| 22 Oct 2026, 10:56 | 3,398 | +7 |
| 18 Oct 2026, 23:14 | 3,391 | +8 |
| 15 Oct 2026, 13:06 | 3,383 | +5 |
| 12 Oct 2026, 16:11 | 3,378 | +5 |
| 5 Oct 2026, 18:01 | 3,373 | +13 |
| 18 Sept 2026, 19:56 | 3,360 | +9 |
| 14 Sept 2026, 11:39 | 3,351 | -4 |
| 11 Sept 2026, 07:58 | 3,355 | +6 |
| 9 Sept 2026, 00:22 | 3,349 | no change |
| 6 Sept 2026, 06:56 | 3,349 | +9 |
| 1 Sept 2026, 23:16 | 3,340 | +9 |
| 29 Aug 2026, 16:44 | 3,331 | +6 |
| 26 Aug 2026, 09:41 | 3,325 | -4 |
| 19 Aug 2026, 09:24 | 3,329 | +4 |
| 16 Aug 2026, 18:58 | 3,325 | +4 |
| 13 Aug 2026, 05:45 | 3,321 | 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.
@gharavix · 219,898
Telegram ranks this channel #10 of 72 here — alongside 71 others — read 13 August 2026
@jazb_dokhtar · 23,979
Telegram ranks this channel #24 of 79 here — alongside 78 others — read 17 September 2026
@dhvmen · 26,127
Telegram ranks this channel #31 of 69 here — alongside 68 others — read 12 September 2026
@ravanemard · 55,649
Telegram ranks this channel #33 of 78 here — alongside 77 others — read 23 August 2026
@HamidRezaeiAcademy · 75,739
Telegram ranks this channel #38 of 76 here — alongside 75 others — read 19 August 2026
This channel appears in 5 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 25 October 2026 — this entry's latest reading, not the date you are reading this.
“دوره ایکس” (@dorehx), 3,399 subscribers as measured 25 October 2026. Telegram Register, tgregister.com/channel/dorehx.
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.