Channel
سخن مرد خدا
@marde_khoda121
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,392subscribers
+6 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001670397244 |
|---|---|
| Type | Channel |
| Username | @marde_khoda121 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/marde_khoda121 |
Topic
Religion — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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 |
|---|---|---|
| 5 Nov 2026, 21:08 | 2,392 | +1 |
| 31 Oct 2026, 10:20 | 2,391 | +2 |
| 28 Oct 2026, 05:00 | 2,389 | +3 |
| 25 Oct 2026, 10:19 | 2,386 | +2 |
| 22 Oct 2026, 05:29 | 2,384 | +4 |
| 18 Oct 2026, 23:17 | 2,380 | +3 |
| 12 Oct 2026, 16:09 | 2,377 | +5 |
| 5 Oct 2026, 17:15 | 2,372 | +4 |
| 28 Sept 2026, 11:37 | 2,368 | +8 |
| 17 Sept 2026, 00:43 | 2,360 | no change |
| 15 Sept 2026, 20:38 | 2,360 | -2 |
| 12 Sept 2026, 03:55 | 2,362 | +1 |
| 7 Sept 2026, 19:59 | 2,361 | -4 |
| 3 Sept 2026, 00:18 | 2,365 | -22 |
| 30 Aug 2026, 11:28 | 2,387 | +1 |
| 27 Aug 2026, 06:30 | 2,386 | 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.
@ShadmehrAghilio · 30,540
Telegram ranks this channel #38 of 48 here — alongside 47 others — read 5 September 2026
@OnlineConversationSchool_Film · 21,493
Telegram ranks this channel #61 of 80 here — alongside 79 others — read 25 September 2026
@semahos · 46,246
Telegram ranks this channel #71 of 81 here — alongside 80 others — read 27 August 2026
@dnapluse · 29,859
Telegram ranks this channel #75 of 77 here — alongside 76 others — read 9 September 2026
@semohos1 · 25,528
Telegram ranks this channel #76 of 86 here — alongside 85 others — read 13 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“سخن مرد خدا” (@marde_khoda121), 2,392 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/marde_khoda121.
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.