Telegram RegisterThe public register of Telegram
Telegram profile photo for UzCombinator

Channel

UzCombinator

@uzcombinator

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Cite this entry

8,781subscribers

-354 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002956027944
TypeChannel
Username@uzcombinator
CreatedBetween 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live28 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/uzcombinator

Growth

8,7819,1358,9586 August 2026 — 9,135 subscribers6 August 2026 — 9,135 subscribers6 August 2026 — 9,119 subscribers9 August 2026 — 9,053 subscribers12 August 2026 — 9,010 subscribers15 August 2026 — 8,947 subscribers18 August 2026 — 8,911 subscribers22 August 2026 — 8,852 subscribers25 August 2026 — 8,823 subscribers28 August 2026 — 8,781 subscribers6 August 202628 August 2026
10 measurements spanning 23 days, net -354. 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 8,728–9,188 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 17:268,781-42
25 Aug 2026, 08:328,823-29
22 Aug 2026, 11:268,852-59
18 Aug 2026, 19:368,911-36
15 Aug 2026, 17:178,947-63
12 Aug 2026, 14:559,010-43
9 Aug 2026, 15:119,053-66
6 Aug 2026, 20:429,119-16
6 Aug 2026, 02:529,135no change
6 Aug 2026, 00:559,135first reading

Engagement

116 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 31 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
22.3%
avg views ÷ 8,781 subscribers
Avg views / post
1,960
116 posts measured
Reaction rate
0.939%
reactions ÷ views · ER floor
Posts in window
116
of 116 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 111 of 116 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 28 August 2026
Posts held116 (3 August 202628 August 2026)
Views total227,160
Reactions total2,059
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 16:12 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
5m 43s
Average length
29s

Measured directly from 12 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,356 reactions across 95 posts, in 12 distinct kinds. The most used accounts for 34.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥47034.7%
37327.5%
❤‍🔥15311.3%
1067.82%
👍1057.74%
🎉664.87%
😁261.92%
👏221.62%
😍120.885%
🆒90.664%
🏆80.59%
🤩60.442%

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

Measured over the 116 most recent posts we hold, published 3 August 2026 to 28 August 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.

Telegram Stars

Stars received
51
across the posts below
Posts paid on
2
of 116 we hold a reading for · 2%
Most on one post
50
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @uzcombinator. 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 116 most recent posts we hold for this entry, published 3 August 2026 to 28 August 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.

Recent posts

28 Aug 2026, 16:02 UTC248 views7 reactionsread 28 August 2026
Photo

🚀 Bugun UzCombinator tomonidan Venture fond va Investetiya menejerlari uchun birinchi yopiq "Invest Menejerlar Uchrashuvi" tashkil etildi! Tadbir davomida investor menejerlar UzCombinatordagi startaplar bilan yaqindan tanishib, ularning mahsulotlari, traction ko‘rsatkichlari va rivojlanish bosqichlari haqida ma’lumot oldilar 📈 Shuningdek, investorlar uchun maxsus ishlab chiqilgan "UzCombinator Investor Platform" ta

3🎉2🔥2

28 Aug 2026, 16:02 UTC234 views5 reactionsread 28 August 2026
Video message

Video message, posted without a caption

🔥21🎉1🤩1

28 Aug 2026, 15:56 UTC354 views5 reactionsread 28 August 2026

🤔Bugun UzCombinatorda qanaqa event bo'ldi, bilasizmi?

🔥3😁2

28 Aug 2026, 14:34 UTC834 views6 reactionsread 28 August 2026
Photo

UzCombinator co-founderi Ulug‘bek Ismatov bilan o‘tkazilgan bugungi eksklyuziv sessiyadan foto-lavhalar 🚀 ⚡️ @uzcombinator

2❤‍🔥2🔥2

28 Aug 2026, 07:03 UTC≈1,360 views12 reactionsread 28 August 2026

🚀 Startaplarda kommunikatsiya: muvaffaqiyat kaliti yoki inqiroz sababi? Ko‘pincha startaplarning muvaffaqiyatsizligiga texnik xatolar emas, balki jamoa ichidagi noto‘g‘ri kommunikatsiya sabab bo‘ladi. G‘oya qanchalik zo‘r bo‘lmasin, uni to‘g‘ri yetkazib berish va jamoani bir maqsad sari birlashtirish alohida san’at. Tajribali mutaxassis Ulug‘bek Ismatov bilan bo‘lib o‘tadigan navbatdagi sessiyamiz aynan shu muhim m

