Telegram RegisterThe public register of Telegram
Telegram profile photo for NURAFSHON XOZMAG

Channel

NURAFSHON XOZMAG

@Nurafshon_xozmag

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Cite this entry

62subscribers

-4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001454418908
TypeChannel
Username@Nurafshon_xozmag
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live7 October 2026
Measurements held7
Confirmed unchanged1 time, most recently 7 October 2026
On Telegramt.me/Nurafshon_xozmag

Topic

Ecommerce storefront — 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 28 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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

616663.57 August 2026 — 66 subscribers10 August 2026 — 66 subscribers14 August 2026 — 64 subscribers5 September 2026 — 63 subscribers14 September 2026 — 62 subscribers26 September 2026 — 61 subscribers7 October 2026 — 62 subscribers627 August 20267 October 2026
7 measurements spanning 61 days, net -4. 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 60–67 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Oct 2026, 11:2062+1
26 Sept 2026, 11:0061-1
14 Sept 2026, 08:1562-1
5 Sept 2026, 19:3863-1
14 Aug 2026, 02:3664-2
10 Aug 2026, 01:4666no change
7 Aug 2026, 11:1666first reading

Engagement

20 posts held, back to 7 July 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 27 August 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
7m 05s
Average length
21s

Measured directly from 20 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Recent posts

27 Aug 2025, 15:18 UTC279 viewsread 10 August 2026
Video

Narxi 35.000 so’m ✔️ Buyurtma bering🔜@nurafshon_adm1n ➡️Murojat qiling Tel 📞: 97-777-07-69

17 Jul 2025, 07:22 UTC356 viewsread 10 August 2026
Video

Narxi 50.000 so’m ✔️ Buyurtma bering🔜@nurafshon_adm1n ➡️Murojat qiling Tel 📞: 97-777-07-69

7 Jul 2025, 19:25 UTC339 viewsread 10 August 2026
Video

Narxi 25.000 so’m ✔️ Buyurtma bering🔜@nurafshon_adm1n ➡️Murojat qiling Tel 📞: 97-777-07-69

7 Jul 2025, 19:23 UTC312 viewsread 10 August 2026
Video

Narxi 40.000 so’m ✔️ Buyurtma bering🔜@nurafshon_adm1n ➡️Murojat qiling Tel 📞: 97-777-07-69

7 Jul 2025, 19:23 UTC281 viewsread 10 August 2026
Video

Narxi 35.000 so’m ✔️ Buyurtma bering🔜@nurafshon_adm1n ➡️Murojat qiling Tel 📞: 97-777-07-69

7 Jul 2025, 19:22 UTC266 viewsread 10 August 2026
Video

Narxi 50.000 so’m ✔️ Buyurtma bering🔜@nurafshon_adm1n ➡️Murojat qiling Tel 📞: 97-777-07-69

7 Jul 2025, 19:20 UTC242 viewsread 10 August 2026
Video

Narxi 30.000 so’m ✔️ Buyurtma bering🔜@nurafshon_adm1n ➡️Murojat qiling Tel 📞: 97-777-07-69

7 Jul 2025, 19:19 UTC226 viewsread 10 August 2026
Video

Narxi 120.000 so’m ✔️ Buyurtma bering🔜@nurafshon_adm1n ➡️Murojat qiling Tel 📞: 97-777-07-69

7 Jul 2025, 19:19 UTC212 viewsread 10 August 2026
Video

Narxi 25.000 so’m ✔️ Buyurtma bering🔜@nurafshon_adm1n ➡️Murojat qiling Tel 📞: 97-777-07-69

7 Jul 2025, 19:18 UTC208 viewsread 10 August 2026
Video

Narxi 75.000 so’m ✔️ Buyurtma bering🔜@nurafshon_adm1n ➡️Murojat qiling Tel 📞: 97-777-07-69

7 Jul 2025, 19:17 UTC204 viewsread 10 August 2026
Video

Narxi 50.000 so’m ✔️ Buyurtma bering🔜@nurafshon_adm1n ➡️Murojat qiling Tel 📞: 97-777-07-69

7 Jul 2025, 19:17 UTC198 viewsread 10 August 2026
Video

Narxi 25.000 so’m ✔️ Buyurtma bering🔜@nurafshon_adm1n ➡️Murojat qiling Tel 📞: 97-777-07-69

Showing the 12 most recent of 20 posts we hold for @Nurafshon_xozmag. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

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

“NURAFSHON XOZMAG” (@Nurafshon_xozmag), 62 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/Nurafshon_xozmag.

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.