Telegram RegisterThe public register of Telegram
Telegram profile photo for Proliga

Channel

Proliga

@proligauzb

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

12,847subscribers

+417 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-1001280848107
TypeChannel
Username@proligauzb
Created2 July 2020measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live11 September 2026
Measurements held29
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/proligauzb

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 11 September 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 why it has no browse page of its own yet.

Growth

12,43012,85712,643.56 August 2026 — 12,430 subscribers6 August 2026 — 12,430 subscribers7 August 2026 — 12,455 subscribers8 August 2026 — 12,453 subscribers9 August 2026 — 12,440 subscribers10 August 2026 — 12,488 subscribers11 August 2026 — 12,556 subscribers12 August 2026 — 12,573 subscribers13 August 2026 — 12,568 subscribers14 August 2026 — 12,584 subscribers16 August 2026 — 12,666 subscribers17 August 2026 — 12,671 subscribers18 August 2026 — 12,684 subscribers19 August 2026 — 12,682 subscribers20 August 2026 — 12,714 subscribers21 August 2026 — 12,734 subscribers23 August 2026 — 12,750 subscribers24 August 2026 — 12,760 subscribers25 August 2026 — 12,756 subscribers26 August 2026 — 12,747 subscribers27 August 2026 — 12,768 subscribers29 August 2026 — 12,777 subscribers30 August 2026 — 12,785 subscribers30 August 2026 — 12,786 subscribers1 September 2026 — 12,790 subscribers3 September 2026 — 12,801 subscribers5 September 2026 — 12,815 subscribers8 September 2026 — 12,857 subscribers11 September 2026 — 12,847 subscribers12,8476 August 202611 September 2026
29 measurements spanning 36 days, net +417. 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 12,366–12,921 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 29
Measured (UTC)SubscribersChange
11 Sept 2026, 13:2112,847-10
8 Sept 2026, 19:3912,857+42
5 Sept 2026, 13:2112,815+14
3 Sept 2026, 11:3812,801+11
1 Sept 2026, 00:2612,790+4
30 Aug 2026, 21:1412,786+1
30 Aug 2026, 00:3612,785+8
29 Aug 2026, 01:1812,777+9
27 Aug 2026, 22:1212,768+21
26 Aug 2026, 23:2812,747-9
25 Aug 2026, 21:1412,756-4
24 Aug 2026, 22:1812,760+10
23 Aug 2026, 06:3612,750+16
21 Aug 2026, 17:4512,734+20
20 Aug 2026, 16:0412,714+32
19 Aug 2026, 17:3312,682-2
18 Aug 2026, 20:3312,684+13
17 Aug 2026, 19:3612,671+5
16 Aug 2026, 15:4312,666+82
14 Aug 2026, 21:1812,584first reading

Engagement

200 posts held, back to 5 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 48 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
46.7%
avg views ÷ 12,847 subscribers
Avg views / post
6,000
127 posts measured
Reaction rate
0.331%
reactions ÷ views · ER floor
Posts in window
127
of 200 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 112 of 127 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 2 September 2026
Posts held200 (5 August 20262 September 2026)
Views total762,450
Reactions total2,271
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Sept 2026, 21:13 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
40m 59s
Average length
38s

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

3,370 reactions across 175 posts, in 4 distinct kinds. The most used accounts for 35.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1,18235.1%
👏97128.8%
🏆73721.9%
🤩48014.2%

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

Measured over the 200 most recent posts we hold, published 5 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, 18:05 UTC≈2,610 views25 reactionsread 2 September 2026
Video

🔵 Marko Milichkovich yana bu ishni amalga oshirdi 🤩 U yana maydon markazidan raqib darvozasini ishgʻol qildi ☄️ 📲 https://t.me/ProLigaUZB

🔥22🤩3

2 Sept 2026, 15:19 UTC≈4,990 views31 reactionsread 2 September 2026
Photo

⚽️⚽️ Proliga. Metallurg onlayn jadvalda 2-oʻringa koʻtarilib oldi 📲 https://t.me/proligauzb

🔥23🏆4👏4

2 Sept 2026, 15:04 UTC≈4,910 views14 reactionsread 2 September 2026
Photo

⚽️⚽️ Proliga. 19-tur 🔴 OLIMPIK MOBIUZ 2:3 METALLURG 🔵 ⚽️ Abdushukur Mahamatov, 19 penalti (1:0), Marko Milichkovich, 29 (1:1), Marko Milichkovich, 45+1 (1:2), Bunyodbek Rahimov, 50 (2:2), Marko Milichkovich, 87 penalti (2:3) 📲 https://t.me/ProLigaUZB

🏆11👏3

2 Sept 2026, 14:22 UTC≈5,140 views9 reactionsread 2 September 2026
Video

🟢 🔴 OLIMPIK MOBIUZ 2:2 METALLURG 🔵 ⚽️ Bunyodbek Rahimov, 50 (2:2)

👏9

2 Sept 2026, 14:00 UTC≈5,460 views12 reactionsread 2 September 2026
Video

🟢 🔴 OLIMPIK MOBIUZ 1:2 METALLURG 🔵 ⚽️ Marko Milichkovich, 45+1 (1:2)

🔥8🏆4

