Channel
@tomdiliklar
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
567subscribers
-253 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001932996410 |
|---|---|
| Type | Channel |
| Username | @tomdiliklar |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/tomdiliklar |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 13:57 | 567 | -193 |
| 10 Sept 2026, 17:01 | 760 | -18 |
| 1 Sept 2026, 12:08 | 778 | -2 |
| 25 Aug 2026, 02:16 | 780 | -1 |
| 18 Aug 2026, 00:43 | 781 | -39 |
| 10 Aug 2026, 09:45 | 820 | no change |
| 10 Aug 2026, 09:31 | 820 | first reading |
6 posts held, back to 30 July 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 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 6 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Tomdi tumani hokimi Orzumurod Umarov "Tomdibuloq" OFYga tashrif buyurib, hududda obodonlashtirish borasida olib borilayotgan ishlar holatini o‘rgandi. Mas’ullar bilan ishlar samaradorligi muhokama qilinib, hududni yanada obod va ko‘rkam maskanga aylantirish, mavjud kamchiliklarni bartaraf etish yuzasidan tegishli vazifalar belgilab berildi. 👉 Томди хабарларига аъзо бўлинг👉 https://t.me/+B35cRK-1XrAyMGVi
☑️☑️☑️TOMDIBULOQ OFYDA HAMKORLIK MASALALARI MUHOKAMA QILINDI Xalq deputatlari Tomdi tumani Kengashi raisi J.Turmaxanov "Tomdibuloq" OFY raisi M.Tashbayev hamda hokim yordamchisi R.Dayrabayev bilan uchrashuv o‘tkazdi. Uchrashuv davomida mahallada olib borilayotgan ijtimoiy-iqtisodiy islohotlar, obodonlashtirish va ko‘kalamzorlashtirish ishlari, aholi murojaatlari bilan ishlash, bandlikni ta’minlash hamda kambag‘alli…
Tomdi tumani hokimi Orzumurod Umarov, tuman prokurori Oybek Kurbonov hamda tuman soliq inspeksiyasi boshlig‘i Qahramon Xolmuminov “Keriz” OFYda bo‘lib, “Og‘ir toifadagi mahallalar” dasturi doirasida hududda amalga oshirilayotgan qurilish va obodonlashtirish ishlari bilan tanishdi.
https://t.me/suvchilar_maktabi/1850 Navoiyga ovoz bosaylik, guruhlarga ham tarqatamiz 20:00 da to’gaydi. Tezkor bosamiz
O‘zbekiston Respublikasi Mustaqilligining 35 yilligi munosabati bilan o‘tkazilayotgan “Mahallada obodlik va mehr-saxovat oyligi” doirasida Tomdi tumani "Tomdibuloq" ovul fuqarolar yig‘inida fuqarolar hamda korxona va tashkilotlar xodimlari ishtirokida hashar ishlari uyushqoqlik bilan amalga oshirilmoqda. Hashar davomida hududlarni obodonlashtirish, tozalikni ta’minlash va mahalla ko‘rkini yanada yaxshilashga qaratil…
Tomdi tumani hokimi Orzumurod Umarov "Sharq" OFYga tashrifi davomida Rohat aholi punktida bo‘lib, mahalladagi fuqarolar bilan uchrashdi. Tashrif chog‘ida aholi bilan samimiy muloqot qilinib, xonadonlar va ko‘chalarni obodonlashtirish, ozodalikni ta’minlash, hovlilar hamda ko‘cha yoqalarini tartibga keltirish masalalari yuzasidan tushuntirish ishlari olib borildi.
Showing the 6 most recent of 6 posts we hold for @tomdiliklar. 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.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“TOMDILIKLAR” (@tomdiliklar), 567 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/tomdiliklar.
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.