Channel
gholamhosainnazari
@Gholamhosainnazari
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,523subscribers
+75 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001051541211 |
|---|---|
| Type | Channel |
| Username | @Gholamhosainnazari |
| Created | Between 1 May 2016 and 28 February 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 September 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/Gholamhosainnazari |
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 99% 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 |
|---|---|---|
| 9 Nov 2026, 02:37 | 4,523 | +2 |
| 5 Nov 2026, 18:08 | 4,521 | -1 |
| 2 Nov 2026, 14:50 | 4,522 | -2 |
| 30 Oct 2026, 04:48 | 4,524 | +4 |
| 27 Oct 2026, 01:29 | 4,520 | -1 |
| 24 Oct 2026, 01:41 | 4,521 | +1 |
| 21 Oct 2026, 09:55 | 4,520 | +2 |
| 18 Oct 2026, 14:55 | 4,518 | +8 |
| 15 Oct 2026, 13:17 | 4,510 | +4 |
| 12 Oct 2026, 09:17 | 4,506 | +5 |
| 5 Oct 2026, 14:17 | 4,501 | +9 |
| 28 Sept 2026, 03:00 | 4,492 | +30 |
| 14 Sept 2026, 04:58 | 4,462 | +6 |
| 10 Sept 2026, 10:59 | 4,456 | +1 |
| 4 Sept 2026, 21:41 | 4,455 | +8 |
| 3 Sept 2026, 20:14 | 4,447 | no change |
| 1 Sept 2026, 06:12 | 4,447 | -1 |
| 28 Aug 2026, 15:30 | 4,448 | 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.
@malorani · 28,545
Telegram ranks this channel #7 of 64 here — alongside 63 others — read 18 September 2026
@mohsenfirouziyan_real · 48,397
Telegram ranks this channel #25 of 74 here — alongside 73 others — read 28 August 2026
@momenzadeh_music · 31,677
Telegram ranks this channel #36 of 83 here — alongside 82 others — read 9 September 2026
@khalijmusic_info · 31,221
Telegram ranks this channel #49 of 81 here — alongside 80 others — read 7 September 2026
This channel appears in 4 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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“gholamhosainnazari” (@Gholamhosainnazari), 4,523 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/Gholamhosainnazari.
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.