Channel
شاخه وان ئه حمه دی
@shakhavansene
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,386subscribers
+82 since we began measuring on 30 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001094683156 |
|---|---|
| Type | Channel |
| Username | @shakhavansene |
| Created | Between 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/shakhavansene |
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 51% 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, 20:38 | 2,386 | +5 |
| 2 Nov 2026, 16:16 | 2,381 | +4 |
| 30 Oct 2026, 16:17 | 2,377 | -4 |
| 27 Oct 2026, 10:55 | 2,381 | -1 |
| 24 Oct 2026, 19:29 | 2,382 | +1 |
| 21 Oct 2026, 09:06 | 2,381 | +2 |
| 18 Oct 2026, 07:44 | 2,379 | +2 |
| 12 Oct 2026, 01:18 | 2,377 | +8 |
| 5 Oct 2026, 07:38 | 2,369 | +19 |
| 27 Sept 2026, 01:18 | 2,350 | +13 |
| 17 Sept 2026, 01:32 | 2,337 | no change |
| 15 Sept 2026, 20:01 | 2,337 | +28 |
| 11 Sept 2026, 23:20 | 2,309 | -1 |
| 7 Sept 2026, 10:18 | 2,310 | +9 |
| 2 Sept 2026, 18:48 | 2,301 | -3 |
| 30 Aug 2026, 06:30 | 2,304 | 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.
@delsouzkhaledii · 29,952
Telegram ranks this channel #16 of 65 here — alongside 64 others — read 9 September 2026
@miladahmaditel · 21,812
Telegram ranks this channel #22 of 72 here — alongside 71 others — read 21 September 2026
@farshadaminii · 40,719
Telegram ranks this channel #26 of 55 here — alongside 54 others — read 30 August 2026
@Rahmatazary · 32,519
Telegram ranks this channel #28 of 77 here — alongside 76 others — read 7 September 2026
@Roholakarami · 38,332
Telegram ranks this channel #43 of 62 here — alongside 61 others — read 1 September 2026
@bartaonana · 19,159
Telegram ranks this channel #56 of 61 here — alongside 60 others — read 3 October 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“شاخه وان ئه حمه دی” (@shakhavansene), 2,386 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/shakhavansene.
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.