🔥 4-е сообщение за сегодня 09.11.26 14:25 МСК НЖТИ 39523 СМАКОБОЛ 4520 9365 #НЖТИ 💙 УВБ-76 логи 🎥 стрим 💬 чат
🫡121✍57custom 539109063696109900937custom 541584126217762608526😁22custom 545199897693494952714☃8❤7

Channel
@uvb76logs
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts recorded as deleted · Citations · Cite this entry
94,843subscribers
+1,628 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001831345427 |
|---|---|
| Type | Channel |
| Username | @uvb76logs |
| Description | Контакт для связи по рекламе и другим вопросам @uvb76logs_adm |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 63 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/uvb76logs |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 21 August 2026 and assigned it the closest of 31 fixed categories, at 93% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 00:09 | 94,843 | -120 |
| 8 Nov 2026, 13:14 | 94,963 | -79 |
| 7 Nov 2026, 10:06 | 95,042 | -104 |
| 6 Nov 2026, 09:11 | 95,146 | -159 |
| 5 Nov 2026, 08:38 | 95,305 | -52 |
| 4 Nov 2026, 06:50 | 95,357 | -68 |
| 3 Nov 2026, 04:38 | 95,425 | -86 |
| 2 Nov 2026, 04:38 | 95,511 | -21 |
| 1 Nov 2026, 05:28 | 95,532 | -19 |
| 31 Oct 2026, 05:36 | 95,551 | -21 |
| 30 Oct 2026, 09:06 | 95,572 | -12 |
| 29 Oct 2026, 08:30 | 95,584 | +50 |
| 28 Oct 2026, 04:37 | 95,534 | +79 |
| 27 Oct 2026, 01:50 | 95,455 | -13 |
| 26 Oct 2026, 00:49 | 95,468 | +1 |
| 25 Oct 2026, 02:30 | 95,467 | +78 |
| 24 Oct 2026, 00:29 | 95,389 | +109 |
| 22 Oct 2026, 22:30 | 95,280 | +166 |
| 21 Oct 2026, 20:46 | 95,114 | +47 |
| 20 Oct 2026, 13:30 | 95,067 | first reading |
135 posts held, back to 20 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 200 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 9 November 2026 |
|---|---|
| Posts held | 135 (20 July 2026 – 9 November 2026) |
| Views total | 743,500 |
| Reactions total | 10,205 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 19:41 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.
Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
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.
61,665 reactions across 134 posts, in 74 distinct kinds. The most used accounts for 30.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5391090636961099009 | 18,743 | 30.4% | |
| 🫡 | 9,514 | 15.4% | |
| custom 5415841262177626085 | 8,767 | 14.2% | |
| ✍ | 4,979 | 8.07% | |
| custom 5451998976934949527 | 4,217 | 6.84% | |
| 🤣 | 2,614 | 4.24% | |
| ❤ | 2,395 | 3.88% | |
| 😁 | 2,109 | 3.42% | |
| custom 5449698107119904829 | 1,481 | 2.40% | |
| 🔥 | 1,426 | 2.31% | |
| 😱 | 667 | 1.08% | |
| 👍 | 508 | 0.824% | |
| 🤔 | 351 | 0.569% | |
| 🤡 | 316 | 0.512% | |
| 🍾 | 252 | 0.409% | |
| 👀 | 196 | 0.318% | |
| 💩 | 181 | 0.294% | |
| 😨 | 174 | 0.282% | |
| 🌚 | 155 | 0.251% | |
| ❤🔥 | 124 | 0.201% | |
| 54 further kinds | 2,496 | 4.05% |
Custom emoji. 4 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 134 of the 135 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 61,665 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 135 most recent posts we hold, published 20 July 2026 to 9 November 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @uvb76logs. 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 135 most recent posts we hold for this entry, published 20 July 2026 to 9 November 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.
Telegram’s own ‘edited’ marker: 1 of 27 posts held from the last 30 days (3.70%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🔥 4-е сообщение за сегодня 09.11.26 14:25 МСК НЖТИ 39523 СМАКОБОЛ 4520 9365 #НЖТИ 💙 УВБ-76 логи 🎥 стрим 💬 чат
🫡121✍57custom 539109063696109900937custom 541584126217762608526😁22custom 545199897693494952714☃8❤7
🔥 3-е сообщение за сегодня 09.11.26 13:52 МСК НЖТИ 56111 КВАСОСТОЛ 8971 0680 #НЖТИ 💙 УВБ-76 логи 🎥 стрим 💬 чат
🍾128custom 539109063696109900964✍36custom 541584126217762608529custom 545199897693494952713🔥10🎄6😭4
🔥 2-е сообщение за сегодня 09.11.26 11:42 МСК НЖТИ 05030 ЗЛОСЛОВЬЕ 6979 9692 #НЖТИ 💙 УВБ-76 логи 🎥 стрим 💬 чат
custom 5391090636961099009125✍68🫡34custom 541584126217762608520😁16🤬13😱7❤6
🔥 Сообщение за сегодня 09.11.26 11:02 МСК НЖТИ 44702 ЗЕВОСТОРГ 2751 2830 #НЖТИ 💙 УВБ-76 логи 🎥 стрим 💬 чат
✍104custom 539109063696109900947custom 541584126217762608545🫡24❤15😁11👍8🔥5
ℹ️ Приносим извинения за задержку по техническим причинам с публикацией двух сообщений от 05.11.2026 19:09 и 20:04 МСК. На данный момент все проблемы устранены, публикация сообщений ведётся в обычном режиме. 💙 УВБ-76 логи 🎥 стрим 💬 чат
🫡340🤝47💋43❤37custom 545199897693494952719✍11🤣11😭4
🔥 4-е сообщение за вчера 05.11.26 20:04 МСК НЖТИ 17521 ВАТТОФАЙЛ 5059 6881 #НЖТИ 💙 УВБ-76 логи 🎥 стрим 💬 чат
custom 5415841262177626085145✍42custom 539109063696109900942🤣35🫡22custom 545199897693494952711❤8🤔7
🔥 3-е сообщение за вчера 05.11.26 19:09 МСК НЖТИ 25828 БРОНТОЗАВР 8526 1223 #НЖТИ 💙 УВБ-76 логи 🎥 стрим 💬 чат
custom 5391090636961099009139✍59🤣34🫡34🦄26custom 541584126217762608518❤10🤡7
🔥 2-е сообщение за сегодня 05.11.26 11:32 МСК НЖТИ 42005 МИЛЯ 5351 5627 #НЖТИ 💙 УВБ-76 логи 🎥 стрим 💬 чат
custom 5415841262177626085132✍77🫡54custom 539109063696109900927custom 54519989769349495279😱5🍓3🎉3
🔥 Сообщение за сегодня 05.11.26 11:15 МСК НЖТИ 79814 ПОДПУХЛЫЙ 2499 5166 #НЖТИ 💙 УВБ-76 логи 🎥 стрим 💬 чат
custom 5391090636961099009168✍75🫡39custom 541584126217762608528🌭18custom 545199897693494952717❤13🤡11
🔥 Сообщение за сегодня 02.11.26 11:23 МСК НЖТИ 60767 ДУЧЕ 2152 8370 #НЖТИ 💙 УВБ-76 логи 🎥 стрим 💬 чат
custom 5391090636961099009247custom 5415841262177626085125🫡84🤣43✍41custom 545199897693494952721🎃12🔥12
🔥 4-е сообщение за сегодня 26.10.26 16:18 МСК НЖТИ 50962 РЕВОНОРД 8592 8891 Ошибка передачи: первая группа цифр при первом прочтении передана как "60962", второе прочтение "50962" — верное. #НЖТИ #ошибка 💙 УВБ-76 логи 🎥 стрим 💬 чат
custom 5391090636961099009192✍81🫡52custom 541584126217762608538❤18custom 545199897693494952717👍8🤷♂8
🔥 3-е сообщение за сегодня 26.10.26 15:33 МСК НЖТИ 99891 АМАДРИЛЛ 8539 0054 #НЖТИ 💙 УВБ-76 логи 🎥 стрим 💬 чат
custom 5391090636961099009138custom 541584126217762608563🫡46✍30😱12🐳9🗿9🤔8
Showing the 12 most recent of 135 posts we hold for @uvb76logs. 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.
We recorded 3 posts on @uvb76logs as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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.
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 23 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“УВБ-76 логи” (@uvb76logs), 94,843 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/uvb76logs.
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.