Channel
UOBCOM | 96 | السچ
@UOBCOM96sch
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,818subscribers
+75 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001666423025 |
|---|---|
| Type | Channel |
| Username | @UOBCOM96sch |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 2 times, most recently 6 November 2026 |
| On Telegram | t.me/UOBCOM96sch |
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 100% 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 |
|---|---|---|
| 3 Nov 2026, 15:36 | 3,818 | +2 |
| 31 Oct 2026, 16:28 | 3,816 | -3 |
| 28 Oct 2026, 10:19 | 3,819 | +4 |
| 25 Oct 2026, 20:56 | 3,815 | +5 |
| 19 Oct 2026, 17:44 | 3,810 | +6 |
| 16 Oct 2026, 09:47 | 3,804 | +3 |
| 13 Oct 2026, 09:28 | 3,801 | +6 |
| 7 Oct 2026, 05:39 | 3,795 | +13 |
| 30 Sept 2026, 10:40 | 3,782 | +23 |
| 15 Sept 2026, 18:17 | 3,759 | -2 |
| 11 Sept 2026, 21:57 | 3,761 | +9 |
| 7 Sept 2026, 07:22 | 3,752 | +1 |
| 6 Sept 2026, 22:52 | 3,751 | no change |
| 2 Sept 2026, 11:33 | 3,751 | +2 |
| 30 Aug 2026, 08:34 | 3,749 | +6 |
| 27 Aug 2026, 06:45 | 3,743 | 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.
@usmle_qbanks · 26,075
Telegram ranks this channel #15 of 41 here — alongside 40 others — read 12 September 2026
@MPTC_1 · 34,568
Telegram ranks this channel #16 of 89 here — alongside 88 others — read 2 September 2026
@Boards_and_Beyond_videos_2023 · 157
Telegram ranks this channel #25 of 83 here — alongside 82 others — read 28 August 2026
@elhusseinyusmle · 44,335
Telegram ranks this channel #30 of 75 here — alongside 74 others — read 28 August 2026
@MedrollB · 22,570
Telegram ranks this channel #36 of 77 here — alongside 76 others — read 21 September 2026
@lraq_ed_maktaba · 46,467
Telegram ranks this channel #66 of 94 here — alongside 93 others — read 27 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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“UOBCOM | 96 | السچ” (@UOBCOM96sch), 3,818 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/UOBCOM96sch.
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.