Channel
کانال رسمی محمد دل افکار
@mohamaddelafkar
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,499subscribers
+493 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001060738872 |
|---|---|
| Type | Channel |
| Username | @mohamaddelafkar |
| Created | Between 1 May 2016 and 28 February 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/mohamaddelafkar |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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 |
|---|---|---|
| 8 Nov 2026, 12:55 | 5,499 | +18 |
| 5 Nov 2026, 05:48 | 5,481 | +14 |
| 2 Nov 2026, 03:49 | 5,467 | +11 |
| 29 Oct 2026, 17:22 | 5,456 | -4 |
| 26 Oct 2026, 19:10 | 5,460 | -4 |
| 24 Oct 2026, 04:20 | 5,464 | +3 |
| 21 Oct 2026, 15:00 | 5,461 | +7 |
| 18 Oct 2026, 06:20 | 5,454 | +14 |
| 15 Oct 2026, 01:29 | 5,440 | +21 |
| 11 Oct 2026, 12:39 | 5,419 | +31 |
| 4 Oct 2026, 19:19 | 5,388 | +35 |
| 24 Sept 2026, 23:42 | 5,353 | +81 |
| 17 Sept 2026, 02:57 | 5,272 | +36 |
| 13 Sept 2026, 04:40 | 5,236 | +89 |
| 9 Sept 2026, 16:58 | 5,147 | +39 |
| 3 Sept 2026, 22:37 | 5,108 | +17 |
| 1 Sept 2026, 12:11 | 5,091 | no change |
| 31 Aug 2026, 10:36 | 5,091 | +18 |
| 28 Aug 2026, 09:57 | 5,073 | +16 |
| 25 Aug 2026, 04:11 | 5,057 | 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.
@asgharebakerdar · 27,888
Telegram ranks this channel #14 of 71 here — alongside 70 others — read 14 September 2026
@davoodyounesi · 39,732
Telegram ranks this channel #26 of 67 here — alongside 66 others — read 30 August 2026
@asghar_alizade5657 · 55,564
Telegram ranks this channel #36 of 58 here — alongside 57 others — read 29 August 2026
@kormang · 19,134
Telegram ranks this channel #51 of 69 here — alongside 68 others — read 30 September 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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“کانال رسمی محمد دل افکار” (@mohamaddelafkar), 5,499 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/mohamaddelafkar.
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.