Channel
پرواز روح || برون فکنی
@kanalshahin
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,799subscribers
+200 since we began measuring on 23 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001528643662 |
|---|---|
| Type | Channel |
| Username | @kanalshahin |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 September 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/kanalshahin |
Topic
Religion — 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 53% 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 |
|---|---|---|
| 8 Nov 2026, 11:07 | 3,799 | +8 |
| 2 Nov 2026, 06:55 | 3,791 | +6 |
| 30 Oct 2026, 07:56 | 3,785 | +12 |
| 26 Oct 2026, 23:39 | 3,773 | +10 |
| 24 Oct 2026, 02:00 | 3,763 | +7 |
| 21 Oct 2026, 01:07 | 3,756 | +13 |
| 18 Oct 2026, 02:19 | 3,743 | +20 |
| 11 Oct 2026, 06:21 | 3,723 | +15 |
| 4 Oct 2026, 22:15 | 3,708 | +12 |
| 25 Sept 2026, 16:39 | 3,696 | +31 |
| 16 Sept 2026, 18:22 | 3,665 | -4 |
| 13 Sept 2026, 05:01 | 3,669 | +20 |
| 9 Sept 2026, 04:40 | 3,649 | +20 |
| 7 Sept 2026, 13:36 | 3,629 | no change |
| 3 Sept 2026, 10:16 | 3,629 | +12 |
| 31 Aug 2026, 09:14 | 3,617 | +8 |
| 27 Aug 2026, 23:26 | 3,609 | +9 |
| 25 Aug 2026, 00:13 | 3,600 | +1 |
| 23 Aug 2026, 19:30 | 3,599 | 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.
@erfanvametafizik · 33,475
Telegram ranks this channel #16 of 86 here — alongside 85 others — read 3 September 2026
@fereshte_irannezhadd · 24,878
Telegram ranks this channel #27 of 55 here — alongside 54 others — read 14 September 2026
@jadouye_angels · 35,529
Telegram ranks this channel #30 of 71 here — alongside 70 others — read 2 September 2026
@booksofus · 51,705
Telegram ranks this channel #60 of 84 here — alongside 83 others — read 23 August 2026
@Roohe_bartar · 30,948
Telegram ranks this channel #61 of 93 here — alongside 92 others — read 7 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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“پرواز روح || برون فکنی” (@kanalshahin), 3,799 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/kanalshahin.
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.