Channel
کربلایی وحیددبیر
@Dabir_vahid110
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,338subscribers
-18 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001016047240 |
|---|---|
| Type | Channel |
| Username | @Dabir_vahid110 |
| Created | Between 1 December 2015 and 31 March 2016 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 October 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 3 times, most recently 5 November 2026 |
| On Telegram | t.me/Dabir_vahid110 |
Topic
Religion — 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 100% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Oct 2026, 13:58 | 1,338 | +1 |
| 21 Oct 2026, 09:15 | 1,337 | -4 |
| 18 Oct 2026, 10:06 | 1,341 | +2 |
| 15 Oct 2026, 01:21 | 1,339 | -1 |
| 12 Oct 2026, 04:20 | 1,340 | +3 |
| 5 Oct 2026, 07:40 | 1,337 | -8 |
| 1 Oct 2026, 03:08 | 1,345 | no change |
| 27 Sept 2026, 03:39 | 1,345 | -8 |
| 17 Sept 2026, 20:39 | 1,353 | -1 |
| 10 Sept 2026, 01:36 | 1,354 | +1 |
| 4 Sept 2026, 15:58 | 1,353 | -2 |
| 1 Sept 2026, 04:43 | 1,355 | +2 |
| 26 Aug 2026, 09:15 | 1,353 | -1 |
| 23 Aug 2026, 14:27 | 1,354 | -1 |
| 20 Aug 2026, 02:44 | 1,355 | -1 |
| 16 Aug 2026, 19:22 | 1,356 | +2 |
| 13 Aug 2026, 01:44 | 1,354 | +3 |
| 9 Aug 2026, 19:32 | 1,351 | -5 |
| 5 Aug 2026, 22:12 | 1,356 | 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.
@Mreza_Danaei · 19,187
Telegram ranks this channel #23 of 65 here — alongside 64 others — read 2 October 2026
@eeydanian315 · 22,168
Telegram ranks this channel #26 of 92 here — alongside 91 others — read 21 September 2026
@naseri205 · 23,146
Telegram ranks this channel #32 of 94 here — alongside 93 others — read 25 September 2026
@amirhoseinhazrati128 · 40,118
Telegram ranks this channel #32 of 94 here — alongside 93 others — read 31 August 2026
@morteza_yebor313 · 73,220
Telegram ranks this channel #33 of 92 here — alongside 91 others — read 20 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 30 October 2026 — this entry's latest reading, not the date you are reading this.
“کربلایی وحیددبیر” (@Dabir_vahid110), 1,338 subscribers as measured 30 October 2026. Telegram Register, tgregister.com/channel/Dabir_vahid110.
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.