2 Sept 2026, 13:45 UTC≈7,090 views38 reactionsread 2 September 2026
Video

Supergol! 🟢 🔴 OLIMPIK MOBIUZ 1:1 METALLURG 🔵 ⚽️ Marko Milichkovich, 29 (1:1)

🔥25👏7🤩4🏆2

2 Sept 2026, 13:34 UTC≈5,350 viewsread 2 September 2026
Video

🟢 🔴 OLIMPIK MOBIUZ 1:0 METALLURG 🔵 ⚽️ Abdushukur Maxamatov, 19 penalti (1:0)

2 Sept 2026, 12:55 UTC≈5,400 views0 reactionsread 2 September 2026
Photo

🔴 OLIMPIK MOBIUZ — METALLURG 🔵 🟢 https://youtu.be/VQbe-HNTOro

2 Sept 2026, 12:08 UTC≈7,410 views85 reactionsread 2 September 2026
Photo

🔵 Aral 13-sentyabrdan e’tiboran Turon stadioniga qaytadi 📲 https://t.me/ProLigaUZB

👏62🏆10🤩7🔥6

2 Sept 2026, 10:09 UTC≈5,510 views9 reactionsread 2 September 2026
Photo

⚽️⚽️ Bugungi uchrashuvni o‘tkazib yuboradiganlar 📲 https://t.me/ProLigaUZB

🔥7🤩2

2 Sept 2026, 09:11 UTC≈5,600 views17 reactionsread 2 September 2026
Photo

⚽️⚽️ Har ikkala jamoa bugungi bahsga ko‘tarinki kayfiyatda yetib kelmoqda 18:00 🔴 OLIMPIK MOBIUZ — METALLURG 🔵 📲 https://t.me/ProLigaUZB

🔥17

2 Sept 2026, 06:29 UTC≈5,920 views25 reactionsread 2 September 2026
Photo

⚽️⚽️ Proliga. Gol+pas tizimi bo‘yicha ko‘rsatkichlar 📲 https://t.me/ProLigaUZB

👏19🔥3🤩3

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

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

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.

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.

UzPFL
@uzpfl · 58,755
Telegram ranks this channel #7 of 79 here — alongside 78 others — read 23 August 2026
Суперлига | Tribuna.uz
@superliganews · 29,276
Telegram ranks this channel #15 of 78 here — alongside 77 others — read 8 September 2026
Uzbekistan Football Association
@FAUzbekistan · 60,104
Telegram ranks this channel #37 of 80 here — alongside 79 others — read 22 August 2026
FC NEFTCHI
@pfcneftchi_uz · 35,009
Telegram ranks this channel #43 of 85 here — alongside 84 others — read 3 September 2026
FC NASAF
@fcnasaf · 42,835
Telegram ranks this channel #44 of 81 here — alongside 80 others — read 29 August 2026
Championat.asia
@championatasia · 97,724
Telegram ranks this channel #55 of 77 here — alongside 76 others — read 16 August 2026

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

Referenced elsewhere

This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.

Wikipedia

7 Wikipedia articles name this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.

2022 Uzbekistan Pro League (en.wikipedia.org)
“…Uzbekistan|UZT]] ([[UTC+5]]) |round = 1 |score = 2–1 |report = [https://t.me/proligauzb/3132 Match report] |team1 = [[FC Yangiyer|Yangiyer]] |goals1 =…”
read 23 August 2026
2023 Uzbekistan Pro League (en.wikipedia.org)
“…Uzbekistan|UZT]] ([[UTC+5]]) |round = 3 |score = 2–1 |report = [https://t.me/proligauzb/6560 Match report] |team1 = [[FC Shurtan|Shoʻrtan]] |goals1 =…”
read 23 August 2026
2025 Uzbekistan Pro League (en.wikipedia.org)
“…ishtirok etadigan Proliga musobaqasiga qurʼa tashlandi][https://t.me/proligauzb/9976 Proliga-2025 qur’asi] == Background == 2025 participation…”
read 23 August 2026
2026 Uzbekistan Pro League (en.wikipedia.org)
“…tournament, which will feature 6 teams, has been made}}[https://t.me/proligauzb/9976 Proliga-2025 qur’asi][https://championat…”
read 23 August 2026
Про-лига Узбекистана по футболу 2022 (ru.wikipedia.org)
“…Узбекистане|UZT]] ([[UTC+5]]) |round = 1 |score = 2–1 |report = [https://t.me/proligauzb/3132 Hisobot] |team1 = [[Янгиер (футбольный клуб)|Янгиер]] |goals1…”
read 23 August 2026
Про-лига Узбекистана по футболу 2023 (ru.wikipedia.org)
“…[[Узбекистанское время|UZT]] ([[UTC+5]]) |round = 3 |score = 2-1 |report = [https://t.me/proligauzb/6560 Отчет] |team1 = [[Шуртан (футбольный клуб)|Шуртан]] |goals1…”
read 23 August 2026
Про-лига Узбекистана по футболу 2025 (ru.wikipedia.org)
“…|url-status=live }}{{Cite web |url=https://t.me/proligauzb/9976 |title=Proliga-2025 qur’asi |archive-date=2025-05-01…”
read 23 August 2026

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

“Proliga” (@proligauzb), 12,847 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/proligauzb.

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.