Channel
Moath’s Journey 📝.
@MoathForHelp
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,724subscribers
-3 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001974100565 |
|---|---|
| Type | Channel |
| Username | @MoathForHelp |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 24 September 2026 |
| Last confirmed live | 13 October 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 13 October 2026 |
| On Telegram | t.me/MoathForHelp |
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 24 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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, 02:11 | 1,724 | +4 |
| 6 Oct 2026, 12:21 | 1,720 | -5 |
| 29 Sept 2026, 18:18 | 1,725 | +7 |
| 24 Sept 2026, 15:47 | 1,718 | no change |
| 19 Sept 2026, 02:58 | 1,718 | +1 |
| 14 Sept 2026, 19:39 | 1,717 | +2 |
| 11 Sept 2026, 10:17 | 1,715 | +1 |
| 6 Sept 2026, 19:37 | 1,714 | +2 |
| 29 Aug 2026, 18:47 | 1,712 | -1 |
| 26 Aug 2026, 13:21 | 1,713 | +2 |
| 23 Aug 2026, 22:37 | 1,711 | +1 |
| 20 Aug 2026, 06:38 | 1,710 | -13 |
| 17 Aug 2026, 12:46 | 1,723 | -2 |
| 14 Aug 2026, 12:58 | 1,725 | -2 |
| 13 Aug 2026, 10:45 | 1,727 | 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.
@soso44kh · 64,831
Telegram ranks this channel #22 of 62 here — alongside 61 others — read 20 August 2026
@mensa09 · 84,084
Telegram ranks this channel #38 of 88 here — alongside 87 others — read 18 August 2026
@STEP_512 · 138,307
Telegram ranks this channel #42 of 86 here — alongside 85 others — read 13 August 2026
@Acdh_university · 19,068
Telegram ranks this channel #50 of 86 here — alongside 85 others — read 3 October 2026
@SMLE_medicine · 33,090
Telegram ranks this channel #61 of 83 here — alongside 82 others — read 4 September 2026
@Jabal_channel · 38,851
Telegram ranks this channel #64 of 87 here — alongside 86 others — read 31 August 2026
This channel appears in 6 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.
“Moath’s Journey 📝.” (@MoathForHelp), 1,724 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/MoathForHelp.
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.