Channel
قسم obstetrics &Gyne للدفعة الخامسة
@Gyn_Obs_5th
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,795subscribers
+53 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001663117152 |
|---|---|
| Type | Channel |
| Username | @Gyn_Obs_5th |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 23 September 2026 |
| Last confirmed live | 23 September 2026 |
| Measurements held | 13 |
| On Telegram | t.me/Gyn_Obs_5th |
Topic
Education — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 79% 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 |
|---|---|---|
| 23 Sept 2026, 15:28 | 1,795 | no change |
| 18 Sept 2026, 09:01 | 1,795 | +14 |
| 14 Sept 2026, 10:38 | 1,781 | +8 |
| 11 Sept 2026, 06:37 | 1,773 | +6 |
| 2 Sept 2026, 11:35 | 1,767 | +1 |
| 30 Aug 2026, 07:07 | 1,766 | -1 |
| 27 Aug 2026, 08:48 | 1,767 | +4 |
| 24 Aug 2026, 04:35 | 1,763 | +4 |
| 17 Aug 2026, 20:37 | 1,759 | +5 |
| 14 Aug 2026, 13:28 | 1,754 | +6 |
| 11 Aug 2026, 07:57 | 1,748 | +5 |
| 8 Aug 2026, 00:08 | 1,743 | +1 |
| 7 Aug 2026, 15:45 | 1,742 | 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.
@pediatricaljoky · 21,762
Telegram ranks this channel #16 of 93 here — alongside 92 others — read 22 September 2026
@pedia8 · 22,915
Telegram ranks this channel #19 of 96 here — alongside 95 others — read 19 September 2026
@mypharmacyta · 26,041
Telegram ranks this channel #44 of 83 here — alongside 82 others — read 13 September 2026
@Dr_Waleed_Al_Sibakhi · 50,811
Telegram ranks this channel #63 of 93 here — alongside 92 others — read 25 August 2026
@Medical_MhM · 85,555
Telegram ranks this channel #68 of 81 here — alongside 80 others — read 5 September 2026
@Dopamine_Clinical2025 · 55,703
Telegram ranks this channel #76 of 90 here — alongside 89 others — read 23 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 23 September 2026 — this entry's latest reading, not the date you are reading this.
“قسم obstetrics &Gyne للدفعة الخامسة” (@Gyn_Obs_5th), 1,795 subscribers as measured 23 September 2026. Telegram Register, tgregister.com/channel/Gyn_Obs_5th.
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.