Telegram RegisterThe public register of Telegram

Channel

Новини Суми Події Сумах

@trukha_Ua4

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

9,735subscribers

-57 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001181852185
TypeChannel
Username@trukha_Ua4
DescriptionЗ усіх питань звертайтесь @Topinfo_ADM Поділитись новиною можна @Top_info_ua_bot
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/trukha_Ua4

Topic

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 10 August 2026 and assigned it the closest of 31 fixed categories, at 99% 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.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@suspilnesumy/470807 Aug 2026, 05:41 UTC@trukha_Ua4/34395 · this entry7 Aug 2026, 05:41 UTC1.00under a minute
@suspilnesumy/470837 Aug 2026, 06:01 UTC@trukha_Ua4/34398 · this entry7 Aug 2026, 06:01 UTC1.00under a minute
@suspilnesumy/470887 Aug 2026, 06:47 UTC@trukha_Ua4/34403 · this entry7 Aug 2026, 06:47 UTC1.00under a minute
@suspilnesumy/470897 Aug 2026, 07:41 UTC@trukha_Ua4/34404 · this entry7 Aug 2026, 07:41 UTC1.00under a minute
@suspilnesumy/470907 Aug 2026, 08:42 UTC@trukha_Ua4/34405 · this entry7 Aug 2026, 08:42 UTC1.00under a minute
@suspilnesumy/470947 Aug 2026, 15:01 UTC@trukha_Ua4/34409 · this entry7 Aug 2026, 15:01 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@suspilnesumy11 (8/8 hand-verifiable sample passed)1.00under a minute@suspilnesumy (101)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 10 of the 10 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 15 comparable posts for this entry, running 7 August 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @suspilnesumy. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 8 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

9,7359,7929,763.57 August 2026 — 9,792 subscribers7 August 2026 — 9,792 subscribers8 August 2026 — 9,761 subscribers11 August 2026 — 9,735 subscribers7 August 202611 August 2026
4 measurements spanning 4 days, net -57. 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 9,726–9,801 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 12:529,735-26
8 Aug 2026, 17:419,761-31
7 Aug 2026, 18:019,792no change
7 Aug 2026, 17:569,792first reading

Engagement

83 posts held, back to 7 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 14 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
2.56%
avg views ÷ 9,735 subscribers
Avg views / post
249
83 posts measured
Reaction rate
0.769%
reactions ÷ views · ER floor
Posts in window
83
of 83 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 71 of 83 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 12 August 2026
Posts held83 (7 August 202612 August 2026)
Views total20,690
Reactions total141
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 14:53 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
9,880
Videos
1,200
Links
1,350

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
6m 05s
Average length
1m 13s

Measured directly from 5 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

141 reactions across 71 posts, in 8 distinct kinds. The most used accounts for 34.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👎4934.8%
🙏4129.1%
3424.1%
😱74.96%
🔥42.84%
😭32.13%
😢21.42%
🌚10.709%

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 71 of the 83 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 141reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 83 most recent posts we hold, published 7 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.

Recent posts

12 Aug 2026, 12:59 UTC80 viewsread 12 August 2026
Photo

🛑 Нацполіція провела понад 400 обшуків і припинила роботу 94 шахрайських call-центрів Загалом проведено 411 обшуків та припинено діяльність 94 шахрайських call-центрів. У приміщеннях поліцейські виявили 1794 повністю обладнані робочі місця. 26 фігурантам уже повідомлено про підозру. Під час слідчих дій вилучено 3336 одиниць комп’ютерної техніки, 1346 телефонів, понад 5200 SIM-карток, 90 банківських карток, засоби д

12 Aug 2026, 12:49 UTC92 views1 reactionsread 12 August 2026
Video

Три КАБи влучили в центральну частину Стецьківки. Атака армії РФ сталася сьогодні близько 15:00. Загиблих та поранених немає, пошкоджено до 10 приватних будинків, — повідомив Суспільному староста села Юрій Лисенко. На відео перші хвилини після ударів. Кадри Суспільному надав Юрій Лисенко.

