Channel
| n a j m e s h a k i b |
@najmeshakib
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,645subscribers
-82 since we began measuring on 2 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001306361499 |
|---|---|
| Type | Channel |
| Username | @najmeshakib |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/najmeshakib |
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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 |
|---|---|---|
| 5 Nov 2026, 19:59 | 3,645 | -5 |
| 2 Nov 2026, 09:34 | 3,650 | -1 |
| 30 Oct 2026, 09:10 | 3,651 | -5 |
| 27 Oct 2026, 06:29 | 3,656 | -2 |
| 24 Oct 2026, 10:26 | 3,658 | -4 |
| 21 Oct 2026, 03:06 | 3,662 | -3 |
| 17 Oct 2026, 19:27 | 3,665 | -2 |
| 15 Oct 2026, 02:07 | 3,667 | -2 |
| 11 Oct 2026, 16:15 | 3,669 | -9 |
| 5 Oct 2026, 07:15 | 3,678 | -20 |
| 26 Sept 2026, 12:56 | 3,698 | -14 |
| 17 Sept 2026, 02:41 | 3,712 | -4 |
| 12 Sept 2026, 22:59 | 3,716 | -8 |
| 6 Sept 2026, 23:25 | 3,724 | no change |
| 3 Sept 2026, 15:15 | 3,724 | -3 |
| 2 Sept 2026, 10:30 | 3,727 | 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.
@rang_zard · 30,016
Telegram ranks this channel #27 of 83 here — alongside 82 others — read 7 September 2026
@fereshtesocialmedia · 4
Telegram ranks this channel #27 of 76 here — alongside 75 others — read 2 September 2026
@Haghbaayan · 42,629
Telegram ranks this channel #29 of 70 here — alongside 69 others — read 4 September 2026
@StoriAm0_5 · 30,536
Telegram ranks this channel #57 of 83 here — alongside 82 others — read 6 September 2026
@yeganegharanli · 32,140
Telegram ranks this channel #77 of 81 here — alongside 80 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“| n a j m e s h a k i b |” (@najmeshakib), 3,645 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/najmeshakib.
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.