Channel
نورا🌙
@nooramon
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,621subscribers
-199 since we began measuring on 30 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002211007472 |
|---|---|
| Type | Channel |
| Username | @nooramon |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 1 November 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 1 November 2026 |
| On Telegram | t.me/nooramon |
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 16 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 |
|---|---|---|
| 1 Nov 2026, 23:36 | 3,621 | -9 |
| 29 Oct 2026, 19:17 | 3,630 | -10 |
| 26 Oct 2026, 21:49 | 3,640 | -9 |
| 23 Oct 2026, 19:27 | 3,649 | -11 |
| 20 Oct 2026, 09:00 | 3,660 | -8 |
| 17 Oct 2026, 05:59 | 3,668 | -10 |
| 14 Oct 2026, 12:38 | 3,678 | -8 |
| 10 Oct 2026, 13:55 | 3,686 | -19 |
| 4 Oct 2026, 18:59 | 3,705 | -35 |
| 25 Sept 2026, 04:00 | 3,740 | -35 |
| 16 Sept 2026, 11:01 | 3,775 | -5 |
| 12 Sept 2026, 05:59 | 3,780 | -8 |
| 8 Sept 2026, 04:01 | 3,788 | -18 |
| 6 Sept 2026, 19:45 | 3,806 | no change |
| 2 Sept 2026, 15:06 | 3,806 | -14 |
| 30 Aug 2026, 10:15 | 3,820 | 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.
@Camentic · 19,403
Telegram ranks this channel #8 of 50 here — alongside 49 others — read 28 September 2026
@Amirtataloo7 · 26,434
Telegram ranks this channel #25 of 52 here — alongside 51 others — read 12 September 2026
@DNYXW880 · 32,374
Telegram ranks this channel #30 of 53 here — alongside 52 others — read 30 August 2026
@Moharraz_1 · 28,022
Telegram ranks this channel #36 of 87 here — alongside 86 others — read 10 September 2026
@project_bartarr · 28,673
Telegram ranks this channel #64 of 66 here — alongside 65 others — read 7 September 2026
@adhdbefarsi · 22,179
Telegram ranks this channel #65 of 82 here — alongside 81 others — read 19 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 1 November 2026 — this entry's latest reading, not the date you are reading this.
“نورا🌙” (@nooramon), 3,621 subscribers as measured 1 November 2026. Telegram Register, tgregister.com/channel/nooramon.
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.