🏬 Кўчмас мулк ва реклама агентлиги!
- Уй жой олиш ва сотишда
қийналяпсизми?
- Биз сизга ёрдам берамиз
📞 +998-90-772-80-00
Реклама бериш ва хамкорлик учун👇
👉 @reklamauz_manager га ёзинг
Created
Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
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 10 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.
Channels linked by matching posts
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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.
66 measurements spanning 102 days, net -15,565. 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 77,366–113,317 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)
Subscribers
Change
17 Nov 2026, 10:46
86,434
-1,015
14 Nov 2026, 06:31
87,449
-1,197
11 Nov 2026, 07:07
88,646
-677
9 Nov 2026, 14:40
89,323
-357
8 Nov 2026, 09:06
89,680
-442
7 Nov 2026, 01:54
90,122
-330
6 Nov 2026, 04:17
90,452
-435
5 Nov 2026, 00:15
90,887
-274
3 Nov 2026, 23:06
91,161
-70
2 Nov 2026, 22:55
91,231
+3,726
1 Nov 2026, 20:07
87,505
+3,036
31 Oct 2026, 22:27
84,469
+1,956
30 Oct 2026, 22:45
82,513
-669
29 Oct 2026, 23:09
83,182
-558
28 Oct 2026, 22:01
83,740
-490
27 Oct 2026, 23:45
84,230
-378
26 Oct 2026, 22:36
84,608
+265
25 Oct 2026, 23:58
84,343
-345
24 Oct 2026, 22:54
84,688
-898
23 Oct 2026, 20:46
85,586
first reading
Engagement
920 posts held, back to 6 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 209 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
2.13%
avg views ÷ 86,434 subscribers
Avg views / post
1,840
268 posts measured
Reaction rate
0.136%
reactions ÷ views · ER floor
Posts in window
268
of 920 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 139 of 268 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 18 November 2026
Posts held
920 (6 August 2026 – 18 November 2026)
Views total
492,504
Reactions total
345
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
18 Nov 2026, 05:46 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
Photos
≈8,960
Videos
≈3,480
Links
≈7,170
Lifetime counters from Telegram’s own channel header, read 18 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Video runtime
12h 55m
Average length
1m 23s
Measured directly from 560 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.
Reaction mix
1,600 reactions across 528 posts, in 16 distinct kinds. The most used accounts for 36.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
583
36.4%
⚡
381
23.8%
🔥
198
12.4%
🤩
139
8.69%
🥰
86
5.38%
😇
79
4.94%
🎉
53
3.31%
😁
35
2.19%
😍
23
1.44%
👏
7
0.438%
🤝
4
0.25%
🍾
3
0.188%
👌
3
0.188%
🤗
3
0.188%
😎
2
0.125%
💯
1
0.063%
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 535 of the 920 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 1,600 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 920 most recent posts we hold, published 6 August 2026 to 18 November 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.
Recent posts
Telegram’s own ‘edited’ marker: 26 of 268 posts held from the last 30 days (9.70%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
КВАРТИРА ИЖАРАГА
БЕРИЛАДИ ❗️
Манзил Андижон шаҳар, Бўстон даҳаси
• Қават: 10 қаватли бино + лифт бор
• 4 Қават 2 хона
• Ремонти: Яхши ҳолатда, яшашга тайёр, Акфа ром МДФ ва Темир эшик ўрнатилган, Иситиш тизими мавжуд
• Сув, Свет, Канализация бор
• Жихозлари: Жихозлари билан
Нархи: 250$
+Маклер хизмати бор
📞 +998-99-434-88-26
➡️ @Andijon_uybozor_uz
➡️ @Andijon_shahar_uybozor
😎Telegram 😎Instagram
⚡2
Showing the 12 most recent of 920 posts we hold for @andijon_uybozor_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.
Posts edited after publishing
@andijon_uybozor_uz edited 38 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.
First edit seen
9 August 2026
Most recent edit
13 November 2026
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 5 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.
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 17 November 2026 — this
entry's latest reading, not the date you are reading this.
“Andijon UyBozor | UZ” (@andijon_uybozor_uz), 86,434 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/andijon_uybozor_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.