Channel
تَعلومُهم
@ta3lomohm
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,609subscribers
-71 since we began measuring on 21 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001284645200 |
|---|---|
| Type | Channel |
| Username | @ta3lomohm |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/ta3lomohm |
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 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 |
|---|---|---|
| 5 Nov 2026, 10:31 | 3,609 | -5 |
| 2 Nov 2026, 02:38 | 3,614 | -1 |
| 30 Oct 2026, 07:59 | 3,615 | -4 |
| 27 Oct 2026, 00:27 | 3,619 | -1 |
| 24 Oct 2026, 04:20 | 3,620 | -3 |
| 20 Oct 2026, 20:19 | 3,623 | -1 |
| 17 Oct 2026, 18:01 | 3,624 | -2 |
| 15 Oct 2026, 03:50 | 3,626 | -6 |
| 11 Oct 2026, 18:41 | 3,632 | -6 |
| 4 Oct 2026, 23:02 | 3,638 | -11 |
| 25 Sept 2026, 18:16 | 3,649 | -17 |
| 12 Sept 2026, 08:56 | 3,666 | -2 |
| 7 Sept 2026, 22:21 | 3,668 | -3 |
| 7 Sept 2026, 00:30 | 3,671 | no change |
| 3 Sept 2026, 03:10 | 3,671 | -7 |
| 31 Aug 2026, 07:54 | 3,678 | +3 |
| 25 Aug 2026, 03:08 | 3,675 | -4 |
| 22 Aug 2026, 04:48 | 3,679 | -1 |
| 21 Aug 2026, 19:45 | 3,680 | 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.
@Kodurat3 · 64,482
Telegram ranks this channel #11 of 66 here — alongside 65 others — read 22 August 2026
@mathsoso_1430a · 27,375
Telegram ranks this channel #36 of 95 here — alongside 94 others — read 12 September 2026
@E7sas2039 · 22,296
Telegram ranks this channel #40 of 94 here — alongside 93 others — read 20 September 2026
@flametowardsthetop · 41,901
Telegram ranks this channel #65 of 92 here — alongside 91 others — read 29 August 2026
@EduTechno21 · 62,407
Telegram ranks this channel #65 of 92 here — alongside 91 others — read 21 August 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.
“تَعلومُهم” (@ta3lomohm), 3,609 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/ta3lomohm.
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.