https://t.me/Umr_Daftarim_uz
Signed Gulchexra Qurbonova

Channel
@Umr_Daftarim_uz
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
14,147subscribers
-2,057 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001844213631 |
|---|---|
| Type | Channel |
| Username | @Umr_Daftarim_uz |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/Umr_Daftarim_uz |
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 10 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 08:16 | 14,147 | -37 |
| 16 Sept 2026, 05:38 | 14,184 | -42 |
| 14 Sept 2026, 11:56 | 14,226 | -55 |
| 12 Sept 2026, 18:21 | 14,281 | -46 |
| 10 Sept 2026, 16:57 | 14,327 | -164 |
| 7 Sept 2026, 17:36 | 14,491 | -110 |
| 4 Sept 2026, 17:21 | 14,601 | -32 |
| 3 Sept 2026, 02:08 | 14,633 | -59 |
| 1 Sept 2026, 23:06 | 14,692 | -24 |
| 31 Aug 2026, 23:59 | 14,716 | -24 |
| 30 Aug 2026, 22:47 | 14,740 | -12 |
| 29 Aug 2026, 20:03 | 14,752 | -31 |
| 28 Aug 2026, 23:33 | 14,783 | -13 |
| 28 Aug 2026, 03:03 | 14,796 | -16 |
| 27 Aug 2026, 05:07 | 14,812 | -37 |
| 26 Aug 2026, 01:41 | 14,849 | -12 |
| 25 Aug 2026, 03:35 | 14,861 | -37 |
| 23 Aug 2026, 22:24 | 14,898 | -61 |
| 22 Aug 2026, 06:08 | 14,959 | -215 |
| 21 Aug 2026, 00:42 | 15,174 | first reading |
782 posts held, back to 7 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 51 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 72 of 260 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 782 (7 August 2026 – 2 September 2026) |
| Views total | 41,367 |
| Reactions total | 114 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 18:23 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Measured directly from 301 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.
329 reactions across 203 posts, in 9 distinct kinds. The most used accounts for 58.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 192 | 58.4% | |
| 👍 | 87 | 26.4% | |
| 😍 | 20 | 6.08% | |
| 💯 | 12 | 3.65% | |
| 🥰 | 11 | 3.34% | |
| 🕊 | 3 | 0.912% | |
| 🤝 | 2 | 0.608% | |
| 😘 | 1 | 0.304% | |
| 🙏 | 1 | 0.304% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 216 of the 782 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 329 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 782 most recent posts we hold, published 7 August 2026 to 2 September 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
https://t.me/Umr_Daftarim_uz
Signed Gulchexra Qurbonova
https://t.me/Umr_Daftarim_uz
❤1
Signed Gulchexra Qurbonova
https://t.me/Umr_Daftarim_uz
Signed Gulchexra Qurbonova
Аллоҳим!.. Бизларга яхшилик эшикларини, омонлик эшикларини, саломатлик эшикларини, неъмат эшикларини, баракот эшикларини, куч-қувват эшикларини, дўстлик эшикларини, раҳмат эшикларини, ризқ эшикларини, илм эшикларини, мағфират эшикларини очсин. ТУНИНГИЗ ИБОДАТДА ЎТСИН АЗИЗЛАРИМ... 🌹🌹🌹🌹🌹🌹🌹🌹🌹🌹🌹🌹 https://t.me/Umr_Daftarim_uz
❤1
Signed Gulchexra Qurbonova
https://t.me/Umr_Daftarim_uz
👍1
Signed Gulchexra Qurbonova
https://t.me/Umr_Daftarim_uz
Signed Gulchexra Qurbonova
#мен_келинман 72-қисм Аввалига ҳожатга чиқяпти, деб ўйлади. Лекин Жавоҳирги тажжубга солиб Дониёр кийина бошлади. Кейин ўзи ёпиниб ётган қалин одёлни кўтариб чиқиб кетди. Жавоҳирнинг юрагида умид уйғонди. “Дониёр Баҳора билан боғланган бўлса-я”, дея дили ёришди. Дониёрнинг келишини интиқлик билан кута бошлади. Сал ўтмай, Дониёр қайтди. Жавоҳир ўрнидан туриб, унга “қаердан келяпсан?” дегандек қаради. Дониёр индам…
❤5
Signed Gulchexra Qurbonova
#мен_келинман 71-қисм #муаллиф_Наргиза_Усанбоева Жавоҳир йўловчиси бўлмаса-да, Баҳорани учратган кўчасига бир-неча марта борди. Аммо топа олмади. Москва катта, кўча кўп, иморат кўп, одам кўп, қай биридан изласин. Хуллас у кун бўйи кайфиятсиз юрди, кўзлари тинмай Баҳорани қидирди. Лекин топа олмади. - Ака, қизни йўқ қилдингми? – деди йигитлар кечки овқат пайтида Жавоҳирдан норози бўлишиб. – Шу уйни йиғиб, овқ…
❤2
Signed Gulchexra Qurbonova
#мен_келинман 70-қисм - Ҳеч бўлмаса, юрагингиз бўшайди-ку. Балки... бир-икки сўм ёрдам қиларман. - Раҳмат, умрингиздан барака топинг... – холанинг йиғлагани эшитилди. - Хола, - деди Жавоҳир аёлнинг қалби қулфини очишга тиришиб. – Сизнинг ҳам болангиз Россиядами? Аёл баттар йиғига зўр берди. Кейин зўрға гапира бошлади. - Менинг ҳам бир болам Россияда эди. Менинг ва акасининг дардига даврмон …
❤2
Signed Gulchexra Qurbonova
#мен_келинман 69-қисм - Йўқса... – деди янгам кўзларини лўқ қилиб. – Куёвнинг холасига нуқсонингиз ҳақида айтаман... Мен қотиб қолдим. “Нуқсоним...” Ҳа, менинг нуқсоним бор... - Боя холаси билан телефон алишдик. Тўй маслаҳати учун. Мен холасига келиннинг “оқ доғи” бор десам... бўлди! Менинг ичимга титроқ кирди. 💦 Жавоҳир ўша куни туни билан ишлади. Юрган кўчаси борки, негадир Баҳорани қидирди. Баҳор…
❤2
Signed Gulchexra Qurbonova
Photo, posted without a caption
Signed Gulchexra Qurbonova
Sticker, posted without a caption
Signed Gulchexra Qurbonova
Showing the 12 most recent of 782 posts we hold for @Umr_Daftarim_uz. 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.
@Umr_Daftarim_uz edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
“УМР ДАФТАРИМ УЗ” (@Umr_Daftarim_uz), 14,147 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/Umr_Daftarim_uz.
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.