Channel
کانال شعرهای زیبا و ناب
@najisher
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,701subscribers
+19 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001003091398 |
|---|---|
| Type | Channel |
| Username | @najisher |
| Created | Between 1 September 2015 and 31 December 2015 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/najisher |
Topic
Literature — 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 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 15:40 | 3,701 | -4 |
| 11 Sept 2026, 18:01 | 3,705 | -3 |
| 6 Sept 2026, 23:41 | 3,708 | no change |
| 6 Sept 2026, 19:20 | 3,708 | -2 |
| 30 Aug 2026, 12:57 | 3,710 | +7 |
| 27 Aug 2026, 04:38 | 3,703 | +12 |
| 21 Aug 2026, 04:42 | 3,691 | -8 |
| 17 Aug 2026, 22:03 | 3,699 | +2 |
| 15 Aug 2026, 07:28 | 3,697 | +6 |
| 12 Aug 2026, 05:39 | 3,691 | -1 |
| 9 Aug 2026, 12:02 | 3,692 | +10 |
| 5 Aug 2026, 18:40 | 3,682 | 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.
@sayvangagli9 · 30,508
Telegram ranks this channel #29 of 48 here — alongside 47 others — read 9 September 2026
@hoshang_ebtehhaj · 82,642
Telegram ranks this channel #29 of 88 here — alongside 87 others — read 18 August 2026
@sokhen_nab · 76,605
Telegram ranks this channel #34 of 80 here — alongside 79 others — read 19 August 2026
@Pe_mesle_paeiz0 · 25,263
Telegram ranks this channel #51 of 76 here — alongside 75 others — read 14 September 2026
@foroghfarokhzad · 45,057
Telegram ranks this channel #52 of 91 here — alongside 90 others — read 27 August 2026
@remixmoon · 130,335
Telegram ranks this channel #57 of 75 here — alongside 74 others — read 14 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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“کانال شعرهای زیبا و ناب” (@najisher), 3,701 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/najisher.
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.