Channel
مقرر الأوبس 👩🍼💙🌸
@NilevalleyObs
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,783subscribers
+93 since we began measuring on 1 September 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001977706555 |
|---|---|
| Type | Channel |
| Username | @NilevalleyObs |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 24 September 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/NilevalleyObs |
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 24 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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 |
|---|---|---|
| 8 Nov 2026, 19:07 | 1,783 | +3 |
| 5 Nov 2026, 17:18 | 1,780 | +2 |
| 2 Nov 2026, 12:09 | 1,778 | +3 |
| 30 Oct 2026, 21:36 | 1,775 | +2 |
| 27 Oct 2026, 19:41 | 1,773 | +6 |
| 24 Oct 2026, 17:59 | 1,767 | +10 |
| 22 Oct 2026, 01:38 | 1,757 | +1 |
| 15 Oct 2026, 07:46 | 1,756 | +3 |
| 12 Oct 2026, 12:40 | 1,753 | +9 |
| 6 Oct 2026, 02:15 | 1,744 | +7 |
| 29 Sept 2026, 01:37 | 1,737 | +19 |
| 24 Sept 2026, 15:47 | 1,718 | no change |
| 18 Sept 2026, 21:18 | 1,718 | +16 |
| 14 Sept 2026, 14:40 | 1,702 | +3 |
| 11 Sept 2026, 00:19 | 1,699 | +1 |
| 6 Sept 2026, 00:18 | 1,698 | +8 |
| 1 Sept 2026, 06:30 | 1,690 | 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.
@sdgtbookstore · 35,234
Telegram ranks this channel #2 of 74 here — alongside 73 others — read 24 September 2026
@Kibreet · 37,891
Telegram ranks this channel #14 of 87 here — alongside 86 others — read 1 September 2026
@medicincollecation · 20,025
Telegram ranks this channel #46 of 88 here — alongside 87 others — read 1 October 2026
@gynaandobsdrnadine · 28,246
Telegram ranks this channel #56 of 67 here — alongside 66 others — read 10 September 2026
@Medical_MhM · 85,228
Telegram ranks this channel #73 of 81 here — alongside 80 others — read 5 September 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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“مقرر الأوبس 👩🍼💙🌸” (@NilevalleyObs), 1,783 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/NilevalleyObs.
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.