Channel
كلية الهندسة المدنية - جامعة حمص
@madni37
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,660subscribers
-76 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001660215128 |
|---|---|
| Type | Channel |
| Username | @madni37 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 September 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/madni37 |
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 46% 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 Sept 2026, 11:38 | 4,660 | -11 |
| 9 Sept 2026, 23:59 | 4,671 | -12 |
| 4 Sept 2026, 12:20 | 4,683 | -12 |
| 2 Sept 2026, 20:22 | 4,695 | no change |
| 1 Sept 2026, 09:35 | 4,695 | -7 |
| 29 Aug 2026, 18:07 | 4,702 | -8 |
| 26 Aug 2026, 16:03 | 4,710 | -16 |
| 23 Aug 2026, 07:16 | 4,726 | -4 |
| 19 Aug 2026, 23:26 | 4,730 | -9 |
| 16 Aug 2026, 17:15 | 4,739 | +4 |
| 13 Aug 2026, 11:57 | 4,735 | -1 |
| 12 Aug 2026, 23:46 | 4,736 | 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.
@chatincognito · 200,385
Telegram ranks this channel #27 of 35 here — alongside 34 others — read 26 August 2026
@SyriaUN · 47,326
Telegram ranks this channel #34 of 69 here — alongside 68 others — read 26 August 2026
@tigerichancy · 31,080
Telegram ranks this channel #37 of 39 here — alongside 38 others — read 6 September 2026
@SyMOHEASR · 150,282
Telegram ranks this channel #38 of 74 here — alongside 73 others — read 12 August 2026
@syrianjobs2 · 34,552
Telegram ranks this channel #56 of 61 here — alongside 60 others — read 4 September 2026
@Homs24A · 29,858
Telegram ranks this channel #59 of 70 here — alongside 69 others — read 7 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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“كلية الهندسة المدنية - جامعة حمص” (@madni37), 4,660 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/madni37.
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.