Telegram RegisterThe public register of Telegram
Telegram profile photo for Труха⚡️Запоріжжя

Channel

Труха⚡️Запоріжжя

@truexazaporozie

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts edited after publishing · Posts recorded as deleted · Polls · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

285,725subscribers

+8,847 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001689250492
TypeChannel
Username@truexazaporozie
Created25 May 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live18 November 2026
Measurements held67
Confirmed unchanged1 time, most recently 18 November 2026
On Telegramt.me/truexazaporozie

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 8 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 the other topics.

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 in near-verbatim form on 7 other registered channels. 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
@eto_zp/728471 Sept 2026, 10:59 UTC@truexazaporozie/69095 · this entry1 Sept 2026, 16:59 UTC1.006.0 hours
@eto_zp/728973 Sept 2026, 18:10 UTC@truexazaporozie/70406 · this entry23 Sept 2026, 19:03 UTC1.0020 days
@truexazaporozie/72361 · this entry28 Oct 2026, 14:59 UTC@eto_zp/7430128 Oct 2026, 15:05 UTC1.006 minutes
@truexazaporozie/73658 · this entry16 Nov 2026, 22:06 UTC@eto_zp/7484616 Nov 2026, 22:07 UTC0.94under a minute
@truexazaporozie/71907 · this entry20 Oct 2026, 18:46 UTC@eto_zp/7409920 Oct 2026, 18:52 UTC0.815 minutes
@truexazaporozie/73702 · this entry17 Nov 2026, 19:24 UTC@eto_zp/7487017 Nov 2026, 19:42 UTC0.7619 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@eto_zp19 (8/8 hand-verifiable sample passed)0.87under a minutethis entry (13–6)
@truexanewsua12 (8/8 hand-verifiable sample passed)0.9619 minutesthis entry (8–4)
@batalionmonako9 (8/8 hand-verifiable sample passed)1.00under a minute@batalionmonako (5–4)
@chernigiv_truexa7 (7/7 hand-verifiable sample passed)0.92under a minute@chernigiv_truexa (5–2)
@truexakharkiv6 (6/6 hand-verifiable sample passed)1.00under a minuteeven
@truexadnepr6 (6/6 hand-verifiable sample passed)0.98under a minuteeven
@UaOnlii6 (6/6 hand-verifiable sample passed)0.9882 minutes@UaOnlii (5–1)

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. 28 of the 28 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 1,365 comparable posts for this entry, running 5 August 2026 to 17 November 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).

Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 18 November 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

276,277285,725281,0016 August 202618 November 2026
67 measurements spanning 104 days, net +8,847. 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 274,860–287,142 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 67
Measured (UTC)SubscribersChange
18 Nov 2026, 04:21285,725+1,078
15 Nov 2026, 02:06284,647+1,164
11 Nov 2026, 21:50283,483+438
9 Nov 2026, 22:04283,045+503
8 Nov 2026, 10:01282,542+418
7 Nov 2026, 07:15282,124+796
6 Nov 2026, 10:04281,328+1,330
5 Nov 2026, 08:41279,998+1,386
4 Nov 2026, 11:09278,612+352
3 Nov 2026, 14:27278,260+335
2 Nov 2026, 13:19277,925-202
1 Nov 2026, 10:16278,127-128
31 Oct 2026, 08:09278,255-445
30 Oct 2026, 06:57278,700-159
29 Oct 2026, 08:06278,859-70
28 Oct 2026, 04:08278,929-27
27 Oct 2026, 04:20278,956+81
26 Oct 2026, 00:44278,875-104
24 Oct 2026, 21:27278,979-40
23 Oct 2026, 23:06279,019first reading

Engagement

3,318 posts held, back to 5 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 257 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
18.1%
avg views ÷ 285,725 subscribers
Avg views / post
51,700
989 posts measured
Reaction rate
0.708%
reactions ÷ views · ER floor
Posts in window
989
of 3,318 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 988 of 989 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 17 November 2026
Posts held3,318 (5 August 2026 – 17 November 2026)
Views total51,168,043
Reactions total362,103
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 19:51 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
2h 14m
Average length
51s

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

