Channel
کانال جزوات و نمونه سوالات دندانپزشکی
@jozvedandanpezeshki
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,245subscribers
+387 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001665826202 |
|---|---|
| Type | Channel |
| Username | @jozvedandanpezeshki |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 5 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/jozvedandanpezeshki |
Topic
Education — 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 100% 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 |
|---|---|---|
| 6 Nov 2026, 08:24 | 4,245 | +9 |
| 3 Nov 2026, 15:20 | 4,236 | +13 |
| 31 Oct 2026, 09:34 | 4,223 | +18 |
| 28 Oct 2026, 06:06 | 4,205 | +16 |
| 25 Oct 2026, 00:45 | 4,189 | +17 |
| 21 Oct 2026, 22:20 | 4,172 | +11 |
| 18 Oct 2026, 07:00 | 4,161 | +38 |
| 15 Oct 2026, 07:19 | 4,123 | +13 |
| 12 Oct 2026, 13:14 | 4,110 | +50 |
| 5 Oct 2026, 21:18 | 4,060 | +42 |
| 28 Sept 2026, 06:19 | 4,018 | +62 |
| 16 Sept 2026, 02:57 | 3,956 | +12 |
| 12 Sept 2026, 16:39 | 3,944 | +3 |
| 8 Sept 2026, 07:36 | 3,941 | +17 |
| 5 Sept 2026, 23:21 | 3,924 | no change |
| 3 Sept 2026, 09:14 | 3,924 | +2 |
| 30 Aug 2026, 22:15 | 3,922 | +15 |
| 27 Aug 2026, 21:05 | 3,907 | +9 |
| 25 Aug 2026, 03:29 | 3,898 | +19 |
| 22 Aug 2026, 06:05 | 3,879 | 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.
@mokale7 · 32,358
Telegram ranks this channel #36 of 69 here — alongside 68 others — read 3 September 2026
@SepehrKhalsep · 21,189
Telegram ranks this channel #63 of 64 here — alongside 63 others — read 23 September 2026
@mohsenchavoshi · 235,106
Telegram ranks this channel #89 of 91 here — alongside 90 others — read 14 August 2026
This channel appears in 3 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“کانال جزوات و نمونه سوالات دندانپزشکی” (@jozvedandanpezeshki), 4,245 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/jozvedandanpezeshki.
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.