National news — 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 8 August 2026 and assigned it the closest of 31 fixed categories, at 98% 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.
Observations
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Views and reactions moved apart
On 3 of the 196 posts we watched over 30days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.0182 reactions per view.
Each interval, as we read it — views and reactions before and after
Expectedis the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).
What this does and does not say.It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.
Recorded under the key view_reaction_decoupling, last confirmed 12 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
Growth
9 measurements spanning 6 days, net +15,274. 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 1,178,495–1,203,085 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
12 Aug 2026, 14:15
1,200,248
+4,133
11 Aug 2026, 17:02
1,196,115
+2,327
10 Aug 2026, 15:31
1,193,788
+4,600
9 Aug 2026, 18:21
1,189,188
+4,079
8 Aug 2026, 20:16
1,185,109
+3,777
7 Aug 2026, 19:02
1,181,332
-3,043
6 Aug 2026, 18:22
1,184,375
-599
6 Aug 2026, 17:14
1,184,974
no change
6 Aug 2026, 16:41
1,184,974
first reading
Engagement
207 posts held, back to 6 August 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 17 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
7.67%
avg views ÷ 1,200,248 subscribers
Avg views / post
92,100
207 posts measured
Reaction rate
1.88%
reactions ÷ views · ER floor
Posts in window
207
of 207 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 12 August 2026
Posts held
207 (6 August 2026 – 12 August 2026)
Views total
19,058,000
Reactions total
358,155
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
13 Aug 2026, 00:17 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
≈47,100
Videos
≈22,200
Links
≈63,900
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Video runtime
46m 20s
Average length
43s
Measured directly from 64 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.
View velocity
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 196 of this channel’s own posts over the last 30 days (1 of the 24-hour readings behind this are interpolated, not measured directly): across 163of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 2.5 hours of being posted; a typical post has already reached 30.2% of its 24-hour view count within the first hour, and 73.7% within the first six; the median 24-hour reach across those posts is 91,150 views — 7.59% of this channel’s own subscriber count (90th percentile 102,000).
8 most recently posted, with a view-velocity reading
60 minutes: 24,700 → 3.0 hours: 48,605 interp. → 6.0 hours: 60,400still climbing at last reading
not yet at 24h
89 minutesprovisional — final view count still climbing
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed viewsis the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
Reaction mix
358,155 reactions across 207 posts, in 13 distinct kinds. The most used accounts for 31.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🤬
113,592
31.7%
👍
41,866
11.7%
🙏
41,552
11.6%
🤡
39,881
11.1%
😢
38,883
10.9%
❤
29,335
8.19%
🔥
26,660
7.44%
😁
10,637
2.97%
😱
5,500
1.54%
👎
4,240
1.18%
🤔
4,094
1.14%
👏
1,593
0.445%
🍾
322
0.09%
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 207 of the 207 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 358,155reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 207 most recent posts we hold, published 6 August 2026 to 12 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
32
across the posts below
Posts paid on
21
of 207 we hold a reading for · 10%
Most on one post
10
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @novini_ukrtg. 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 207 most recent posts we hold for this entry, published 6 August 2026 to 12 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.
🔥 ЗСУ провели масштабний контрнаступ: DeepState вперше за останні місяці вніс зміни до карти, які не розголошувалися
Нагадаємо, з січня по серпень ДШВ у ході наступальної операції на Олександрівському напрямку звільнили 745 км² території.
Серед звільнених — Зелений Гай, Новохатське, Грушівське, Толстой, Зірка, Ялта, Піддубне, Мирне, Воскресенка, Січневе, Воронне, Тернове, Березове, Степове, Калинівське, Привілля, З…
Повітряні сили ЗСУ більше не повідомлятимуть у щоденних зведеннях кількість запущених росією ракет, — Юрій Ігнат
Тепер такі дані публікуватимуть лише раз на місяць, а причину зміни формату поки не повідомляють.
Український Телеграм
Українці побачили сонячне затемнення: у столиці Сонце було закрите лише на 2,66%, а на заході країни — понад 40%
Найбільше затемнення в Україні спостерігатиметься в Ужгороді, де Сонце буде закрите на 43,44%, а пік явища очікується о 20:47.
Український Телеграм
🔥 Офіційно: вночі в Новоросійську уражено чотири кораблі російського військового флоту, — Генеральний штаб
🟡2 фрегати «Адмірал Макаров» та «Адмірал Ессен».
🟡Малий ракетний корабель «Буян-М».
🟡Корабель охорони «Василь Биков».
Український Телеграм
❗️Абітурієнти, НМТ дозволять складати повторно в тому ж році для покращення бала, — Зеленський анонсував зміни
Президент закликав скоротити кількість тестувань та переглянути терміни їх проведення для зменшення навантаження на дітей.
Український Телеграм
❗️путін зупинить війну, у нас є план, — Володимир Зеленський додав: «Ми розуміємо, що маємо робити».
«Україна має перенести війну на територію рф, щоб росіяни відчули її наслідки та почали тиснути на власну владу».
Український Телеграм
Маршрут поїзда Київ — Кишинів доповнили постійною зупинкою на станції Ревака поблизу аеропорту Кишинева, — УЗ
Станція розташована поруч з аеропортом, а дістатися до нього можна буде на безкоштовних шатлах для пасажирів.
Для зупинки біля аеропорту потрібно попередити провідника. Поки що вона передбачена лише для рейсів Київ → Кишинів.
Український Телеграм
⚡️ НЕ пропустіть: лише сьогодні з 20:15 жителі західної частини України зможуть побачити сонячне затемнення
Загалом сьогодні — унікальний астрономічний день: сонячне затемнення, парад планет і пік зорепаду Персеїди.
Таке астрономічне поєднання повториться через 70 років.
Український Телеграм
❤388👍101👏41🤡27🙏15😁12🔥6
Showing the 12 most recent of 207 posts we hold for @novini_ukrtg. 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.
Posts edited after publishing
@novini_ukrtg edited 17 posts 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
7 August 2026
Most recent edit
12 August 2026
Citation-graph rank
Citation-graph rank — 203,144 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
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.
Domains linked from posts
5 domainsthis channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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.
“Український Телеграм 🇺🇦” (@novini_ukrtg), 1,200,248 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/novini_ukrtg.
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.
