Channel
Final Materials | Mosab
@finalmaterial
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,515subscribers
+50 since we began measuring on 14 September 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001707690844 |
|---|---|
| Type | Channel |
| Username | @finalmaterial |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 September 2026 |
| Last confirmed live | 1 November 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 1 November 2026 |
| On Telegram | t.me/finalmaterial |
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 2 October 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 1 Nov 2026, 05:31 | 2,515 | -4 |
| 29 Oct 2026, 09:16 | 2,519 | +5 |
| 26 Oct 2026, 14:27 | 2,514 | +2 |
| 23 Oct 2026, 13:48 | 2,512 | +6 |
| 20 Oct 2026, 05:09 | 2,506 | +3 |
| 17 Oct 2026, 05:56 | 2,503 | +4 |
| 13 Oct 2026, 20:27 | 2,499 | +4 |
| 8 Oct 2026, 05:38 | 2,495 | +10 |
| 2 Oct 2026, 00:39 | 2,485 | +19 |
| 16 Sept 2026, 05:59 | 2,466 | +1 |
| 16 Sept 2026, 00:39 | 2,465 | no change |
| 14 Sept 2026, 19:47 | 2,465 | 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.
@Dramropedia · 22,472
Telegram ranks this channel #4 of 86 here — alongside 85 others — read 21 September 2026
@Theoils · 23,442
Telegram ranks this channel #12 of 73 here — alongside 72 others — read 18 September 2026
@alehssan_serial · 24,772
Telegram ranks this channel #13 of 88 here — alongside 87 others — read 16 September 2026
@alehssan_medicine · 21,549
Telegram ranks this channel #18 of 84 here — alongside 83 others — read 24 September 2026
@Prof_adlan_local · 19,586
Telegram ranks this channel #23 of 82 here — alongside 81 others — read 1 October 2026
@adlanmedicine · 25,328
Telegram ranks this channel #28 of 82 here — alongside 81 others — read 14 September 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 1 November 2026 — this entry's latest reading, not the date you are reading this.
“Final Materials | Mosab” (@finalmaterial), 2,515 subscribers as measured 1 November 2026. Telegram Register, tgregister.com/channel/finalmaterial.
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.