Telegram RegisterThe public register of Telegram
Telegram profile photo for Marg'ilon darvozalari

Supergroup

Marg'ilon darvozalari

@darvoza_qoqon_darvoza_navoiy

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

1,630members

-90 since we began measuring on 8 August 2026

124 online right now

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

Register entry

Telegram ID-1001676867297
TypeSupergroup
Username@darvoza_qoqon_darvoza_navoiy
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded25 September 2026
Last confirmed live26 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/darvoza_qoqon_darvoza_navoiy

Topic

Real estate — 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 25 September 2026 and assigned it the closest of 31 fixed categories, at 66% 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

1,6301,7201,6758 August 2026 — 1,720 members8 August 2026 — 1,719 members11 August 2026 — 1,713 members14 August 2026 — 1,709 members17 August 2026 — 1,707 members21 August 2026 — 1,698 members24 August 2026 — 1,691 members27 August 2026 — 1,684 members30 August 2026 — 1,680 members3 September 2026 — 1,673 members8 September 2026 — 1,664 members12 September 2026 — 1,655 members15 September 2026 — 1,648 members25 September 2026 — 1,648 members26 September 2026 — 1,630 members8 August 202626 September 2026
15 measurements spanning 49 days, net -90. 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 1,617–1,734 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
26 Sept 2026, 14:001,630-18
25 Sept 2026, 16:061,648no change
15 Sept 2026, 18:211,648-7
12 Sept 2026, 12:391,655-9
8 Sept 2026, 10:141,664-9
3 Sept 2026, 09:471,673-7
30 Aug 2026, 20:571,680-4
27 Aug 2026, 13:491,684-7
24 Aug 2026, 15:371,691-7
21 Aug 2026, 02:341,698-9
17 Aug 2026, 17:271,707-2
14 Aug 2026, 17:551,709-4
11 Aug 2026, 18:371,713-6
8 Aug 2026, 10:381,719-1
8 Aug 2026, 09:351,720first 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

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

“Marg'ilon darvozalari” (@darvoza_qoqon_darvoza_navoiy), 1,630 members as measured 26 September 2026. Telegram Register, tgregister.com/channel/darvoza_qoqon_darvoza_navoiy.

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.