367,709 reactions across 996 posts, in 6 distinct kinds. The most used accounts for 52.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤬191,50052.1%
😢90,70224.7%
❤39,20410.7%
🤣25,7307.00%
👍14,1093.84%
🔥6,4641.76%

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 999 of the 1,000 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 367,709 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 19 October 2026 to 17 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.

Advertising

Ad load
6.70%
67 of 1,000 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
56,400
over 67 measured posts
Median views · rest
54,400
over 933 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 19 October 2026 to 17 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

Telegram’s own ‘edited’ marker: 548 of 989 posts held from the last 30 days (55.4%) 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).

17 Nov 2026, 19:24 UTC≈20,600 views193 reactionsread 17 November 2026

💡❌ Графік відключення світла на завтра, – обленерго. 1.1: 00:00 – 04:30, 10:00 – 15:00, 19:00 – 24:00; 1.2: 00:00 – 04:30, 13:00 – 18:00, 22:00 – 24:00; 2.1: 08:30 – 13:30, 17:30 – 22:30; 2.2: 00:00 – 00:30, 08:30 – 13:30, 17:30 – 22:30; 3.1: 04:00 – 09:00, 18:00 – 23:00; 3.2: 04:00 – 09:00, 13:30 – 18:30; 4.1: 08:30 – 13:30, 17:30 – 22:30; 4.2: 00:00 – 00:30, 05:30 – 10:30, 14:30 – 19:30, 23:30 – 24:00; 5.1: 00:00 …

🤬133❤32😢17🤣10🔥1

17 Nov 2026, 17:53 UTC≈48,200 views538 reactionsread 17 November 2026

💡В області повністю скасовано аварійні відключення електроенергії, – ОВА. Водночас погодинні відключення продовжують діяти. Труха⚡️Запоріжжя | Надіслати новину

🤬271👍116🤣78❤51😢22

17 Nov 2026, 17:53 UTC≈41,300 views187 reactionsread 17 November 2026
Photo

«Підрив довіри до САП і НАБУ? Підірвати можна лише те, що існує». У мережі висміяли та розкритикували спроби «Української правди» Томаша Фіали незграбно виправдати інформацію про корупцію навколо голови САП Клименка та його дружини. ТРУХА⚡️Україна | Надіслати новину

🤣108🤬48❤25😢4👍2

17 Nov 2026, 17:27 UTC≈54,600 views559 reactionsread 17 November 2026

❗️На вечір та ніч отримано «червоний» рівень на балістику, – монітори. Вмикайте сповіщення на мій канал, щоб бути в курсі усіх загроз. Труха⚡️Запоріжжя | Надіслати новину

🤬385😢111🤣38❤16🔥9

17 Nov 2026, 17:10 UTC≈48,200 views232 reactionsread 17 November 2026

⚡️ Підкуп суддів ВАКС та домовленості з прокурорами САП: ексгенпрокурор Кравченко оприлюднив матеріали справи, у якій фігурує найближче оточення керівника САП Клименка. За його словами, дружина очільника САП та керівниця адвокатського бюро Наталія Редіч могли бути причетні до корупційної схеми з підкупу суддів і прокурорів для вирішення справ клієнтів. Зокрема, йдеться про справу мера одного з міст Західної України…

🤣107❤80🤬34😢8🔥3

17 Nov 2026, 16:25 UTC≈61,000 views827 reactionsread 17 November 2026
Video

Момент вчорашнього прильоту по Запоріжжю😱 Водій народився в сорочці. 📱: maksv5666 Труха⚡️Запоріжжя | Надіслати новин

🤬472😢247❤61🤣30👍17

17 Nov 2026, 16:00 UTC≈65,400 views455 reactionsread 17 November 2026
AdvertisementPhoto

❗️OPG вас звечора попереджав, ви його знову проігнорували. Вчора о 21:00 OPG написав, біля 23:00 русня застосує балістику від 10х та реактивні по місту, але ніхто йому знову не повірив. Раніше він попереджав про атаки КАБ, за дві доби до застосування, всі попередження збувались. ❗️Вночі буде новий обстріл про який OPG вже повідомив в своєму каналі👇 #реклама

🤬268❤78🤣76😢33

