Telegram RegisterThe public register of Telegram
Telegram profile photo for УВБ-76 логи

Channel

УВБ-76 логи

@uvb76logs

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

94,831subscribers

+1,616 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001831345427
TypeChannel
Username@uvb76logs
DescriptionКонтакт для связи по рекламе и другим вопросам @uvb76logs_adm
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 October 2026
Measurements held39
Confirmed unchanged1 time, most recently 15 October 2026
On Telegramt.me/uvb76logs

Topic

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

Growth

92,58095,95794,268.56 August 2026 — 93,215 subscribers7 August 2026 — 93,180 subscribers7 August 2026 — 93,218 subscribers8 August 2026 — 93,228 subscribers10 August 2026 — 93,141 subscribers11 August 2026 — 93,065 subscribers12 August 2026 — 93,048 subscribers13 August 2026 — 92,882 subscribers14 August 2026 — 92,924 subscribers15 August 2026 — 92,892 subscribers17 August 2026 — 92,953 subscribers18 August 2026 — 92,939 subscribers19 August 2026 — 92,964 subscribers20 August 2026 — 92,966 subscribers21 August 2026 — 92,818 subscribers22 August 2026 — 92,744 subscribers24 August 2026 — 92,718 subscribers25 August 2026 — 92,709 subscribers26 August 2026 — 92,680 subscribers27 August 2026 — 92,580 subscribers28 August 2026 — 93,475 subscribers29 August 2026 — 93,624 subscribers30 August 2026 — 94,029 subscribers31 August 2026 — 95,311 subscribers1 September 2026 — 95,653 subscribers2 September 2026 — 95,806 subscribers3 September 2026 — 95,833 subscribers5 September 2026 — 95,957 subscribers9 September 2026 — 95,800 subscribers11 September 2026 — 95,614 subscribers13 September 2026 — 95,591 subscribers15 September 2026 — 95,637 subscribers17 September 2026 — 95,653 subscribers24 September 2026 — 95,296 subscribers3 October 2026 — 95,080 subscribers8 October 2026 — 94,996 subscribers12 October 2026 — 94,885 subscribers14 October 2026 — 94,891 subscribers15 October 2026 — 94,831 subscribers94,8316 August 202615 October 2026
39 measurements spanning 70 days, net +1,616. 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 92,073–96,464 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 39
Measured (UTC)SubscribersChange
15 Oct 2026, 09:0594,831-60
14 Oct 2026, 07:5794,891+6
12 Oct 2026, 17:1894,885-111
8 Oct 2026, 06:1794,996-84
3 Oct 2026, 20:1695,080-216
24 Sept 2026, 22:3895,296-357
17 Sept 2026, 03:4095,653+16
15 Sept 2026, 06:2195,637+46
13 Sept 2026, 14:5995,591-23
11 Sept 2026, 17:5995,614-186
9 Sept 2026, 06:5695,800-157
5 Sept 2026, 20:5795,957+124
3 Sept 2026, 19:2195,833+27
2 Sept 2026, 12:5295,806+153
1 Sept 2026, 11:5795,653+342
31 Aug 2026, 13:0395,311+1,282
30 Aug 2026, 09:5794,029+405
29 Aug 2026, 07:4693,624+149
28 Aug 2026, 08:5493,475+895
27 Aug 2026, 12:2592,580first reading

Engagement

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

ERR · 30 days
25.7%
avg views ÷ 94,831 subscribers
Avg views / post
24,400
43 posts measured
Reaction rate
1.47%
reactions ÷ views · ER floor
Posts in window
43
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.

What these figures were computed from
WindowRolling 30 days · latest post in window 15 October 2026
Posts held116 (20 July 2026 – 15 October 2026)
Views total1,049,900
Reactions total15,405
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Oct 2026, 02:26 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

Photos
30
Videos
283
Links
601

Lifetime counters from Telegram’s own channel header, read 16 October 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.

Video runtime
31s
Average length
16s

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

53,551 reactions across 115 posts, in 73 distinct kinds. The most used accounts for 30.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 539109063696109900916,24730.3%
🫡7,98314.9%
custom 54158412621776260857,46813.9%
✍3,9657.40%
custom 54519989769349495273,9297.34%
🤣2,4614.60%
❤2,2324.17%
😁2,0173.77%
custom 54496981071199048291,4812.77%
🔥1,3462.51%
👍4830.902%
😱3840.717%
🤔2940.549%
🤡2830.528%
👀1910.357%
😨1630.304%
🌚1450.271%
💩1420.265%
❤‍🔥1170.218%
🏆1140.213%
53 further kinds2,1063.93%

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 115 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 53,551 reactions 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 20 July 2026 to 15 October 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
116
across the posts below
Posts paid on
38
of 115 we hold a reading for · 33%
Most on one post
52
single highest reading

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 116 most recent posts we hold for this entry, published 20 July 2026 to 15 October 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

15 Oct 2026, 16:32 UTC≈10,200 views208 reactionsread 16 October 2026
File

🔥 5-е сообщение за сегодня 15.10.26 19:24 МСК НЖТИ 90711 РАУТОМАХ 0283 3764 #НЖТИ 💙 УВБ-76 логи 🎥 стрим 💬 чат

🫡94custom 541584126217762608551custom 539109063696109900919👀14✍11custom 54519989769349495276❤4🔥3

