Channel
ضِمـَاد
@notdy1
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,256subscribers
-244 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001939745367 |
|---|---|
| Type | Channel |
| Username | @notdy1 |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/notdy1 |
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 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, 09:39 | 3,256 | -16 |
| 2 Nov 2026, 22:47 | 3,272 | -10 |
| 31 Oct 2026, 02:08 | 3,282 | -9 |
| 28 Oct 2026, 12:08 | 3,291 | -7 |
| 25 Oct 2026, 06:40 | 3,298 | -3 |
| 22 Oct 2026, 12:05 | 3,301 | -8 |
| 19 Oct 2026, 11:56 | 3,309 | -7 |
| 16 Oct 2026, 20:55 | 3,316 | -11 |
| 13 Oct 2026, 11:06 | 3,327 | -17 |
| 7 Oct 2026, 07:22 | 3,344 | -11 |
| 30 Sept 2026, 03:19 | 3,355 | -41 |
| 15 Sept 2026, 20:18 | 3,396 | -17 |
| 12 Sept 2026, 13:36 | 3,413 | -21 |
| 8 Sept 2026, 21:04 | 3,434 | no change |
| 8 Sept 2026, 14:21 | 3,434 | -11 |
| 3 Sept 2026, 11:56 | 3,445 | -10 |
| 31 Aug 2026, 02:18 | 3,455 | -8 |
| 27 Aug 2026, 17:15 | 3,463 | -5 |
| 24 Aug 2026, 21:38 | 3,468 | -10 |
| 20 Aug 2026, 21:57 | 3,478 | 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.
@Nahwy · 320,124
Telegram ranks this channel #2 of 49 here — alongside 48 others — read 10 August 2026
@uubbbv · 46,233
Telegram ranks this channel #10 of 41 here — alongside 40 others — read 25 August 2026
@FTFF0 · 43,414
Telegram ranks this channel #15 of 36 here — alongside 35 others — read 29 August 2026
@Iran_Bel_Arabi · 53,808
Telegram ranks this channel #16 of 50 here — alongside 49 others — read 22 August 2026
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total, of which the 4 where it ranks highest are shown above. 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.
“ضِمـَاد” (@notdy1), 3,256 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/notdy1.
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.