Channel
استخدامی دبیری زیست راهینو
@dabiri_zist1403
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,203subscribers
-27 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 | -1001911441927 |
|---|---|
| Type | Channel |
| Username | @dabiri_zist1403 |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 October 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/dabiri_zist1403 |
Topic
Education — 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 4 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 |
|---|---|---|
| 7 Nov 2026, 00:36 | 1,203 | -5 |
| 3 Nov 2026, 14:55 | 1,208 | -1 |
| 28 Oct 2026, 00:08 | 1,209 | -2 |
| 24 Oct 2026, 23:45 | 1,211 | +1 |
| 21 Oct 2026, 20:57 | 1,210 | -1 |
| 18 Oct 2026, 22:40 | 1,211 | +1 |
| 15 Oct 2026, 23:31 | 1,210 | -2 |
| 6 Oct 2026, 21:15 | 1,212 | -1 |
| 4 Oct 2026, 03:21 | 1,213 | no change |
| 29 Sept 2026, 18:56 | 1,213 | -6 |
| 19 Sept 2026, 05:01 | 1,219 | +1 |
| 14 Sept 2026, 10:21 | 1,218 | -5 |
| 10 Sept 2026, 15:19 | 1,223 | -4 |
| 1 Sept 2026, 08:35 | 1,227 | -1 |
| 29 Aug 2026, 16:33 | 1,228 | -1 |
| 27 Aug 2026, 02:38 | 1,229 | -1 |
| 26 Aug 2026, 05:15 | 1,230 | 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.
@estekhdamfor1 · 19,038
Telegram ranks this channel #20 of 82 here — alongside 81 others — read 5 October 2026
@Drjomepor_e · 19,057
Telegram ranks this channel #62 of 83 here — alongside 82 others — read 3 October 2026
@Takestekhdammm · 28,268
Telegram ranks this channel #64 of 83 here — alongside 82 others — read 9 September 2026
@akhbareestekhdami · 51,120
Telegram ranks this channel #66 of 80 here — alongside 79 others — read 26 August 2026
@olumpezeshkii1400 · 32,129
Telegram ranks this channel #85 of 93 here — alongside 92 others — read 5 September 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“استخدامی دبیری زیست راهینو” (@dabiri_zist1403), 1,203 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/dabiri_zist1403.
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.