17 Nov 2026, 15:32 UTC≈64,900 views370 reactionsread 17 November 2026

Летять на Космос! Труха⚡️Запоріжжя | Надіслати новину

🤬266😢61❤19🔥12🤣9👍3

17 Nov 2026, 14:39 UTC≈71,100 views568 reactionsread 17 November 2026

Кількість поранених зросла до 42 людей, – ОВА. Їм надають усю необхідну медичну допомогу. Труха⚡️Запоріжжя | Надіслати новину

😢393🤬120❤30🤣11👍7🔥7

17 Nov 2026, 13:51 UTC≈73,500 views466 reactionsread 17 November 2026

Реактивний БпЛА над Запоріжжям. Курсом на мости! Труха⚡️Запоріжжя | Надіслати новину

🤬339😢69❤23🔥17🤣17👍1

17 Nov 2026, 13:32 UTC≈77,100 views1,014 reactionsread 17 November 2026
Video

Кримський міст зазнав масштабних руйнувань, – СБУ заявила про знищення арки та автомобільного прольоту. Внаслідок спільної спецоперації із Силами оборони повністю знищено одну з металевих арок та автомобільний проліт під нею. Попередньо пошкоджено й залізничну частину мосту. Операція тривала близько місяця та складалася із семи етапів. Для ударів використовували українське озброєння, зокрема ракети-дрони «Паляниця»…

❤545👍224🔥155🤬47🤣43

17 Nov 2026, 12:35 UTC≈77,900 views485 reactionsread 17 November 2026

Курсом на ГЕС, – Черешня. Труха⚡️Запоріжжя | Надіслати новину

🤬355😢86❤22🤣13🔥8👍1

Showing the 12 most recent of 3,318 posts we hold for @truexazaporozie. 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

@truexazaporozie edited 20 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
29 August 2026
Most recent edit
13 November 2026

Posts recorded as deleted after publishing

We recorded 43 posts on @truexazaporozie 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.

First seen missing
8 August 2026
Most recent seen missing
13 November 2026
Median time before seen missing
13 hours
Seen missing in the last 30 days
8

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

11 Nov 2026, 14:56 UTCAnonymous Poll1,230 voters approx.

А поки ви гадаєте про ім’я третього «партнера», давайте вирішимо більш нагальне питання. Що ж робити Михайлу Федорову?

  1. Нехай іде служити: у нього ж є контракти, які він увів;64%
  2. Нехай ще створює фірми: заробляти на оборонці – це ж «критична необхідність» для економіки;10%
  3. Нехай їде за кордон: буде радником до міністрів інших країн і вчить їх «українському диву»;6%
  4. Нехай відкриває піар-агенцію: будуть красиві презентації, які випереджають реальні результати;6%
  5. Свій варіант / Дивитися результати14%

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 1,000 most recent posts we hold (the sample is capped at 1,000), published 19 October 2026 to 17 November 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.

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 3 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.

Names

Channels on the register whose handles appear in this channel's posts.

ДСНС України
@dsns_telegram · 75,556
6 posts
Новини поліції Запорізької області
@police_zp_news · 3,651
5 posts
Батальйон Монако
@batalionmonako · 982
4 posts
ДСНС Запоріжжя
@gu_dsns_zp · 3,279
4 posts
Труха⚡️Україна
@truexanewsua · 3,165,345
4 posts
Запорізька обласна прокуратура
@zap_gp_gov_ua · 1,066
4 posts
Англійська — це легко
@AngliiskaEasy_bot · 10,114
3 posts
Патрульна поліція Запорізької області
@patrolpolicezp · 3,614
2 posts
Адвокат Права
@advocatprava7 · 1,568,310
1 post
Адвокат Мілер
@advokatmillerua · 182,242
1 post
⚡️INFOFAKT УКРАЇНА
@anonymousforan · 6,850
1 post
Генеральний штаб ЗСУ
@GeneralStaffZSU · 64,824
1 post
Кушугумська громада
@kushugumrada · 6,194
1 post
НОВИНА 🇺🇦
@NovynaUKR · 1,453,790
1 post
Труха⚡️Одеса | Новини
@odesatruexa · 264,519
1 post
△ 225 ОШП △
@OSHP_225 · 23,458
1 post
ПЕТРЕНКО ✙
@petrenko_iHS · 34,895
1 post
Рівне⚡️Труха
@rivnetruexa · 116,492
1 post
Шрам
@shrammoleg · 2,189
1 post
Тарас Мельничук: КМУ 🇺🇦 ВРУ
@tmelnychuk · 11,989
1 post
Труха⚡️Дніпро | Новини
@truexadnepr · 399,271
1 post
Труха⚡️Житомир
@truexazhitomir · 165,964
1 post
УС: Україна, новини, політика, війна
@u_now · 1,401,643
1 post
Ужгород⚡️Труха
@uzgorodtruexa · 76,396
1 post

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

