Channel
تعليمات دون خوان
@froghani2
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,651subscribers
+64 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001022045236 |
|---|---|
| Type | Channel |
| Username | @froghani2 |
| Created | Between 1 December 2015 and 31 March 2016 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 26 September 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/froghani2 |
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 26 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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 |
|---|---|---|
| 11 Nov 2026, 07:05 | 1,651 | +2 |
| 7 Nov 2026, 06:34 | 1,649 | -2 |
| 4 Nov 2026, 09:30 | 1,651 | +5 |
| 1 Nov 2026, 13:10 | 1,646 | -2 |
| 29 Oct 2026, 16:46 | 1,648 | +2 |
| 26 Oct 2026, 09:46 | 1,646 | +9 |
| 23 Oct 2026, 02:20 | 1,637 | -2 |
| 20 Oct 2026, 03:57 | 1,639 | +3 |
| 17 Oct 2026, 06:38 | 1,636 | +4 |
| 14 Oct 2026, 10:40 | 1,632 | +7 |
| 11 Oct 2026, 00:01 | 1,625 | +5 |
| 5 Oct 2026, 02:36 | 1,620 | +5 |
| 26 Sept 2026, 09:02 | 1,615 | +12 |
| 26 Sept 2026, 03:12 | 1,603 | no change |
| 17 Sept 2026, 18:17 | 1,603 | +1 |
| 13 Sept 2026, 19:21 | 1,602 | +3 |
| 10 Sept 2026, 03:36 | 1,599 | +3 |
| 4 Sept 2026, 20:20 | 1,596 | -4 |
| 31 Aug 2026, 22:37 | 1,600 | +1 |
| 28 Aug 2026, 12:07 | 1,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.
@sokhan_nab53 · 46,640
Telegram ranks this channel #27 of 85 here — alongside 84 others — read 26 August 2026
@Asrar_Daroun · 35,213
Telegram ranks this channel #33 of 73 here — alongside 72 others — read 2 September 2026
@Khodshenasivo · 42,244
Telegram ranks this channel #75 of 97 here — alongside 96 others — read 29 August 2026
@NOSTALGYSONGS · 44,998
Telegram ranks this channel #75 of 84 here — alongside 83 others — read 28 August 2026
@Roohe_bartar · 30,975
Telegram ranks this channel #80 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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“تعليمات دون خوان” (@froghani2), 1,651 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/froghani2.
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.