Go'zal yorimโค๏ธโ๐ฅ Trend๐ (Shoxislom_qudratullayev) bilan๐ฅ
๐4๐ฏ4๐คฉ4โค3๐ฅฐ3โคโ๐ฅ1๐1๐ฅ1
Signed โ๏ธ๐๐ฎ๐ก๐ซ๐ข๐๐๐ข๐ง.๐ฅ๐ฏ

Channel
@uz_beatsz
On this record: Growth ยท Engagement ยท What this channel posts ยท Reactions ยท Posts ยท Citations ยท Cite this entry
57subscribers
+2 since we began measuring on 13 August 2026
Risers and fallers across the register ยท movement among entries of Under 1,000.
| Telegram ID | -1002130615488 |
|---|---|
| Type | Channel |
| Username | @uz_beatsz |
| Created | Between 1 November 2023 and 31 May 2024 โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/uz_beatsz |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 12:17 | 57 | -1 |
| 6 Sept 2026, 09:59 | 58 | -1 |
| 22 Aug 2026, 20:09 | 59 | +4 |
| 14 Aug 2026, 12:55 | 55 | no change |
| 13 Aug 2026, 09:47 | 55 | first reading |
17 posts held, back to 26 November 2025 โ 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 17 posts for this entry, the most recent from 3 June 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 15 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.
320 reactions across 17 posts, in 24 distinct kinds. The most used accounts for 19.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ๐ | 61 | 19.1% | |
| ๐ฅ | 38 | 11.9% | |
| ๐ฏ | 32 | 10.0% | |
| โค | 31 | 9.69% | |
| ๐ฅฐ | 30 | 9.38% | |
| โคโ๐ฅ | 25 | 7.81% | |
| ๐คฉ | 23 | 7.19% | |
| ๐ | 19 | 5.94% | |
| ๐ | 9 | 2.81% | |
| ๐ฆ | 9 | 2.81% | |
| ๐ | 8 | 2.50% | |
| ๐ | 8 | 2.50% | |
| customย 5332660707865406692 | 5 | 1.56% | |
| customย 5465665777619204788 | 4 | 1.25% | |
| ๐ | 4 | 1.25% | |
| ๐ | 3 | 0.938% | |
| ๐ | 2 | 0.625% | |
| ๐ | 2 | 0.625% | |
| ๐คทโโ | 2 | 0.625% | |
| customย 5330307568298374406 | 1 | 0.313% | |
| 4 further kinds | 4 | 1.25% |
Custom emoji. 3 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id โ no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegramโs.
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 17 of the 17 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 320 reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 17 most recent posts we hold, published 26 November 2025 to 3 June 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.
Go'zal yorimโค๏ธโ๐ฅ Trend๐ (Shoxislom_qudratullayev) bilan๐ฅ
๐4๐ฏ4๐คฉ4โค3๐ฅฐ3โคโ๐ฅ1๐1๐ฅ1
Signed โ๏ธ๐๐ฎ๐ก๐ซ๐ข๐๐๐ข๐ง.๐ฅ๐ฏ
Ko'ksim qazib ko'mib qoyganman๐ฅ
๐7โคโ๐ฅ6โค3๐2๐ฅ2๐คฉ2๐ฏ1๐ฅฐ1
Signed โ๏ธ๐๐ฎ๐ก๐ซ๐ข๐๐๐ข๐ง.๐ฅ๐ฏ
Zilol ayronda mehmon bo'ldik ๐ฅ โ๏ธ +998947344757 ๐ซก
๐5๐ฅฐ4๐ฅ3โค1๐1๐1๐ฏ1
Signed โ๏ธ๐๐ฎ๐ก๐ซ๐ข๐๐๐ข๐ง.๐ฅ๐ฏ
๐โHar bir yoโl โ bu yangi hikoya.โ๐ช . . . #photos #andijan #imomota #imomotaโฐ๏ธ
๐ฏ4๐คฉ3๐2๐2๐ฅ2โค1โคโ๐ฅ1๐1
Signed .
Kunduz desam, kunlarim tunday, Tonglarim ham yorishmas go`yo. Sensiz juda qiynalib ketdim, Hayotimda qolmadi maโno.๐ฅ
๐6๐ฆ4๐2๐ฅ2๐คทโโ2๐1
Signed โ๏ธ๐๐ฎ๐ก๐ซ๐ข๐๐๐ข๐ง.๐ฅ๐ฏ
"Insofsiz"๐ฅ (cover) Yangiliklar qilishda davom etamiz๐ฅ
๐ฆ5โค2๐2๐2๐ฅ2โคโ๐ฅ1๐ค1
Signed โ๏ธ๐๐ฎ๐ก๐ซ๐ข๐๐๐ข๐ง.๐ฅ๐ฏ
๐ฑShoxislom_qudratullayev bilan birga ko'pchilikni talab va istaklariga ko'ra shu qo'shiqni joylashni maqul ko'rdik!!! Bizdan ijod va mehnat๐ฅ sizlardan padershka kutib qolamizโ๐ป . ๐ฅ TO'LIQ VIDEO . . #ohonajon #dolya #reels #toptags #uzbekistan๐บ๐ฟ
โค4๐ฅ3๐2๐คฉ2โคโ๐ฅ1๐ฏ1๐1
Signed โ๏ธ๐๐ฎ๐ก๐ซ๐ข๐๐๐ข๐ง.๐ฅ๐ฏ
Sizga yor - yor aytilgan oqshom. Ko'ksim qazib ko'mib qo'yganman๐๐ฅ
๐ฏ4๐3โค2๐2๐คฉ2๐ฅฐ2โคโ๐ฅ1๐1
Signed โ๏ธ๐๐ฎ๐ก๐ซ๐ข๐๐๐ข๐ง.๐ฅ๐ฏ
Shiringina armonimโค๏ธโ๐ฉน๐ฅ Anchadan beri po'st bo'lmagandi๐ค Endi Xudo hohlasa doimo ijoddaman๐ซก She'r muallifi : https://t.me/mumtozbegim_sherlari โ๐ป
โค4๐4๐คฉ3โคโ๐ฅ1๐1๐ฏ1๐ฅฐ1
Signed โ๏ธ๐๐ฎ๐ก๐ซ๐ข๐๐๐ข๐ง.๐ฅ๐ฏ
2 - video ๐ฅ Ukamizga gap yoq) Shu yoshda qo'rqme saxnaga chiqish ๐คฉ
๐4โค3๐ฅ3๐2๐ฏ2๐ฅฐ2โคโ๐ฅ1๐คฉ1
Signed โ๏ธ๐๐ฎ๐ก๐ซ๐ข๐๐๐ข๐ง.๐ฅ๐ฏ
Bo'ldikmi biz begona, alam qilardi menga yomona๐ฅ
โคโ๐ฅ3๐3๐ฅ3โค1๐1๐คฉ1
Signed โ๏ธ๐๐ฎ๐ก๐ซ๐ข๐๐๐ข๐ง.๐ฅ๐ฏ
Rahmat jigarim boringa shukur โ๐ป๐ซ Karochi tuguldim๐
๐2๐ฅฐ2customย 53326607078654066922โค1๐1๐ฅ1customย 54656657776192047881
Signed โ๏ธ๐๐ฎ๐ก๐ซ๐ข๐๐๐ข๐ง.๐ฅ๐ฏ
Showing the 12 most recent of 17 posts we hold for @uz_beatsz. 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.
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.
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 13 September 2026 โ this entry's latest reading, not the date you are reading this.
โUz beats๐ฆ โ (@uz_beatsz), 57 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/uz_beatsz.
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.