Это Запорожье 🇺🇦 Новости
@eto_zp · 174,735
#1
∆✙🍒Гнила черешня🇺🇦✙∆
@gnilayachereha · 412,798
#2
Труха⚡️Україна
@truexanewsua · 3,165,345
#3
ЗАПОРІЖЖЯ.ІНФО🍁
@info_zp · 192,549
#4
Оперативно → by HLEP
@operatyvnohlep · 173,958
#5
ЗаБор Запоріжжя
@zaborzp · 109,648
#6
Лачен пише
@lachentyt · 1,576,100
#7
🇺🇦Запоріжжя Новини🇺🇦Запорожье Новости
@etozp · 73,643
#8
it_is_zp
@it_is_zp_tg · 44,928
#9
Труха⚡️Київ
@truexakyiv · 974,888
#10
ПРУФ | ЗАПОРІЖЖЯ 🇺🇦 ЗАПОРОЖЬЕ
@prufzp · 36,216
#11
Анатолій Куртєв
@kurtievofficial · 47,143
#12
🇺🇦 Іван Федоров | Рада Оборони Запорізької обл.
@ivan_fedorov_zp · 52,192
#13
Повітряні Сили ЗС України / Air Force of the Armed Forces of Ukraine
@kpszsu · 938,170
#14
Україна Online: Новини | Політика
@UaOnlii · 1,534,047
#15
Труха⚡️Дніпро | Новини
@truexadnepr · 399,271
#16
ЗАПОРІЖЖЯ НОВИНИ | ЗАПОРОЖЬЕ НОВОСТИ 🇺🇦 | РАДАР | CВЕТ
@pro_zp_2023 · 26,004
#17
Реальний Київ | Украина
@kievreal1 · 1,550,018
#18
▵ Очі Всюди | Дніпро ▵
@eyes_everywhere_dnipro · 23,361
#19
Хуевое Запорожье | Запоріжжя
@huevoe_zaporozhye · 24,623
#20
🚨Запоріжжя | Оперативно | Аварійка
@avariyka_zaporizg · 49,925
#21
ХДніпро 🇺🇦
@hyevuy_dnepr · 520,852
#22
✙DeepState✙🇺🇦
@deepstateua · 750,207
#23
Труха⚡️Харків | Новини
@truexakharkiv · 589,049
#24
ЗАПОРІЗЬКА СІЧ
@zaporizka_sish · 26,387
#25
Карта повітряних тривог 🇺🇦
@alarmua · 940,548
#26
Михайло Семікін - Запорізька ОВА
@zoda_gov_ua · 33,512
#27
Типичное Запорожье
@typzp · 21,891
#28
Киевский Движ
@k_dvizh · 470,936
#29
ТРИВОГА ЗАПОРІЖЖЯ 🚨
@trevoga_zaporozhe_novini · 11,387
#30
Куди летить? | Тривога
@radar_raketaa · 490,712
#31
БЕЗ БАЙДИ
@bezbaidy · 60,688
#32
Суспільне Запоріжжя
@suspilnezaporizhzhya · 33,005
#33
Славне Запоріжжя 🇺🇦 | Світло
@slavne_zaporizhia · 21,460
#34
5 РЕДАКЦІЯ | Новини Запоріжжя
@five_redakcia · 25,561
#35
ЗАПОРІЖЖЯ.НЕЗЛАМНЕ
@zapnovini · 9,329
#36
Оперативний ЗСУ
@operativnoZSU · 359,454
#37
Повестка🇺🇦Запорожья
@povestkazpchat · 13,722
#38
Регіна Харченко. Секретар Запорізької міської ради
@regina_harchenko · 11,268
#39
Київ ІНФО | Новини Україна 🇺🇦
@kievinfo_kyiv · 1,262,439
#40
Хуйовий Харків 🇺🇦 Хуевый Харьков
@huyovy_kharkiv · 463,751
#41
Дніпро Alerts 🚀 🚨
@dnipro_alerts · 809,443
#42
Труха⚡️Крим
@truexacrimeaua · 56,653
#43
Труха⚡️Одеса | Новини
@odesatruexa · 264,519
#44
Патрульна поліція Запорізької області
@patrolpolicezp · 3,614
#45
Акцент 🇺🇦 Оперативні новини Запоріжжя та України, все про війну
@akzentzp · 14,278
#46
ТСН новини / ТСН.ua
@tch_channel · 729,418
#47
Карта повітряних тривог ‼️ Вибухи ‼️ Ракети ‼️
@povitryanatrivogaaa · 728,432
#48
СІЧЕМО | pro ЗАПОРІЖЖЯ
@sichemo · 11,991
#49
Перший Запорізький 🇺🇦 Первый Запорожский
@onenews_zp · 12,946
#50
Труха⚡️Херсон
@truexakhersonua · 99,033
#51
Vgorode.ua | Запоріжжя
@zpvgorode · 6,803
#52
АТ "Запоріжжяобленерго"
@Zaporizhzhyaoblenergo_news · 94,455
#53
Радар⚡️Запоріжжя
@radar_zaporizhzhya · 88,544
#54
Николаевский Ванёк
@vanek_nikolaev · 2,571,456
#55
INSIDER UA | Україна | Новини
@insiderukr · 2,141,667
#56
Всевидящее ОКО (миллион подписчиков)
@oko_ua · 1,751
#57
УС: Україна, новини, політика, війна
@u_now · 1,401,643
#58
Реальна Війна | Україна | Новини
@voynareal · 1,541,547
#59
Типичный Шевчик - Запорожье | Запоріжжя 🇺🇦
@tpshev_zp · 30,201
#60
Батальйон Монако
@batalionmonako · 982
#61
monitor
@war_monitor · 956,914
#62
Говорять Снайпер ꑭ
@stanislav_osman · 287,183
#63
✙ 🔼Вертикаль
@vert2026 · 113,508
#64
Всевидящее ОКО 18 ✙
@oko18_ukr · 315,880
#65
Бавовна
@ukrbavovna · 800,178
#66
Анатолий Шарий
@asupersharij · 1,736,693
#67
STERNENKO
@ssternenko · 879,121
#68
НЕВЗОРОВ
@nevzorovtv · 1,001,073
#69
Запоріжжя. Відгуки про заклади
@zpplace · 18,280
#70
УНИАН - новости Украины | война с Россией | новини України | війна з Росією | УНІАН
@uniannet · 700,473
#71
Скринька Пандори
@pandoras_box_ua · 157,764
#72
NEXTA Live
@nexta_live · 765,001
#73
KokomE anime & k-pop events 💙 Запоріжжя
@kokomievents · 751
#74
Хуевая Одесса
@xydessa · 943,621
#75
Pravda Gerashchenko
@Pravda_Gerashchenko · 300,901
#76
Israel⚡️Труха
@israel_truexa · 77,373
#77
Дніпро Оперативний 🇺🇦| Війна
@dnepr_operativ · 312,948
#78
Zelenskiy / Official
@v_zelenskiy_official · 665,469
#79
БУТУСОВ ПЛЮС
@ButusovPlus · 347,624
#80
SHTOLL NEWS💋
@SHTOLLNEWS · 513,113
#81
Политика Страны
@stranaua · 334,918
#82