❤‍🔥4🔥42😍2

27 Aug 2026, 11:10 UTC≈1,330 views2 reactionsread 27 August 2026

🚀 Bugun Speko uchun muhim kun! O‘zbekistondan Y Combinator’ga kirgan yosh founder Beknazar Abdikamalov bugun Speko’ni Product Hunt’da launch qilmoqda. Speko voice AI uchun turli tillar va vazifalarga eng mos voice stack’ni topishga yordam beradi. Keling, o‘zbekistonlik founderni global maydonda birgalikda qo‘llab-quvvatlaymiz. 🇺🇿 Product Hunt’da Speko’ga ovoz bering! 🚀 Ovoz berish uchun link shu yerda

🔥2

27 Aug 2026, 07:37 UTC≈1,680 views1 reactionsread 27 August 2026
Video

🚀 Bugun asoschilarimiz uchun navbatdagi amaliy sessiya bo‘lib o‘tmoqda! Bugungi uchrashuvda asoschilarimiz Samira Latipova bilan birgalikda “Growth and CustDev” mavzusida startapni jadal o‘stirish va haqiqiy mijoz ehtiyojlarini aniqlash sirlarini tahlil qilishmoqda⚡️ 📌 Bundan tashqari sessiya davomida: - Startapni barqaror va tezkor o‘stirish (Growth Strategy) - Mijozlarni chuqurroq tushunish va ularning real ehti

👍1

26 Aug 2026, 15:20 UTC≈1,590 views6 reactionsread 27 August 2026

UzCombinatorda startapcha vibe 🚀

🔥4❤‍🔥1🎉1

26 Aug 2026, 15:18 UTC≈1,690 views12 reactionsread 27 August 2026
Video message

Video message, posted without a caption

9👍3

26 Aug 2026, 14:31 UTC≈1,660 views32 reactions50 Starsread 27 August 2026
Photo

🚀 UzCombinator 2-mavsumiga qabul qilingan loyihalar bilan tanishing! Sanoatda dron muhandislariga talab ortib bormoqda, lekin maktablarda buni o‘rgatishda xavfsizlik va tayyor metodika muammosi bor ⚠️ UzCombinator 2-mavsum loyihalaridan biri Drone Edu Train aynan shu muammoga amaliy yechim taklif etmoqda! 🚀 💡Dron Edu Train tomonidan taqim qilinadigan maxsus "10+1" o‘quv komplekti orqali: • Dronlar 250g dan yengil

🔥157👍5😍3🎉1😁1

26 Aug 2026, 11:42 UTC≈1,700 views30 reactionsread 27 August 2026
Photo

🚀UzCombinator’da yangi hamkorliklar davom etmoqda! 📆 Bugun UzCombinatorga O'zbekistondagi yetakchi xosting provayderlaridan biri aHOST kompaniyasi asoschisi va rahbari Artur Suvanov va texnik direktor Sergey Bogdanov tashrif buyurishdi. Tashrif davomida UzCombinator va aHOST o'rtasida kelajakdagi hamkorlik masalalari, hamda startaplarimiz uchun birgalikda yaratishimiz mumkin bo‘lgan yangi imkoniyatlar haqida muhoka

🔥127🏆6🎉3😁2

25 Aug 2026, 11:58 UTC≈1,890 views11 reactionsread 27 August 2026
Photo

🚀 “How to Get Your First 50–100 Customers?” sessiyadan lavhalar Bugun asoschilarimiz Otabek Suvonov bilan birinchi 50–100 ta mijozni topish va jalb qilish haqida amaliy sessiyada qatnashdilar⚡️ 📌 Sessiya davomida asoschilarimiz: - birinchi mijozni topish strategiyalarini o‘rgandilar - target auditoriyani aniqlash va tushunishni shakllantirdilar - mijoz bilan to‘g‘ri muloqot qilish yondashuvlarini o‘rgandilar - das

🔥74

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Posts edited after publishing

@uzcombinator edited 1 post 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
25 August 2026
Most recent edit
25 August 2026

Citation-graph rank

Citation-graph rank — 4,808 of 1,624,174entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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 32 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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.

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

“UzCombinator” (@uzcombinator), 8,781 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/uzcombinator.

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.