Channel
Noorlight777💜🦋
@noorlight777
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,641subscribers
-41 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001647298974 |
|---|---|
| Type | Channel |
| Username | @noorlight777 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/noorlight777 |
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 98% 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 |
|---|---|---|
| 19 Sept 2026, 01:40 | 3,641 | -4 |
| 14 Sept 2026, 17:57 | 3,645 | -9 |
| 11 Sept 2026, 06:55 | 3,654 | -4 |
| 7 Sept 2026, 13:01 | 3,658 | no change |
| 6 Sept 2026, 00:19 | 3,658 | -1 |
| 1 Sept 2026, 17:27 | 3,659 | -8 |
| 29 Aug 2026, 16:26 | 3,667 | -7 |
| 26 Aug 2026, 09:41 | 3,674 | +6 |
| 23 Aug 2026, 10:14 | 3,668 | -8 |
| 20 Aug 2026, 05:23 | 3,676 | -3 |
| 17 Aug 2026, 12:13 | 3,679 | -4 |
| 14 Aug 2026, 11:23 | 3,683 | +1 |
| 13 Aug 2026, 02:45 | 3,682 | 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.
@Mazdafar · 43,170
Telegram ranks this channel #12 of 67 here — alongside 66 others — read 28 August 2026
@mantraa_music · 29,515
Telegram ranks this channel #19 of 83 here — alongside 82 others — read 8 September 2026
@zamin_takhte · 51,266
Telegram ranks this channel #23 of 76 here — alongside 75 others — read 7 September 2026
@dnapluse · 29,146
Telegram ranks this channel #29 of 77 here — alongside 76 others — read 9 September 2026
@satvica · 30,525
Telegram ranks this channel #32 of 85 here — alongside 84 others — read 7 September 2026
@laminor_text_music · 153,361
Telegram ranks this channel #56 of 66 here — alongside 65 others — read 13 August 2026
@soheilsangarzadeh2 · 49,123
Telegram ranks this channel #79 of 86 here — alongside 85 others — read 26 August 2026
This channel appears in 7 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Noorlight777💜🦋” (@noorlight777), 3,641 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/noorlight777.
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.