
Channel
"پـــنــاه"
@Paanaham
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,612subscribers
-79 since we began measuring on 20 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001941373947 |
|---|---|
| Type | Channel |
| Username | @Paanaham |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 25 September 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/Paanaham |
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 25 September 2026 and assigned it the closest of 31 fixed categories, at 78% 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 |
|---|---|---|
| 16 Nov 2026, 19:09 | 1,612 | -3 |
| 11 Nov 2026, 01:47 | 1,615 | -6 |
| 7 Nov 2026, 08:40 | 1,621 | -5 |
| 4 Nov 2026, 09:35 | 1,626 | -2 |
| 1 Nov 2026, 06:31 | 1,628 | -10 |
| 26 Oct 2026, 12:16 | 1,638 | -2 |
| 23 Oct 2026, 16:15 | 1,640 | -1 |
| 20 Oct 2026, 20:40 | 1,641 | -3 |
| 17 Oct 2026, 21:06 | 1,644 | -7 |
| 14 Oct 2026, 22:00 | 1,651 | -6 |
| 11 Oct 2026, 14:20 | 1,657 | -10 |
| 5 Oct 2026, 12:41 | 1,667 | -3 |
| 27 Sept 2026, 23:57 | 1,670 | -1 |
| 25 Sept 2026, 02:24 | 1,671 | no change |
| 18 Sept 2026, 12:56 | 1,671 | -2 |
| 14 Sept 2026, 07:40 | 1,673 | -3 |
| 10 Sept 2026, 17:18 | 1,676 | -2 |
| 5 Sept 2026, 14:16 | 1,678 | -1 |
| 1 Sept 2026, 13:25 | 1,679 | -2 |
| 30 Aug 2026, 00:04 | 1,681 | 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.
@ranandegi_banovann · 90,597
Telegram ranks this channel #15 of 68 here — alongside 67 others — read 21 August 2026
@Blue_coldroom · 27,791
Telegram ranks this channel #29 of 91 here — alongside 90 others — read 10 September 2026
@cafedezhavu · 104,874
Telegram ranks this channel #54 of 73 here — alongside 72 others — read 20 August 2026
@wain_s · 73,362
Telegram ranks this channel #75 of 80 here — alongside 79 others — read 2 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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“"پـــنــاه"” (@Paanaham), 1,612 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/Paanaham.
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.