
Channel
golbang_shajarian
@golbang_shajarian
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,663subscribers
+93 since we began measuring on 21 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001400495657 |
|---|---|
| Type | Channel |
| Username | @golbang_shajarian |
| Created | Between 1 April 2019 and 30 November 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 September 2026 |
| Last confirmed live | 15 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 15 November 2026 |
| On Telegram | t.me/golbang_shajarian |
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 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 |
|---|---|---|
| 15 Nov 2026, 11:05 | 3,663 | +1 |
| 10 Nov 2026, 12:45 | 3,662 | -1 |
| 7 Nov 2026, 01:40 | 3,663 | -3 |
| 4 Nov 2026, 04:10 | 3,666 | -3 |
| 31 Oct 2026, 22:36 | 3,669 | -1 |
| 28 Oct 2026, 16:55 | 3,670 | +3 |
| 25 Oct 2026, 08:10 | 3,667 | -4 |
| 22 Oct 2026, 08:41 | 3,671 | +3 |
| 18 Oct 2026, 13:26 | 3,668 | +1 |
| 15 Oct 2026, 20:26 | 3,667 | +5 |
| 12 Oct 2026, 17:41 | 3,662 | +14 |
| 5 Oct 2026, 20:00 | 3,648 | +13 |
| 28 Sept 2026, 14:22 | 3,635 | +29 |
| 18 Sept 2026, 18:18 | 3,606 | +2 |
| 14 Sept 2026, 12:42 | 3,604 | +4 |
| 10 Sept 2026, 21:36 | 3,600 | +13 |
| 7 Sept 2026, 22:41 | 3,587 | no change |
| 5 Sept 2026, 14:21 | 3,587 | +7 |
| 1 Sept 2026, 07:37 | 3,580 | +1 |
| 29 Aug 2026, 00:25 | 3,579 | 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.
@shajarian_home · 64,094
Telegram ranks this channel #9 of 94 here — alongside 93 others — read 21 August 2026
@Khosousi · 65,602
Telegram ranks this channel #22 of 89 here — alongside 88 others — read 21 August 2026
@koronmusic · 28,765
Telegram ranks this channel #25 of 96 here — alongside 95 others — read 9 September 2026
@Dreaam_life · 72,626
Telegram ranks this channel #48 of 54 here — alongside 53 others — read 25 August 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 15 November 2026 — this entry's latest reading, not the date you are reading this.
“golbang_shajarian” (@golbang_shajarian), 3,663 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/golbang_shajarian.
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.