Telegram RegisterThe public register of Telegram
Telegram profile photo for نَـيّلوفُر

Channel

نَـيّلوفُر

@Nilof9

On this record: Topic · Growth · Engagement · Citations · Cite this entry

2,098subscribers

+60 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001424011103
TypeChannel
Username@Nilof9
Descriptionحيييّت يمسّيير .
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded20 September 2026
Last confirmed live20 September 2026
Measurements held15
On Telegramt.me/Nilof9

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 20 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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

2,0382,0982,0686 August 2026 — 2,038 subscribers7 August 2026 — 2,039 subscribers10 August 2026 — 2,052 subscribers12 August 2026 — 2,062 subscribers16 August 2026 — 2,069 subscribers19 August 2026 — 2,079 subscribers23 August 2026 — 2,082 subscribers26 August 2026 — 2,080 subscribers29 August 2026 — 2,078 subscribers31 August 2026 — 2,071 subscribers4 September 2026 — 2,072 subscribers10 September 2026 — 2,080 subscribers13 September 2026 — 2,084 subscribers17 September 2026 — 2,098 subscribers20 September 2026 — 2,098 subscribers6 August 202620 September 2026
15 measurements spanning 44 days, net +60. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 2,029–2,107 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
20 Sept 2026, 00:442,098no change
17 Sept 2026, 15:582,098+14
13 Sept 2026, 15:372,084+4
10 Sept 2026, 01:552,080+8
4 Sept 2026, 17:592,072+1
31 Aug 2026, 22:042,071-7
29 Aug 2026, 03:032,078-2
26 Aug 2026, 09:522,080-2
23 Aug 2026, 14:472,082+3
19 Aug 2026, 17:052,079+10
16 Aug 2026, 16:042,069+7
12 Aug 2026, 23:132,062+10
10 Aug 2026, 01:222,052+13
7 Aug 2026, 07:082,039+1
6 Aug 2026, 20:182,038first 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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 20 September 2026 — this entry's latest reading, not the date you are reading this.

“نَـيّلوفُر” (@Nilof9), 2,098 subscribers as measured 20 September 2026. Telegram Register, tgregister.com/channel/Nilof9.

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.