
Channel
الامتحان الانكليزي الوطني_خطة وحلول محمد البابلي
@mohammad_al_bably360
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
7,138subscribers
+95 since we began measuring on 22 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002077425671 |
|---|---|
| Type | Channel |
| Username | @mohammad_al_bably360 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 27 August 2026 |
| Last confirmed live | 23 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 23 October 2026 |
| On Telegram | t.me/mohammad_al_bably360 |
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 12 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Oct 2026, 11:25 | 7,138 | -4 |
| 20 Oct 2026, 08:59 | 7,142 | +12 |
| 17 Oct 2026, 05:47 | 7,130 | +1 |
| 14 Oct 2026, 09:28 | 7,129 | -1 |
| 10 Oct 2026, 21:59 | 7,130 | -8 |
| 5 Oct 2026, 00:58 | 7,138 | +5 |
| 25 Sept 2026, 21:19 | 7,133 | +19 |
| 17 Sept 2026, 04:38 | 7,114 | +10 |
| 13 Sept 2026, 01:56 | 7,104 | +19 |
| 9 Sept 2026, 06:56 | 7,085 | +18 |
| 3 Sept 2026, 19:16 | 7,067 | +1 |
| 31 Aug 2026, 03:42 | 7,066 | +10 |
| 28 Aug 2026, 06:34 | 7,056 | +14 |
| 27 Aug 2026, 11:37 | 7,042 | no change |
| 25 Aug 2026, 13:23 | 7,042 | -1 |
| 22 Aug 2026, 06:15 | 7,043 | 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.
@flakavfsk · 49,886
Telegram ranks this channel #3 of 82 here — alongside 81 others — read 25 August 2026
@samahh2024 · 19,333
Telegram ranks this channel #11 of 71 here — alongside 70 others — read 2 October 2026
@saadinelt · 111,912
Telegram ranks this channel #11 of 77 here — alongside 76 others — read 22 August 2026
@diaeabdulzahr · 63,965
Telegram ranks this channel #12 of 89 here — alongside 88 others — read 22 August 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 23 October 2026 — this entry's latest reading, not the date you are reading this.
“الامتحان الانكليزي الوطني_خطة وحلول محمد البابلي” (@mohammad_al_bably360), 7,138 subscribers as measured 23 October 2026. Telegram Register, tgregister.com/channel/mohammad_al_bably360.
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.