Real estate — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 90% 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.
Observations
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Content that also appears on other registered channels
Posts published here appear word for word on 5 other registered channels. They sit inside a group of 13 channels that share the same post bodies with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
Matching posts — open both and compare (6 of the pairs behind the counts below)
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 2 of the 30 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 849 comparable posts for this entry, running 27 June 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).
Across the whole group of 13, the earliest publisher we hold is @Yaxshi_Yomon. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_mutual · clone_source, last confirmed 8 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
Also posting the same content
This channel’s posts match, word for word or near enough, posts on 12 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
196 measurements spanning 81 days, net +64,603. 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 760,096–933,570 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 196
Measured (UTC)
Subscribers
Change
25 Oct 2026, 13:28
875,875
-601
25 Oct 2026, 12:16
876,476
-3,718
25 Oct 2026, 02:56
880,194
-1,163
25 Oct 2026, 01:46
881,357
-4,004
24 Oct 2026, 15:00
885,361
-411
24 Oct 2026, 14:04
885,772
-6,022
24 Oct 2026, 05:18
891,794
-2,451
23 Oct 2026, 23:56
894,245
+25,482
23 Oct 2026, 14:10
868,763
-517
23 Oct 2026, 13:27
869,280
+134
23 Oct 2026, 05:47
869,146
+3,616
22 Oct 2026, 21:06
865,530
-10,297
22 Oct 2026, 10:46
875,827
-1,077
22 Oct 2026, 10:17
876,904
-3,975
22 Oct 2026, 05:18
880,879
-4,576
21 Oct 2026, 18:27
885,455
-6,238
21 Oct 2026, 06:07
891,693
-3,361
21 Oct 2026, 00:48
895,054
no change
21 Oct 2026, 00:16
895,054
-6,332
20 Oct 2026, 11:49
901,386
first reading
Engagement
2,902 posts held, back to 27 June 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 226 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
11.4%
avg views ÷ 875,875 subscribers
Avg views / post
99,600
705 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
705
of 2,902 held
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 2 of 705 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 25 October 2026
Posts held
2,902 (27 June 2026 – 25 October 2026)
Views total
70,219,441
Reactions total
0
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
25 Oct 2026, 11:35 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.
What this channel posts
Video runtime
11h 47m
Average length
1m 01s
Measured directly from 696 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.
View velocity
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
8 most recently posted, with a view-velocity reading
3.0 hours: 8,530 → 6.0 hours: 10,800still climbing at last reading
not yet at 24h
78 minutesupper bound — already past half at first reading · provisional — final view count still climbing
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
Telegram Stars
Stars received
7
across the posts below
Posts paid on
3
of 1,000 we hold a reading for · 0.3%
Most on one post
3
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @kduzb. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 12 September 2026 to 25 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
📍ЯНГИ ТОШКЕНТДА — УЙЛИ БЎЛИШНИНГ ЯНГИ ИМКОНИЯТИ! 🔥
🏙 Bodrum House компаниясидан махсус таклиф!
🚀 Энди ЯнгИ Тошкент лойиҳаларида бошланғич тўловсиз хонадон харид қилиш имконияти!
⚡️ Атиги 100 та хонадон учун амал қиладиган ушбу таклифдан фойдаланишга шошилинг!
📍Янги Тошкент лойиҳасига яқин ҳудудда
📞Батафсил маълумот ва мурожаат учун:
☎️ +998555195555
☎️ +998955915555
☎️ +998953122222
Bodrum House — янги ҳаёт са…
Qimmatbaho muhitda hamyonbop taomlanish mumkinligini bilarmidingiz? 😳 Ketdik!
Ko‘pchilik bu joyni faqat elita uchun deb o‘ylaydi, ammo «Fotix» restorani barcha uchun narxlarni juda qulay qilib qo‘ydi!
Bu yerda har bir nozik did egasi uchun:
🇹🇷Turk taomlari — sharqona lazzat va nafislik
🇺🇿Milliy taomlar — o‘zimizning to‘yimli, o‘zgacha ta’m
🇪🇺Yevropa oshxonasi — zamonaviy va bejirim menyu
✨ Oilangiz, ahli ayoling…
☄️☄️☄️ИСЛОМ ЦИВИЛИЗАЦИЯСИ МАРКАЗИ ЖЕНЕВАДАГИ БМТ ҚАРОРГОҲИДА МАРКАЗИЙ ОСИЁНИНГ ИЛМИЙ ВА МАЪНАВИЙ МЕРОСИНИ ТАҚДИМ ЭТДИ
ЖЕНЕВА, 2026 йил 22 октябрь. — Ўзбекистондаги Ислом цивилизацияси маркази Женевадаги БМТ бўлинмасида Марказий Осиёнинг илмий ва маънавий мероси, шунингдек, уни ўрганиш, сақлаш ва кенг тарғиб этишга қаратилган замонавий лойиҳаларни тақдим этди. Миллатлар саройида «Цивилизациялар, шахслар, кашфиётлар» …
❗️BRT автобуслар учун алоҳида йўлак энди Ўзгаришдан бошлаб Сергелигача бўлган қисмида ташкил қилиш бошлангани айтилмоқда. @dodasi👇👇
https://t.me/joinchat/QWzanpJkwkJVRtJz
Showing the 12 most recent of 2,902 posts we hold for @kduzb. 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.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Quyidagi nomlardan qaysi biri kuchaytirilgan ta’sirga ega energetik ichimlik uchun eng mos keladi?
BOOST24%
HYPER24%
EXTRA42%
UNLIMITED22%
The shares total 112%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 1,000 most recent posts we hold (the sample is capped at 1,000), published 12 September 2026 to 25 October 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Forward network
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.
Mentions
Named by 15 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
Handles this channel named that no longer answer
Dead references
3
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
3
vacant every time we have ever looked
@kduzb named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@bydauto named in 1 post, 15 October 2026 – 15 October 2026
@iroda_sazan named in 1 post, 8 August 2026 – 8 August 2026
@yuliya_sazan named in 1 post, 8 August 2026 – 8 August 2026
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Telegram_Yulduzlari| Расмий канал @tyuzbek · 1,021,016#1
Read from Telegram’s recommendation API, most recently 8 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
Hozirda | Ishonchli xabarlar @hozirda · 127,324 Telegram ranks this channel #1 of 65 here — alongside 64 others — read 13 August 2026
Shov - Shuv UZ @shov_shuvUZ · 162,475 Telegram ranks this channel #1 of 69 here — alongside 68 others — read 11 August 2026
Kursinfo - Dollar kursi 💲 @kursinfo_dollar_moliya · 76,730 Telegram ranks this channel #3 of 40 here — alongside 39 others — read 19 August 2026
Navoiyliklar I Расмий канал @NAVOIYLIKLAR_UZB · 101,998 Telegram ranks this channel #3 of 72 here — alongside 71 others — read 15 August 2026
INSTAGRAM YULDUZLARI @instagram_yulduzlarim · 103,151 Telegram ranks this channel #4 of 46 here — alongside 45 others — read 1 October 2026
AXBOROT @axborotofficial · 52,330 Telegram ranks this channel #4 of 64 here — alongside 63 others — read 25 August 2026
Vachaaach | Rasmiy Kanal @Vachach · 104,594 Telegram ranks this channel #4 of 64 here — alongside 63 others — read 17 August 2026
🎥 AUDIOLAR 🔊 @AUDIO_HAZLLAR · 96,974 Telegram ranks this channel #5 of 51 here — alongside 50 others — read 1 October 2026
𝐌𝐢𝐭𝐭𝐢𝐯𝐢𝐧𝐞 @mittivines · 54,769 Telegram ranks this channel #5 of 53 here — alongside 52 others — read 23 August 2026
🎥 Drakauz 🌀 | Расмий канал 🔥 @drakauz · 24,568 Telegram ranks this channel #7 of 62 here — alongside 61 others — read 15 September 2026
Abdukarim Mirzayev | Rasmiy kanal @Abdukarim_Mirzayev_Tv · 25,400 Telegram ranks this channel #7 of 71 here — alongside 70 others — read 13 September 2026
Toshkentliklar🇺🇿 | Расмий @Toshkentliklar_Uz · 82,878 Telegram ranks this channel #7 of 73 here — alongside 72 others — read 17 August 2026
КУН ВИДЕОЛАРИ 🔴 @KV100 · 19,121 Telegram ranks this channel #8 of 59 here — alongside 58 others — read 1 October 2026
TOSHKENT 24 | TEZKOR XABARLARI @toshkent · 217,358 Telegram ranks this channel #8 of 59 here — alongside 58 others — read 25 August 2026
Kun Videolari 🎥 @Kun_uz · 107,272 Telegram ranks this channel #8 of 43 here — alongside 42 others — read 24 August 2026
Shou-biznes yangiliklari @shoubizyangiliklari · 119,592 Telegram ranks this channel #8 of 65 here — alongside 64 others — read 13 August 2026
UZBEK VIDEO CHANNEL @uzbekvideo · 205,093 Telegram ranks this channel #8 of 67 here — alongside 66 others — read 11 August 2026
MILITSIYA UZB | Расмий канал @MILITSIYA_UZB · 554,841 Telegram ranks this channel #8 of 62 here — alongside 61 others — read 9 August 2026
Carrozzeria Music🎧 @Carrozzeria_music · 19,935 Telegram ranks this channel #9 of 34 here — alongside 33 others — read 6 September 2026
VAQT QADRI @VAQTQADRI · 52,268 Telegram ranks this channel #9 of 68 here — alongside 67 others — read 24 August 2026
Buxoroliklar | Расмий канал @buxoroliklar · 72,738 Telegram ranks this channel #9 of 58 here — alongside 57 others — read 17 August 2026
YANGI YANGIYOL @YANGIYOLbot · 46,621 Telegram ranks this channel #10 of 49 here — alongside 48 others — read 31 August 2026
Sevimli TV @tvsevimli · 44,358 Telegram ranks this channel #10 of 71 here — alongside 70 others — read 27 August 2026
PATRUL UZ | РАСМИЙ КАНАЛ @patrul_uz · 948,567 Telegram ranks this channel #10 of 71 here — alongside 70 others — read 8 August 2026
This channel appears in 178 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Domains linked from posts
72 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 25 October 2026 — this
entry's latest reading, not the date you are reading this.
“Kanallani Dodasi | Расмий канал” (@kduzb), 875,875 subscribers as measured 25 October 2026. Telegram Register, tgregister.com/channel/kduzb.
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.
