Telegram RegisterThe public register of Telegram
Telegram profile photo for Murod Rizayev

Channel

Murod Rizayev

@Murod_Rizo

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

22,831subscribers

-2,387 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001729092881
TypeChannel
Username@Murod_Rizo
Created23 November 2021measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live19 September 2026
Measurements held35
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/Murod_Rizo

Topic

Sports — 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 98% 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.

Growth

22,83125,23824,034.56 August 2026 — 25,218 subscribers6 August 2026 — 25,218 subscribers6 August 2026 — 25,238 subscribers7 August 2026 — 25,111 subscribers8 August 2026 — 24,556 subscribers9 August 2026 — 24,065 subscribers10 August 2026 — 24,023 subscribers11 August 2026 — 24,169 subscribers12 August 2026 — 24,186 subscribers14 August 2026 — 24,081 subscribers15 August 2026 — 24,017 subscribers17 August 2026 — 23,988 subscribers18 August 2026 — 23,926 subscribers19 August 2026 — 23,889 subscribers20 August 2026 — 23,865 subscribers21 August 2026 — 23,837 subscribers23 August 2026 — 23,828 subscribers24 August 2026 — 23,801 subscribers25 August 2026 — 23,762 subscribers26 August 2026 — 23,715 subscribers27 August 2026 — 23,681 subscribers28 August 2026 — 23,653 subscribers29 August 2026 — 23,613 subscribers30 August 2026 — 23,575 subscribers31 August 2026 — 23,540 subscribers1 September 2026 — 23,494 subscribers2 September 2026 — 23,426 subscribers3 September 2026 — 23,386 subscribers5 September 2026 — 23,307 subscribers8 September 2026 — 23,193 subscribers11 September 2026 — 23,093 subscribers13 September 2026 — 23,009 subscribers14 September 2026 — 22,961 subscribers16 September 2026 — 22,908 subscribers19 September 2026 — 22,831 subscribers6 August 202619 September 2026
35 measurements spanning 44 days, net -2,387. 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 22,470–25,599 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
19 Sept 2026, 00:3822,831-77
16 Sept 2026, 14:1922,908-53
14 Sept 2026, 21:5722,961-48
13 Sept 2026, 10:1723,009-84
11 Sept 2026, 13:0023,093-100
8 Sept 2026, 22:2023,193-114
5 Sept 2026, 16:0123,307-79
3 Sept 2026, 14:5923,386-40
2 Sept 2026, 06:5323,426-68
1 Sept 2026, 05:4823,494-46
31 Aug 2026, 03:5423,540-35
30 Aug 2026, 05:3623,575-38
29 Aug 2026, 09:0223,613-40
28 Aug 2026, 10:4723,653-28
27 Aug 2026, 14:0323,681-34
26 Aug 2026, 12:1723,715-47
25 Aug 2026, 15:2423,762-39
24 Aug 2026, 17:4523,801-27
23 Aug 2026, 03:5423,828-9
21 Aug 2026, 18:2623,837first reading

Engagement

202 posts held, back to 3 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 63 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
22.7%
avg views ÷ 22,831 subscribers
Avg views / post
5,190
82 posts measured
Reaction rate
0.857%
reactions ÷ views · ER floor
Posts in window
82
of 202 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 2 September 2026
Posts held202 (3 August 20262 September 2026)
Views total425,270
Reactions total3,645
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 11:53 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
29m 59s
Average length
1m 15s

Measured directly from 24 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

7,800 reactions across 197 posts, in 9 distinct kinds. The most used accounts for 36.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2,83336.3%
🔥1,94024.9%
1,39017.8%
👏7709.87%
🤩3584.59%
😱2813.60%
🤯1962.51%
🎉220.282%
🥰100.128%

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 198 of the 202 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 7,800 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 202 most recent posts we hold, published 3 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.

Recent posts

2 Sept 2026, 19:23 UTC≈4,220 views216 reactionsread 3 September 2026
Photo

Тирик афсона... Муносиб эътироф....

👏160🔥2915👍11🤯1

2 Sept 2026, 14:15 UTC≈4,840 views39 reactionsread 3 September 2026
Photo

Jud Bellingem La Ligada Andres Iniyestadan gollar soni bo'yicha o'tib ketdi. ⚡️ Judning Ispaniya Chempionatidagi gollari soni 36 taga yetdi. Angliyalik futbolchi bu natijaga erishish uchun 90 ta o'yinda maydonga tushishi yetarli bo'ldi.

🤯20👏107👍2

2 Sept 2026, 10:57 UTC≈5,190 views28 reactionsread 3 September 2026

Шахмат бўйича Ўзбекистон эркаклар терма жамоаси дунё рейтингида 6-чи ўринга кўтарилди. Бутунжаҳон Шахмат Олимпиадасида чемпионликни қўлга киритадиган бўлсак рейтингда катта сакраш бўлади. Олға Ўзбекистон!!!

15👍8🔥5

2 Sept 2026, 03:10 UTC≈5,570 views25 reactionsread 3 September 2026

Нега ҳамма ёғи бинт билан ўралган....

🤩17🤯53

1 Sept 2026, 16:25 UTC≈5,960 views99 reactionsread 3 September 2026
Photo

Сити ҳам билади кимни олишни.... 🇺🇿 @Murod_Rizo ✅

🔥63👍275🤩4

1 Sept 2026, 12:57 UTC≈5,570 views43 reactionsread 3 September 2026
Photo

Габриель Жезуш... Да уж.. 🇺🇿 @Murod_Rizo ✅

👍32🤯7🤩21😱1

1 Sept 2026, 05:57 UTC≈5,890 views49 reactionsread 3 September 2026
Photo

Байрамингиз қутлуғ бўлсин!!!

👍463

31 Aug 2026, 06:38 UTC≈5,980 views12 reactionsread 3 September 2026

Йигитларимизга омад. Биринчи ўйиндаги натижа муҳим дейишадику... 🇺🇿 @Murod_Rizo ✅

🔥93

30 Aug 2026, 19:07 UTC≈7,090 views91 reactionsread 3 September 2026
Video

Элдорнинг голи

👍70👏1110

30 Aug 2026, 18:51 UTC≈6,990 views37 reactionsread 3 September 2026

Шомуродовдан гол....

22👍11👏4

30 Aug 2026, 18:50 UTC≈7,040 views40 reactionsread 3 September 2026
Video

Бу йил классико зўр бўладиде ўзиям... Иккаласиям мошний ўйин ўтказишяпти... 🇺🇿 @Murod_Rizo ✅

👍24👏113🤩2

Showing the 12 most recent of 202 posts we hold for @Murod_Rizo. 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

@Murod_Rizo edited 4 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
12 August 2026
Most recent edit
26 August 2026

Forward network

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 4 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.

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.

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.

Faxriddin Turopov
@TuropovFaxriddin · 75,659
Telegram ranks this channel #21 of 63 here — alongside 62 others — read 24 August 2026
BoburAkmalov
@boburakmalov · 68,020
Telegram ranks this channel #24 of 62 here — alongside 61 others — read 4 September 2026
Hasan Turdialiyev | Rasmiy kanal
@turdialiyevhasan · 50,019
Telegram ranks this channel #31 of 61 here — alongside 60 others — read 25 August 2026
🇺🇿 Milliy futbolimiz
@milliyfutbolimizuzb · 29,014
Telegram ranks this channel #46 of 62 here — alongside 61 others — read 7 September 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 19 September 2026 — this entry's latest reading, not the date you are reading this.

“Murod Rizayev” (@Murod_Rizo), 22,831 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/Murod_Rizo.

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.