1

12 Aug 2026, 09:02 UTC176 views2 reactionsread 12 August 2026
Photo

РФ атакувала цивільну інфраструктуру в Роменській, Недригайлівській, Коровинській та Сумській громадах, — ДСНС. Атаки були у ніч з 11 на 12 серпня. "Також під ударом ворожого дрона опинилася цивільна автівка в Сумах. Фахівці ДСНС гасили пожежі та проводили обстеження територій. Всі осередки горіння ліквідовано", — написали в ГУ ДСНС у Сумській області. Як передавала кореспондентка Суспільного, вчора вночі РФ вдарил

1🙏1

12 Aug 2026, 07:23 UTC188 viewsread 12 August 2026

Приміські рейси сполученням Конотоп—Шостка сьогодні припиняють рух через коливання напруги в контактній мережі, — Укрзалізниця. Тимчасово не курсують: 🚊№6544/6543 Конотоп-Пасажирський – Шостка 🚊№6546/6545 Шостка – Конотоп-Пасажирський.

12 Aug 2026, 04:14 UTC237 views5 reactionsread 12 August 2026
Photo

Двоє людей загинули, ще десятеро поранені через обстріли на Сумщині, — поліція. 🔹Сумська громада. Загинув 61-річний чоловік, який в момент удару КАБ був за кермом автомобіля. Поранені дві жінки та два чоловіки. Крім того, до лікарні звернулася жінка, травмована 10 серпня. 🔹У Великописарівській громаді внаслідок влучання дрону в будинок в ніч на 11 серпня загинув загинув 62-річний чоловік, ще один чоловік — поранени

4👎1

11 Aug 2026, 20:46 UTC257 views4 reactionsread 12 August 2026

У Ромнах та районі чути вибухи, передає кореспондентка Суспільного.

🙏31

11 Aug 2026, 19:05 UTC130 views1 reactionsread 12 August 2026
Photo

🔹«Це вже третій раз». Через російський авіаудар у Сумах загинув чоловік, пошкоджені будинки та авто. 🔹«Кожна моя посилка відправлена — це наче своєму, рідному», — дружина загиблого військового про чоловіка та волонтерство. 🔹Зазнав травм під час ліквідації наслідків атаки РФ: у Сумах помер рятувальник Олексій Столяренко. 🔹У сумському притулку побільшало тварин, яких залишають через виїзд: волонтери почали приймати

1

11 Aug 2026, 19:05 UTC123 viewsread 12 August 2026

У Конотопі немає водопостачання через атаку РФ, повідомив міський голова Артем Семеніхін. Введені аварійні графіки, зазначив він.

11 Aug 2026, 17:44 UTC172 views1 reactionsread 12 August 2026

Росія готує мобілізацію на осінь, заявив Зеленський у вечірньому відеозверненні після доповіді очільника ГУР Міноборони Іващенка. За словами президента України, це підтверджується внутрішніми російськими документами. Зеленський стверджує, що Україна готується до активних дій, щоб ускладнити для Росії реалізацію таких планів. Президент визначив відповідні завдання розвідкам і спеціальним службам України.

1

11 Aug 2026, 15:23 UTC215 views2 reactionsread 12 August 2026
Photo

Наслідки авіаудару в Сумах вдень 11 серпня. Російські війська спрямували на місто чотири авіабомби. Одна людина загинула. Пошкоджені та зруйновані близько 20 будинків.

👎2

11 Aug 2026, 13:36 UTC230 views3 reactionsread 12 August 2026
Photo

Армія РФ вдарила по цивільній інфраструктурі Сум чотирма авіабомбами, повідомив очільник ОВА Григоров. Поблизу одного з місць влучання загинув цивільний чоловік. У момент удару він їхав автомобілем. Його особу встановлюють. Пошкоджені та зруйновані близько 20 приватних житлових будинків, а також об’єкти цивільної інфраструктури. Попередньо, поранених немає.

3

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

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

“Новини Суми Події Сумах” (@trukha_Ua4), 9,735 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/trukha_Ua4.

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.