15 Oct 2026, 15:35 UTC≈11,700 views251 reactionsread 16 October 2026
File

🔥 4-е сообщение за сегодня 15.10.26 18:28 МСК НЖТИ 70382 ФИКЦИЯ 9703 0657 #НЖТИ 💙 УВБ-76 логи 🎥 стрим 💬 чат

custom 539109063696109900993🫡58custom 541584126217762608530✍26custom 545199897693494952711🤣10👻9💯9

15 Oct 2026, 14:09 UTC≈14,500 views327 reactionsread 16 October 2026
File

🔥 3-е сообщение за сегодня 15.10.26 14:41 МСК НЖТИ 29625 НОКДАУН 2567 1173 РОГОЖА 0941 0368 #НЖТИ #двойное 💙 УВБ-76 логи 🎥 стрим 💬 чат

custom 5391090636961099009133custom 541584126217762608570🫡51✍22🔥12custom 545199897693494952712😁10🎃9

15 Oct 2026, 14:06 UTC≈12,200 views221 reactionsread 16 October 2026
File

🔥 2-е сообщение за сегодня 15.10.26 13:49 МСК НЖТИ 02095 СУЛЬФОСОЛЬ 0577 5367 #НЖТИ 💙 УВБ-76 логи 🎥 стрим 💬 чат

custom 539109063696109900987🫡37✍31custom 541584126217762608522🤣17custom 54519989769349495278☃7🌚4

15 Oct 2026, 14:04 UTC≈12,100 views217 reactionsread 16 October 2026
File

🔥 Сообщение за сегодня 15.10.26 13:24 МСК НЖТИ 21222 МНЕМОСХЕМА 1180 4865 ХРУПОТКАЧ 6995 1729 #НЖТИ #двойное 💙 УВБ-76 логи 🎥 стрим 💬 чат

custom 539109063696109900987🫡41custom 541584126217762608533✍28👨‍💻7😁6custom 54519989769349495275🔥4

14 Oct 2026, 15:45 UTC≈23,400 views265 reactionsread 16 October 2026
File

🔥 3-е сообщение за сегодня 14.10.26 18:39 МСК НЖТИ 35641 ИШИКТОН 3365 8041 #НЖТИ 💙 УВБ-76 логи 🎥 стрим 💬 чат

🫡116✍66custom 541584126217762608531custom 539109063696109900929👀7❤5💋3🕊3

14 Oct 2026, 12:37 UTC≈16,800 views343 reactionsread 16 October 2026
File

🔥 2-е сообщение за сегодня 14.10.26 15:28 МСК НЖТИ 31899 ДРАПОТЫЛ 5029 0844 ВОЛОХЛЕВ 9232 4881 #НЖТИ #двойное 💙 УВБ-76 логи 🎥 стрим 💬 чат

custom 5415841262177626085128🤣108custom 539109063696109900931🫡27✍18🤔13🎃6💋4

14 Oct 2026, 12:29 UTC≈16,200 views259 reactionsread 16 October 2026
File

🔥 Сообщение за сегодня 14.10.26 15:20 МСК НЖТИ 75859 ЗАКОПУНШ 9186 1994 #НЖТИ 💙 УВБ-76 логи 🎥 стрим 💬 чат

custom 5415841262177626085111🫡58custom 539109063696109900932✍24🤣10🌚9👻7🎃4

11 Oct 2026, 14:33 UTC≈25,300 views397 reactionsread 15 October 2026
File

🔥 2-е сообщение за сегодня 11.10.26 17:25 МСК НЖТИ 24943 БЛОКОПУСК 7362 6129 #НЖТИ 💙 УВБ-76 логи 🎥 стрим 💬 чат

🫡212custom 539109063696109900973✍35custom 541584126217762608531🍾13🔥13❤6👍5

11 Oct 2026, 12:47 UTC≈21,900 views279 reactionsread 15 October 2026
File

🔥 Сообщение за сегодня 11.10.26 15:41 МСК НЖТИ 62070 БЛИЦОТИП 8186 3319 #НЖТИ 💙 УВБ-76 логи 🎥 стрим 💬 чат

custom 5391090636961099009116🫡59✍45custom 541584126217762608526🤔14🤣6🏆5🍓3

9 Oct 2026, 14:26 UTC≈23,600 views324 reactions1 Starread 15 October 2026
File

🔥 2-е сообщение за сегодня 09.10.26 17:05 МСК НЖТИ 01386 БАЛОКРОТ 8445 9873 #НЖТИ 💙 УВБ-76 логи 🎥 стрим 💬 чат

custom 5391090636961099009122🫡65custom 541584126217762608547✍38🤷‍♂14😁11🥰9🤡8

9 Oct 2026, 12:44 UTC≈29,200 views444 reactionsread 15 October 2026
File

🔥 Сообщение за сегодня 09.10.26 15:38 МСК НЖТИ 76999 ПРОБОИНА 5631 3486 #НЖТИ 💙 УВБ-76 логи 🎥 стрим 💬 чат

custom 5391090636961099009170😱87custom 541584126217762608553🫡39🤣37✍24🌚10🔥10

Showing the 12 most recent of 116 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.

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

“УВБ-76 логи” (@uvb76logs), 94,831 subscribers as measured 15 October 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.