Профилактик тадбирлар (Тошкент)

Channel
IIV | TV NAMOYISH | Rasmiy kanal
@iivuz_tv
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
6,326subscribers
+707 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001298461303 |
|---|---|
| Type | Channel |
| Username | @iivuz_tv |
| Created | 17 May 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/iivuz_tv |
Topic
Local community — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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 |
|---|---|---|
| 16 Sept 2026, 04:00 | 6,326 | -16 |
| 12 Sept 2026, 14:00 | 6,342 | -1 |
| 8 Sept 2026, 07:38 | 6,343 | +46 |
| 2 Sept 2026, 19:16 | 6,297 | +16 |
| 30 Aug 2026, 19:13 | 6,281 | -10 |
| 27 Aug 2026, 13:55 | 6,291 | -18 |
| 24 Aug 2026, 19:14 | 6,309 | -27 |
| 21 Aug 2026, 12:59 | 6,336 | -9 |
| 18 Aug 2026, 13:53 | 6,345 | +17 |
| 15 Aug 2026, 12:08 | 6,328 | +193 |
| 12 Aug 2026, 11:37 | 6,135 | +96 |
| 9 Aug 2026, 16:03 | 6,039 | +5 |
| 6 Aug 2026, 15:45 | 6,034 | +415 |
| 6 Aug 2026, 03:34 | 5,619 | no change |
| 5 Aug 2026, 22:30 | 5,619 | first reading |
Engagement
84 posts held, back to 4 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 9 pages 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 84 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Аҳоли мурожаатлари ҳал этилмоқда (Бухоро)
Ўғирлик жинояти аниқланди (Хоразм)
Инсон ҳаёти сақлаб қолинди (Тошкент в)
Гиёҳвандликка қаршиш курашиш тадбирлари (Жиззах)
Гиёҳвандлик воситалари тарқалишининг олди олинди (Наманган)
Бирданига 3-курсга ўқишга киритишни ваъда қилган фирибгар ушланди (Тошкент)
Товламачилик билан шуғулланган шахс ушланди (Тошкент)
Ишсиз фуқаро бошқа бир кишини "ишли" қилмоқчи бўлди (Сурхондарё)
Ноқонуний диний таълим берган аёл ушланди (Фарғона)
Гиёҳвандлик билан боғлиқ жиноятлар фош этилди (Навоий)
Ақидапарастлик таъсирига тушган йигитга ҳукм ўқилди (Жиззах)
Showing the 12 most recent of 84 posts we hold for @iivuz_tv. 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.
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.
Mentions
Named by 68 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
@iivuz · 89,547754 postsSh.G'iyosov | IIV matbuot kotibi
@Sh_Giyasov_IIV_matbuot_kotibi · 33,144101 postsSurxondaryo IIB | Rasmiy kanal
@surviib · 30,26639 postsIIV Jamoat xavfsizligi departamenti | Rasmiy kanal
@iivjxduz · 14,74033 postsNavoiy IIB I Rasmiy kanal
@navoiy_iib · 19,62932 postsToshkent shahar IIBB | Rasmiy kanal
@iibbuz · 30,23227 postsTergov departamenti
@tergov_uz · 8,57625 postsQashqadaryo IIB | Rasmiy kanal
@Qashqadaryo_viloyat_IIB · 14,70024 postsBuxoro IIB | Rasmiy kanal
@bviib · 158,69521 postsSamarqand IIB | Rasmiy kanal
@samiibuz · 19,82520 postsAndijon IIB | Rasmiy kanal
@andviliib · 12,39917 postsIchki ishlar organlari nomzodlari uchun
@nomzod2020 · 8,77415 postsXorazm IIB | Rasmiy kanal
@xorazm_iib · 13,80712 postsFargʻona IIB | Rasmiy kanal
@fviib_uz · 14,94210 postsҚўриқлаш Департаменти | расмий канал
@iiv_qduz · 19,9389 postsMA'RIFAT DARSI | МАЪРИФАТ ДАРСИ
@manaviyat_va_marifat_darsi · 71,0479 postsQaraqalpaqstan R. IIM | Rásmiy kanal
@qriim · 10,6699 postsIIV Kiberjinoyatlarga qarshi kurashish departamenti
@cyberpolice_iiv · 93,0138 postsHUQUQ UZB
@huquq_chanel · 1,3058 postsICHKI ISHLAR VAZIRI | A.A.TASHPULATOV
@ichkiishlarvaziri · 41,7606 postsIIV Kadrlar departamenti
@IIVKadr · 16,4886 postsJIZZAX IIB | Rasmiy kanal
@jiziib · 10,6036 postsIIV Raqamli ta’lim markazi 👮♂️| Police Learning Hub 👮♂️
@Legendary_Officers · 14,1606 postsPOSTDA|Rasmiy kanal
@postdarasmiy · 17,0835 posts
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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.
@manaviyat_va_marifat_darsi · 71,047
Telegram ranks this channel #14 of 45 here — alongside 44 others — read 5 September 2026
@ichkiishlarvaziri · 41,760
Telegram ranks this channel #18 of 61 here — alongside 60 others — read 5 September 2026
@Jaloliddin_Ahmadaliyev_Jalolidin · 73,134
Telegram ranks this channel #52 of 63 here — alongside 62 others — read 19 August 2026
This channel appears in 3 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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“IIV | TV NAMOYISH | Rasmiy kanal” (@iivuz_tv), 6,326 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/iivuz_tv.
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.