4 measurements spanning 6 days, net +167. 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 2,655–2,872 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
12 Aug 2026, 11:09
2,847
+21
9 Aug 2026, 21:22
2,826
+140
6 Aug 2026, 14:54
2,686
+6
6 Aug 2026, 08:20
2,680
first reading
Engagement
25 posts held, back to 21 July 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 2 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
77.9%
avg views ÷ 2,847 subscribers
Avg views / post
2,220
25 posts measured
Reaction rate
0.44%
reactions ÷ views · ER floor
Posts in window
25
of 25 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
Window
Rolling 30 days · latest post in window 7 August 2026
Posts held
25 (21 July 2026 – 7 August 2026)
Views total
55,437
Reactions total
244
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 16:14 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
1m 28s
Average length
44s
Measured directly from 2 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
203 reactions across 20 posts, in 10 distinct kinds. The most used accounts for 42.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
86
42.4%
custom 5215218645382211332
32
15.8%
👍
28
13.8%
😱
21
10.3%
custom 5287448836975903195
15
7.39%
custom 5818802717455290572
14
6.90%
👀
3
1.48%
👏
2
0.985%
⚡
1
0.493%
😨
1
0.493%
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 areTelegram’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 25 of the 25 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 244reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 25 most recent posts we hold, published 21 July 2026 to 7 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.
⚠️ SHOSHILINCH OGOHLANTIRISH!
Davlat tashkilotlari hamda xo‘jalik yurituvchi subyektlar DIQQATIGA ✅
👨💻 Kiberxavfsizlik markazining UZCERT xizmati tomonidan olib borilgan o‘rganishlar natijasida kiberjinoyatchilar O‘zbekiston Respublikasidagi tashkilotlari hamda xo‘jalik yurituvchi subyektlarning kompyuter va serverlariga RDP (Remote Desktop Protocol) xizmati orqali ruxsatsiz kirishga qaratilgan ommaviy kiberhuju…
⚠️ Enterprise Java platformalaridagi xavfli zaifliklar orqali kiberjinoyatchilar serverlarda ixtiyoriy buyruqlarni bajarishi mumkin!
💻 Korporativ axborot tizimlarida keng qo‘llaniladigan Enterprise Java platformalarida aniqlangan bir qator xavfli zaifliklar kiberxavfsizlik mutaxassislari e’tiborini tortmoqda. Black Hat USA 2026 konferensiyasida taqdim etilgan yangi tadqiqot natijalariga ko‘ra, bir nechta mashhur J…
⚠️ Linux yadrosidagi Bridge (STP) zaifligi uchun ommaviy PoC e’lon qilindi: tizimlarda zudlik bilan xavfsizlik yangilanishini amalga oshirish tavsiya etiladi!
😁 Linux operatsion tizimi yadrosining (Linux Kernel) tarmoq ko’prigi (Bridge) quyi tizimida aniqlangan xavfli Use-After-Free (UAF) turidagi zaiflik uchun ommaviy Proof-of-Concept (PoC) kodi e’lon qilindi. Mazkur holat zaiflikdan amalda foydalanishni sezilarl…
⚠️ Cisco IOS XE dasturiy ta’minotida aniqlangan o’ta muhim zaifliklar bartaraf etildi: tashkilotlarga zudlik bilan xavfsizlik yangilanishlarini bajarish tavsiya etiladi!
💻 Cisco kompaniyasi korporativ tarmoqlarda keng qo’llaniladigan Cisco IOS XE Software dasturiy ta’minotida aniqlangan bir nechta o’ta muhim xavfsizlik zaifliklarini bartaraf etuvchi yangilanishlarni e’lon qildi. Mazkur zaifliklar muvaffaqiyatli eks…
🚨 Django’da to’rtta xavfli zaiflik bartaraf etildi: Dasturchilar va tizim administratorlariga zudlik bilan xavfsizlik yangilanishini bajarish tavsiya etiladi!
⚠️ Python dasturlash tilida yaratilgan eng ommabop veb-freymvorklardan biri bo’lgan Django uchun navbatdagi xavfsizlik yangilanishi e’lon qilindi. Ishlab chiquvchilar tomonidan taqdim etilgan Django 6.0.8 hamda Django 5.2.17 versiyalarida aniqlangan to’rtta …
⚠️ OWASP yangi "Subtractive Security Top 10" loyihasini taqdim etdi: kiberjinoyatchilar foydalanishi mumkin bo’lgan hujum yo’llarini bartaraf etish endi ustuvor vazifa!
💻 Zamonaviy kiberxavfsizlik amaliyotida tashkilotlar ko’pincha xavfsizlikni kuchaytirish uchun yangi vositalar, monitoring tizimlari va himoya mexanizmlarini joriy etishga ustuvor ahamiyat beradi. Biroq dunyodagi eng nufuzli axborot xavfsizligi ham…
⚠️ Apache NiFi’dagi xavfli zaifliklar tashkilotlar axborot tizimlarini jiddiy xavf ostida qoldirmoqda! Zudlik bilan xavfsizlik yangilanishlarini o’rnating!
🌐 Ma’lumotlar oqimini boshqarish va avtomatlashtirish uchun keng qo’llaniladigan Apache NiFi platformasida bir nechta xavfli zaifliklar aniqlandi. Mazkur zaifliklardan foydalanish orqali tajovuzkorlar ayrim holatlarda avtorizatsiya cheklovlarini chetlab o’tishi…
📱 macOS tizimidagi CUPS zaifligi uchun ommaviy PoC e’lon qilindi: tajovuzkorlar root darajasidagi huquqlarni qo’lga kiritishi mumkin!
⚠️ Apple operatsion tizimlarida aniqlangan yangi zaiflik kiberxavfsizlik mutaxassislarining jiddiy e’tiborini tortmoqda. Gap CVE-2026-39875 identifikatori bilan ro’yxatga olingan Common UNIX Printing System (CUPS) zaifligi haqida bormoqda. Mazkur zaiflik uchun ommaviy Proof of Conce…
⚠️ Haftasiga 127 million marta yuklab olinadigan Keyv npm paketiga zararli kod joylashtirilganligini bilarmidingiz? Siz ham zarralangan bo’lishingiz mumkin ogoh bo’ling!
💻 Ochiq kodli dasturiy ta’minot (Open Source Software) zamonaviy dasturchilar va tashkilotlar faoliyatining ajralmas qismiga aylangan. Dunyo bo’ylab millionlab dasturchilar kundalik faoliyatida npm (Node Package Manager) platformasidagi kutubxonal…
⚠️ Parol ham, barmoq izi ham kerak emasmi? Google Passkey tizimidagi yangi zaiflik foydalanuvchilar uchun qanday xavf tug’dirmoqda?
💻 Kiberxavfsizlik sohasida so’nggi yillarning eng muhim yangiliklaridan biri sifatida e’tirof etilgan Passkey texnologiyasi foydalanuvchilarni parol bilan bog’liq tahdidlardan himoya qilish maqsadida ishlab chiqilgan edi. Ushbu texnologiya fishing hujumlari, parolni taxmin qilish (Bru…
👨💻 Har bir kiberxavfsizlik mutaxassisi ko'zdan kechirishi kerak bo'lgan GitHub loyihasi – Awesome Hacking
✅ Kiberxavfsizlik sohasida bilim va ko'nikmalarini rivojlantirishni istagan mutaxassislar uchun Awesome Hacking loyihasi eng foydali resurslardan biri hisoblanadi. Ushbu loyiha GitHub platformasida jamlangan bo'lib, axborot xavfsizligining turli yo'nalishlariga oid 50 dan ortiq maxsus resurslar to'plamini o'z…
🚨 Bitta SSH ulanishi qurilmangizni xavf ostiga qo’yishi mumkin! libssh2’dagi kritik zaifliklar orqali zararli serverlar mijoz qurilmalarini nishonga olmoqda!
💻 Axborot xavfsizligi sohasida keng qo’llaniladigan libssh2 kutubxonasida aniqlangan bir nechta yuqori xavflilik darajasiga ega zaifliklar millionlab SSH va SFTP mijoz dasturlarini jiddiy tahdid ostida qoldirmoqda. Mazkur zaifliklardan foydalanish orqali kibe…
🔥4👍2😱2
Showing the 12 most recent of 25 posts we hold for @uzcert_live. 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.
Polls
The 3 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
✈️ Do'stingiz sizga "Telegram Premium sovg'asini olish uchun ovoz berib yuboring" degan havola yubordi. Havolani ochganingizda telefon raqamingiz va Telegram tasdiqlash kodini kiritish so'raldi.
Qaysi harakat eng to'g'ri❓
🅰️ ) Havola domeni tanish ko'rinsa, kodni kiritaman.4%
🔤 ) Kodni faqat bir marta kiritaman, keyin sessiyalarni tekshiraman.3%
🔤 ) Tasdiqlash kodini kiritmayman va do'stim bilan boshqa aloqa orqali bog'lanaman.91%
🔤 ) VPN orqali kirib kodni kiritaman.2%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
🏢 Korxonaning domen administratori hisobidan ish vaqtidan tashqarida yangi administrator hisobi yaratildi. Ushbu faoliyatni tasdiqlovchi dalilni aniqlash uchun qaysi log eng muhim hisoblanadi ❓
🅰️ ) DNS loglari;13%
🔤 ) DHCP loglari;7%
🔤 ) Windows Security Event Log (4720, 4728, 4732 va tegishli audit hodisalari);80%
🔤 ) Printer loglari;0%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
📨 Elektron pochta orqali kutilmaganda yuborilgan quyidagi fayllardan qaysi biri foydalanuvchi uchun eng katta kiberxavf tug‘dirishi mumkin ❓
🅰️ ) report.pdf8%
🔤 ) image.jpg3%
🔤 ) document.txt5%
🔤 ) invoice.pdf.exe84%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 25 most recent posts we hold, published 21 July 2026 to 7 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank
Citation-graph rank — 21,256 of 1,151,006entries 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
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 24 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 12 August 2026 — this
entry's latest reading, not the date you are reading this.
“UzCERT Live” (@uzcert_live), 2,847 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/uzcert_live.
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.
