Channel
سه نتهری کامیار_شنو
@santarikamyar
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,656subscribers
+397 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002107228070 |
|---|---|
| Type | Channel |
| Username | @santarikamyar |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 September 2026 |
| Last confirmed live | 1 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 1 November 2026 |
| On Telegram | t.me/santarikamyar |
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 93% 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 |
|---|---|---|
| 1 Nov 2026, 14:30 | 3,656 | +17 |
| 29 Oct 2026, 08:19 | 3,639 | +19 |
| 22 Oct 2026, 20:19 | 3,620 | +6 |
| 19 Oct 2026, 07:55 | 3,614 | +7 |
| 16 Oct 2026, 08:50 | 3,607 | +1 |
| 12 Oct 2026, 23:39 | 3,606 | +10 |
| 6 Oct 2026, 09:00 | 3,596 | +60 |
| 29 Sept 2026, 03:36 | 3,536 | +94 |
| 15 Sept 2026, 21:22 | 3,442 | +45 |
| 12 Sept 2026, 03:38 | 3,397 | +19 |
| 8 Sept 2026, 23:37 | 3,378 | no change |
| 7 Sept 2026, 21:41 | 3,378 | +29 |
| 2 Sept 2026, 15:06 | 3,349 | +6 |
| 30 Aug 2026, 23:38 | 3,343 | +18 |
| 27 Aug 2026, 20:24 | 3,325 | +12 |
| 24 Aug 2026, 10:16 | 3,313 | +19 |
| 21 Aug 2026, 03:22 | 3,294 | +1 |
| 17 Aug 2026, 21:14 | 3,293 | +22 |
| 14 Aug 2026, 22:13 | 3,271 | +3 |
| 11 Aug 2026, 07:44 | 3,268 | 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.
@NOAZENDE · 22,348
Telegram ranks this channel #3 of 41 here — alongside 40 others — read 19 September 2026
@shnohewal · 32,447
Telegram ranks this channel #38 of 40 here — alongside 39 others — read 5 September 2026
@shnopress_News1 · 20,187
Telegram ranks this channel #43 of 51 here — alongside 50 others — read 28 September 2026
@jomalateangizeshi_1 · 22,157
Telegram ranks this channel #68 of 72 here — alongside 71 others — read 20 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 1 November 2026 — this entry's latest reading, not the date you are reading this.
“سه نتهری کامیار_شنو” (@santarikamyar), 3,656 subscribers as measured 1 November 2026. Telegram Register, tgregister.com/channel/santarikamyar.
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.