Read from Telegram’s recommendation API, most recently 10 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Типичное Запорожье
@typzp · 21,891
Telegram ranks this channel #1 of 81 here — alongside 80 others — read 21 September 2026
Запоріжжя ⚡️Новини
@zaporozhye_insider · 21,991
Telegram ranks this channel #1 of 87 here — alongside 86 others — read 20 September 2026
it_is_zp
@it_is_zp_tg · 44,928
Telegram ranks this channel #1 of 70 here — alongside 69 others — read 28 August 2026
🚨Запоріжжя | Оперативно | Аварійка
@avariyka_zaporizg · 49,925
Telegram ranks this channel #1 of 72 here — alongside 71 others — read 27 August 2026
Это Запорожье 🇺🇦 Новости
@eto_zp · 174,735
Telegram ranks this channel #1 of 84 here — alongside 83 others — read 12 August 2026
▵ Очі Всюди | Дніпро ▵
@eyes_everywhere_dnipro · 23,361
Telegram ranks this channel #2 of 77 here — alongside 76 others — read 4 October 2026
Славне Запоріжжя 🇺🇦 | Світло
@slavne_zaporizhia · 21,460
Telegram ranks this channel #2 of 81 here — alongside 80 others — read 20 September 2026
Хуевое Запорожье | Запоріжжя
@huevoe_zaporozhye · 24,623
Telegram ranks this channel #2 of 80 here — alongside 79 others — read 17 September 2026
ЗАПОРІЖЖЯ НОВИНИ | ЗАПОРОЖЬЕ НОВОСТИ 🇺🇦 | РАДАР | CВЕТ
@pro_zp_2023 · 26,004
Telegram ranks this channel #2 of 82 here — alongside 81 others — read 12 September 2026
Анатолій Куртєв
@kurtievofficial · 47,143
Telegram ranks this channel #2 of 80 here — alongside 79 others — read 26 August 2026
🇺🇦Запоріжжя Новини🇺🇦Запорожье Новости
@etozp · 73,643
Telegram ranks this channel #2 of 88 here — alongside 87 others — read 19 August 2026
ЗаБор Запоріжжя
@zaborzp · 109,648
Telegram ranks this channel #2 of 90 here — alongside 89 others — read 15 August 2026
Суспільне Запоріжжя
@suspilnezaporizhzhya · 33,005
Telegram ranks this channel #3 of 87 here — alongside 86 others — read 5 September 2026
ЗАПОРІЖЖЯ.ІНФО🍁
@info_zp · 192,549
Telegram ranks this channel #3 of 83 here — alongside 82 others — read 11 August 2026
5 РЕДАКЦІЯ | Новини Запоріжжя
@five_redakcia · 25,561
Telegram ranks this channel #4 of 83 here — alongside 82 others — read 15 September 2026
ЗАПОРІЗЬКА СІЧ
@zaporizka_sish · 26,387
Telegram ranks this channel #4 of 81 here — alongside 80 others — read 13 September 2026
🇺🇦 Іван Федоров | Рада Оборони Запорізької обл.
@ivan_fedorov_zp · 52,192
Telegram ranks this channel #4 of 91 here — alongside 90 others — read 22 August 2026
Оперативно → by HLEP
@operatyvnohlep · 173,958
Telegram ranks this channel #4 of 79 here — alongside 78 others — read 12 August 2026
∆✙🍒Гнила черешня🇺🇦✙∆
@gnilayachereha · 412,798
Telegram ranks this channel #4 of 84 here — alongside 83 others — read 10 August 2026
Михайло Семікін - Запорізька ОВА
@zoda_gov_ua · 33,512
Telegram ranks this channel #5 of 87 here — alongside 86 others — read 7 September 2026
БЕЗ БАЙДИ
@bezbaidy · 60,688
Telegram ranks this channel #5 of 86 here — alongside 85 others — read 22 August 2026
Где повестки Запорожье?
@agendaZaporozhye · 106,769
Telegram ranks this channel #7 of 77 here — alongside 76 others — read 22 August 2026
✙ ЗСУ HUB ✙
@ukraine_3CY_HUB · 36,321
Telegram ranks this channel #11 of 77 here — alongside 76 others — read 1 September 2026
Типичный Шевчик - Запорожье | Запоріжжя 🇺🇦
@tpshev_zp · 30,201
Telegram ranks this channel #13 of 72 here — alongside 71 others — read 8 September 2026

This channel appears in 53 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Труха⚡️Запоріжжя” (@truexazaporozie), 285,725 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/truexazaporozie.

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.