Channel
Karim Shæri (psy)
@karimsheri
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,383subscribers
+4 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001094825302 |
|---|---|
| Type | Channel |
| Username | @karimsheri |
| Created | Between 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/karimsheri |
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 86% 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 |
|---|---|---|
| 7 Nov 2026, 09:09 | 3,383 | -2 |
| 4 Nov 2026, 17:46 | 3,385 | +1 |
| 1 Nov 2026, 23:59 | 3,384 | +3 |
| 29 Oct 2026, 23:06 | 3,381 | +2 |
| 26 Oct 2026, 23:36 | 3,379 | +3 |
| 23 Oct 2026, 16:16 | 3,376 | -3 |
| 20 Oct 2026, 09:06 | 3,379 | -3 |
| 17 Oct 2026, 19:37 | 3,382 | -2 |
| 14 Oct 2026, 10:59 | 3,384 | +1 |
| 10 Oct 2026, 18:56 | 3,383 | -3 |
| 4 Oct 2026, 22:37 | 3,386 | +9 |
| 25 Sept 2026, 08:00 | 3,377 | -7 |
| 12 Sept 2026, 19:41 | 3,384 | +3 |
| 8 Sept 2026, 23:31 | 3,381 | no change |
| 8 Sept 2026, 10:59 | 3,381 | -5 |
| 3 Sept 2026, 15:17 | 3,386 | +4 |
| 31 Aug 2026, 04:35 | 3,382 | -2 |
| 28 Aug 2026, 13:24 | 3,384 | +4 |
| 25 Aug 2026, 16:13 | 3,380 | -2 |
| 22 Aug 2026, 09:58 | 3,382 | 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.
@keyvanfeizii · 19,554
Telegram ranks this channel #10 of 77 here — alongside 76 others — read 30 September 2026
@sajadafsharian7 · 28,974
Telegram ranks this channel #20 of 76 here — alongside 75 others — read 8 September 2026
@Official_MohsenNamjoo · 43,786
Telegram ranks this channel #38 of 83 here — alongside 82 others — read 27 August 2026
@harroozpodcast · 20,480
Telegram ranks this channel #47 of 63 here — alongside 62 others — read 26 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“Karim Shæri (psy)” (@karimsheri), 3,383 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/karimsheri.
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.