Channel
722
@bnthamed
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
393subscribers
-13 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002038797062 |
|---|---|
| Type | Channel |
| Username | @bnthamed |
| Description | قل خَيْرًا أو اصمت💐. @asrill_bot https://t.me/zIxlzxl |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 October 2026 |
| Last confirmed live | 13 October 2026 |
| Measurements held | 7 |
| On Telegram | t.me/bnthamed |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 13 October 2026 and assigned it the closest of 31 fixed categories, at 90% 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 |
|---|---|---|
| 13 Oct 2026, 04:30 | 393 | no change |
| 11 Oct 2026, 07:16 | 393 | -1 |
| 30 Sept 2026, 21:17 | 394 | -5 |
| 11 Sept 2026, 14:37 | 399 | -1 |
| 2 Sept 2026, 03:47 | 400 | -3 |
| 25 Aug 2026, 23:05 | 403 | -3 |
| 18 Aug 2026, 20:15 | 406 | 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.
@mimaox · 18,861
Telegram ranks this channel #12 of 52 here — alongside 51 others — read 3 October 2026
@n0n99n · 27,832
Telegram ranks this channel #18 of 64 here — alongside 63 others — read 17 September 2026
@r94hr · 26,200
Telegram ranks this channel #18 of 84 here — alongside 83 others — read 12 September 2026
@forqanwassam313 · 31,298
Telegram ranks this channel #23 of 59 here — alongside 58 others — read 5 September 2026
@wa2004jd · 23,579
Telegram ranks this channel #33 of 63 here — alongside 62 others — read 17 September 2026
@Ayus8hi · 24
Telegram ranks this channel #36 of 54 here — alongside 53 others — read 22 September 2026
@IlAli9 · 22,952
Telegram ranks this channel #37 of 49 here — alongside 48 others — read 19 September 2026
@tillkv · 83,341
Telegram ranks this channel #39 of 57 here — alongside 56 others — read 18 August 2026
@hoari2004 · 21,346
Telegram ranks this channel #40 of 52 here — alongside 51 others — read 26 September 2026
This channel appears in 9 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 13 October 2026 — this entry's latest reading, not the date you are reading this.
“722” (@bnthamed), 393 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/bnthamed.
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.