Telegram RegisterThe public register of Telegram
Telegram profile photo for Суспільне Запоріжжя

Channel

Суспільне Запоріжжя

@suspilnezaporizhzhya

Verified by Telegram

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cross-platform identity · Referenced elsewhere · Cite this entry

33,005subscribers

+137 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-1001449647007
TypeChannel
Username@suspilnezaporizhzhya
DescriptionУсі новини регіону в одному місці. Офіційний канал Суспільного. Надсилайте свої фото, відео та пропозиції в наш бот @zaporizhzhyasuspilnebot
Created23 April 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live16 November 2026
Measurements held66
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/suspilnezaporizhzhya

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 97% 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 12 other registered channels. This entry also forms a group of 2 channels linked by matching posts. 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
@suspilnezaporizhzhya/60423 · this entry20 Aug 2026, 16:49 UTC@trukha_vua0/4406920 Aug 2026, 16:49 UTC1.00under a minute
@suspilnezaporizhzhya/60518 · this entry22 Aug 2026, 14:46 UTC@trukha_vua0/4416422 Aug 2026, 14:46 UTC1.00under a minute
@suspilnezaporizhzhya/60629 · this entry24 Aug 2026, 17:41 UTC@trukha_vua0/4427324 Aug 2026, 17:41 UTC1.00under a minute
@suspilnezaporizhzhya/60705 · this entry25 Aug 2026, 19:05 UTC@trukha_vua0/4433225 Aug 2026, 19:05 UTC1.00under a minute
@suspilnezaporizhzhya/60898 · this entry28 Aug 2026, 16:01 UTC@trukha_vua0/4452628 Aug 2026, 16:01 UTC1.00under a minute
@suspilnezaporizhzhya/64399 · this entry5 Nov 2026, 07:03 UTC@trukha_vua0/479085 Nov 2026, 07:03 UTC1.00under a minute
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
@trukha_vua0199 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (188–11)
@suspilnenews74 (8/8 hand-verifiable sample passed)1.007 minutes@suspilnenews (41–33)
@suspilnecherkasy18 (8/8 hand-verifiable sample passed)1.009 minutes@suspilnecherkasy (10–8)
@suspilnesumy10 (8/8 hand-verifiable sample passed)1.0013 minutes@suspilnesumy (7–3)
@suspilne_lutsk10 (8/8 hand-verifiable sample passed)1.0018 minutesthis entry (10–0)
@suspilnekropyvnytskyi14 (8/8 hand-verifiable sample passed)0.997 minutesthis entry (9–5)
@suspilnemykolaiv10 (8/8 hand-verifiable sample passed)1.0014 minutesthis entry (9–1)
@zp_informue5 (5/5 hand-verifiable sample passed)0.9556 minutesthis entry (5–0)
@trukha_vUA5 (5/5 hand-verifiable sample passed)1.0052 minutesthis entry (5–0)
@suspilneodesa6 (6/6 hand-verifiable sample passed)1.0026 minutesthis entry (4–2)
@suspilneivano_frankivsk12 (8/8 hand-verifiable sample passed)1.003 minutesthis entry (8–4)
@suspilne_vinnytsia6 (6/6 hand-verifiable sample passed)1.0014 minutesthis entry (4–2)

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. 46 of the 46 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,429 comparable posts for this entry, running 6 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @suspilnezaporizhzhya — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

32,58233,05332,817.533,0056 August 202616 November 2026
66 measurements spanning 102 days, net +137. 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 32,511–33,124 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
16 Nov 2026, 00:5933,005+22
12 Nov 2026, 13:1632,983-14
10 Nov 2026, 08:0132,997-23
8 Nov 2026, 18:4933,020-11
7 Nov 2026, 11:4033,031-13
6 Nov 2026, 13:4933,044-9
5 Nov 2026, 14:1033,053+2
4 Nov 2026, 12:4733,051+64
3 Nov 2026, 10:1432,987+89
2 Nov 2026, 07:4032,898+17
1 Nov 2026, 04:5132,881+41
31 Oct 2026, 05:2032,840+25
30 Oct 2026, 06:3032,815+64
29 Oct 2026, 06:2132,751+19
28 Oct 2026, 04:3532,732+25
27 Oct 2026, 06:4532,707+19
26 Oct 2026, 07:5832,688+46
25 Oct 2026, 04:2732,642+60
24 Oct 2026, 03:2832,582-7
23 Oct 2026, 00:2932,589first reading

Engagement

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

ERR · 30 days
18.8%
avg views ÷ 33,005 subscribers
Avg views / post
6,220
680 posts measured
Reaction rate
1.43%
reactions ÷ views · ER floor
Posts in window
680
of 2,483 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 18 November 2026
Posts held2,483 (6 August 2026 – 18 November 2026)
Views total4,227,572
Reactions total60,317
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 08:13 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
≈21,700
Videos
≈1,960
Links
≈27,100

Lifetime counters from Telegram’s own channel header, read 18 November 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
21m 52s
Average length
31s

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

78,430 reactions across 1,000 posts, in 58 distinct kinds. The most used accounts for 29.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏22,78029.0%
🤬18,20823.2%
😢15,90120.3%
❤7,4399.48%
👍2,7083.45%
😭2,7043.45%
💔2,4933.18%
🔥1,6832.15%
🤡9331.19%
🤮4780.609%
😱4320.551%
🤔3610.46%
😡3350.427%
🤯2840.362%
😁2280.291%
💩2200.281%
👎2150.274%
👏1920.245%
🖕1750.223%
💯1220.156%
38 further kinds5390.687%

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 1,000 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 78,430 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 9 October 2026 to 18 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.

Recent posts

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

18 Nov 2026, 07:54 UTC≈1,060 views29 reactionsread 18 November 2026

Загинула жінка, а чоловік дістав поранення в Кушугумі внаслідок атаки російського FPV-дрона, повідомив т.в.о. очільника ЗОВА Михайло Семікін. Безпілотник влучив у відкриту ділянку місцевості. Вибуховою хвилею та уламками пошкоджено житлові будинки.

😢25🤬4

18 Nov 2026, 07:51 UTC≈1,270 views18 reactionsread 18 November 2026

48-річного чоловіка та трирічну дитину врятували під час пожежі в Запоріжжі, повідомили в ДСНС області. Це сталося вчора у квартирі п'ятиповерхового будинку. Там горіли домашні речі та меблі, вогонь охопив 6 кв. м. Наразі з'ясовують причину займання, триває розслідування.

🙏12😱5❤1

18 Nov 2026, 07:15 UTC≈2,420 views66 reactionsread 18 November 2026

Поранені внаслідок учорашніх обстрілів Запоріжжя перебувають на стаціонарному лікуванні. Із них 9 — у тяжкому стані, повідомила секретарка міськради Регіна Харченко.

😢45🙏14🤬6❤1

18 Nov 2026, 06:52 UTC≈2,960 views60 reactionsread 18 November 2026

КАБи на Запорізьку область, повідомили у Повітряних Силах ЗСУ.

🙏37🤬20😡3

18 Nov 2026, 06:33 UTC≈3,390 views57 reactionsread 18 November 2026

Чотири рази атакували військові РФ позиції Сил оборони України на Гуляйпільському напрямку минулої доби, 17 листопада, повідомили в Генштабі ЗСУ. Бойові зіткнення були в напрямках Барвінівки, Єгорівки, Косівцевого та Герасимівки.

🙏40🤬14🤯2❤1

18 Nov 2026, 05:14 UTC≈4,470 views69 reactionsread 18 November 2026
Photo

692 удари по 55 населених пунктах Запорізької області завдали російські військові упродовж доби 17 листопада, повідомив співголова Ради оборони регіону Іван Федоров. Дві людини загинули, ще 49 дістали поранення внаслідок атак на Запоріжжя та Запорізький район.

😢41🤬16🙏8❤4

18 Nov 2026, 04:05 UTC≈5,200 views37 reactionsread 18 November 2026

❗️Оновили графік погодинних відключень світла для Запоріжжя та області на сьогодні, повідомили в обленерго. Зміни дивіться тут.

❤21🤬5👍3🤡2😁2🙏2👏1🤯1

17 Nov 2026, 21:53 UTC≈6,430 views35 reactionsread 18 November 2026

❗️Оновили графік погодинних відключень світла для Запоріжжя та області на завтра, 18 листопада, повідомили в обленерго. Так, збільшили час знеструмлень для підчерг 2.1 та 2.2. Оновлений графік — дивіться тут.

❤21🤬7🤔4🙏2🤡1

17 Nov 2026, 20:52 UTC≈6,700 views90 reactionsread 18 November 2026

390,7 тисяч абонентів заживили після ранкових знеструмлень внаслідок атак РФ по енергосистемі Запорізької області, повідомили і обленерго. Водночас, залишаються локальні відключення світла внаслідок повторних ударів РФ або технологічних порушень — енергетики продовжують працювати над відновленням електропостачання.

❤61👍23🤬3🙏2🫡1

17 Nov 2026, 19:55 UTC≈6,850 views48 reactionsread 18 November 2026

💡Завтра, 18 листопада, у Запоріжжі та області діятимуть графіки погодинних відключень світла. Знеструмлення передбачені для 12 підчерг упродовж доби. Перевірити свою чергу та графік — тут.

🤬31❤9🙏6🍾2

17 Nov 2026, 18:35 UTC≈7,210 views108 reactionsread 18 November 2026

Нині все ще тривають ремонтні роботи з відновлення електропостачання після ранкового масового знеструмлення в Запорізькій області, повідомили в обленерго.

🙏90👍8❤6🤬4

17 Nov 2026, 18:32 UTC≈7,190 views119 reactionsread 18 November 2026
Photo

Обов'язкову евакуацію дітей з батьками оголосили у селищі Балабине на Запоріжжі, повідомили в Кушугумській громаді. Евакуація відбувається у супроводі поліції та благодійників. Родини мають евакуювати до транзитного центру в Запоріжжі, де буде надана необхідна допомога.

😢44👍39🙏19❤14🤣1🤬1🥱1

Showing the 12 most recent of 2,483 posts we hold for @suspilnezaporizhzhya. 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

@suspilnezaporizhzhya edited 7 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
16 August 2026
Most recent edit
18 November 2026

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

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.

ЗАПОРІЖЖЯ.ІНФО🍁
@info_zp · 192,549
#1
Это Запорожье 🇺🇦 Новости
@eto_zp · 174,735
#2
Труха⚡️Запоріжжя
@truexazaporozie · 285,725
#3
Лачен пише
@lachentyt · 1,576,100
#4
Оперативно → by HLEP
@operatyvnohlep · 173,958
#5
🇺🇦 Іван Федоров | Рада Оборони Запорізької обл.
@ivan_fedorov_zp · 52,192
#6
ЗаБор Запоріжжя
@zaborzp · 109,648
#7
СУСПІЛЬНЕ НОВИНИ
@suspilnenews · 262,451
#8
Повітряні Сили ЗС України / Air Force of the Armed Forces of Ukraine
@kpszsu · 938,170
#9
Труха⚡️Україна
@truexanewsua · 3,165,345
#10
Михайло Семікін - Запорізька ОВА
@zoda_gov_ua · 33,512
#11
🇺🇦Запоріжжя Новини🇺🇦Запорожье Новости
@etozp · 73,643
#12
✙DeepState✙🇺🇦
@deepstateua · 750,207
#13
ДСНС Запоріжжя
@gu_dsns_zp · 3,279
#14
5 РЕДАКЦІЯ | Новини Запоріжжя
@five_redakcia · 25,561
#15
ЗАПОРІЗЬКА СІЧ
@zaporizka_sish · 26,387
#16
СІЧЕМО | pro ЗАПОРІЖЖЯ
@sichemo · 11,991
#17
Патрульна поліція Запорізької області
@patrolpolicezp · 3,970
#18
Регіна Харченко. Секретар Запорізької міської ради
@regina_harchenko · 11,268
#19
Суспільне Дніпро
@suspilnednipro · 23,652
#20
ЗАПОРІЖЖЯ.НЕЗЛАМНЕ
@zapnovini · 9,329
#21
Бабель
@babel · 77,898
#22
hromadske
@hromadske_ua · 103,744
#23
ЦАПЛІЄНКО_UKRAINE FIGHTS
@Tsaplienko · 319,669
#24
Українська правда
@ukrpravda_news · 204,669
#25
ТСН новини / ТСН.ua
@tch_channel · 729,418
#26
Реальна Війна | Україна | Новини
@voynareal · 1,541,547
#27
Суспільне Харків
@suspilne_kharkiv · 110,659
#28
Запорізька міська рада 🇺🇦
@zaporizhzhiacitycouncil · 3,667
#29
Ukraine NOW
@UkraineNow · 403,875
#30
БЕЗ БАЙДИ
@bezbaidy · 60,688
#31
Анатолій Куртєв
@kurtievofficial · 47,143
#32
Запорізька обласна прокуратура
@zap_gp_gov_ua · 1,066
#33
Радіо Свобода
@svoboda_radio · 103,317
#34
Український Наступ | #УкрТг ∆
@ukrnastup · 132,638
#35
Новини поліції Запорізької області
@police_zp_news · 3,651
#36
Перший Запорізький 🇺🇦 Первый Запорожский
@onenews_zp · 12,946
#37
Суспільне Херсон
@suspilnekherson · 36,641
#38
ЗАПОРІЖЖЯ НОВИНИ | ЗАПОРОЖЬЕ НОВОСТИ 🇺🇦 | РАДАР | CВЕТ
@pro_zp_2023 · 26,004
#39
ДСНС України
@dsns_telegram · 75,556
#40
Акцент 🇺🇦 Оперативні новини Запоріжжя та України, все про війну
@akzentzp · 14,278
#41
🇺🇦Херcонська ОДА (ОВА)
@khersonskaODA · 20,134
#42
Суспільне Одеса
@suspilneodesa · 46,665
#43
Головні новини Запоріжжя - 061.ua
@ZaporozhyeNews · 5,262
#44
Типичное Запорожье
@typzp · 21,891
#45
Запоріжжя | Новини 🇺🇦
@zprzcitynews · 2,489
#46
Бердянська громада
@berdmisk · 1,734
#47
РБК-Україна
@RBC_ua_news · 74,785
#48
INFORM.ZP 🇺🇦 Новини Запоріжжя | Новости Запорожье
@informzp1 · 10,140
#49
Суспільне Донбас
@suspilnedonbas · 8,916
#50
Телебачення Торонто
@torontotv · 111,865
#51
ГОНЧАРЕНКО
@oleksiihoncharenko · 208,987
#52
Служба безпеки України
@SBUkr · 293,247
#53
Суспільне Крим
@suspilnecrimea · 2,031
#54
КМДА – офіційний канал
@KyivCityOfficial · 403,658
#55
Суспільне Суми
@suspilnesumy · 140,149
#56
Суспільне Київ
@suspilne_kyiv · 8,485
#57
NV | nv.ua | Радіо NV | Новини України | Аналітика | Відео | НВ |
@nvua_official · 49,144
#58
Олександр Ганжа / Дніпропетровська ОДА (ОВА)
@dnipropetrovskaODA · 47,162
#59
КМВА (Київська міська військова адміністрація)
@VA_Kyiv · 54,511
#60
Vitalii KIM | Official
@VitaliiKimOfficial · 250,936
#61
МВС України
@mvs_ukraine · 65,465
#62
∆✙🍒Гнила черешня🇺🇦✙∆
@gnilayachereha · 412,423
#63
STERNENKO
@ssternenko · 879,121
#64
monitor
@war_monitor · 956,914
#65
Радар⚡️Запоріжжя
@radar_zaporizhzhya · 88,544
#66
INSIDER UA | Україна | Новини
@insiderukr · 2,141,667
#67
Всевидящее ОКО (миллион подписчиков)
@oko_ua · 1,751
#68
УС: Україна, новини, політика, війна
@u_now · 1,401,643
#69
Бавовна
@ukrbavovna · 800,178
#70
Новинач
@novinach · 142,158
#71
Скринька Пандори
@pandoras_box_ua · 157,764
#72
Zelenskiy / Official
@v_zelenskiy_official · 665,292
#73
✙ 🔼Вертикаль
@vert2026 · 113,508
#74
Україна Online: Новини | Політика
@UaOnlii · 1,534,047
#75
Крымский ветер
@Crimeanwind · 227,834
#76
ХДніпро 🇺🇦
@hyevuy_dnepr · 520,852
#77
✙ Перша приватна мемарня
@privatnamemarnya · 115,209
#78
ҐРУНТ
@gruntmedia · 147,873
#79
Андрющенко Time
@andriyshTime · 29,875
#80
Pravda Gerashchenko
@Pravda_Gerashchenko · 300,901
#81
Військово-Морські Сили ЗС України | UA Navy
@ukrainian_navy · 12,411
#82
Андрій Єрмак 🇺🇦
@ermaka2022 · 79,747
#83
Головне управління розвідки МО України
@DIUkraine · 220,800
#84
Регіоналіті
@regionality · 100,624
#85
YIGAL LEVIN
@yigal_levin · 218,978
#86
✙🔥Прожарка 🇺🇦✙
@pprogarka · 13,454
#87

Read from Telegram’s recommendation API, most recently 5 September 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.

Анатолій Куртєв
@kurtievofficial · 47,143
Telegram ranks this channel #12 of 80 here — alongside 79 others — read 26 August 2026
АТ "Запоріжжяобленерго"
@Zaporizhzhyaoblenergo_news · 94,455
Telegram ranks this channel #12 of 83 here — alongside 82 others — read 17 August 2026
5 РЕДАКЦІЯ | Новини Запоріжжя
@five_redakcia · 25,561
Telegram ranks this channel #13 of 83 here — alongside 82 others — read 15 September 2026
Михайло Семікін - Запорізька ОВА
@zoda_gov_ua · 33,512
Telegram ranks this channel #13 of 87 here — alongside 86 others — read 7 September 2026
Типичное Запорожье
@typzp · 21,891
Telegram ranks this channel #17 of 81 here — alongside 80 others — read 21 September 2026
ЗАПОРІЗЬКА СІЧ
@zaporizka_sish · 26,387
Telegram ranks this channel #19 of 81 here — alongside 80 others — read 13 September 2026
ЗаБор Запоріжжя
@zaborzp · 109,648
Telegram ranks this channel #21 of 90 here — alongside 89 others — read 15 August 2026
ЗАПОРІЖЖЯ НОВИНИ | ЗАПОРОЖЬЕ НОВОСТИ 🇺🇦 | РАДАР | CВЕТ
@pro_zp_2023 · 26,004
Telegram ranks this channel #22 of 82 here — alongside 81 others — read 12 September 2026
🇺🇦Запоріжжя Новини🇺🇦Запорожье Новости
@etozp · 73,643
Telegram ranks this channel #23 of 88 here — alongside 87 others — read 19 August 2026
Славне Запоріжжя 🇺🇦 | Світло
@slavne_zaporizhia · 21,460
Telegram ranks this channel #27 of 81 here — alongside 80 others — read 20 September 2026
Запоріжжя ⚡️Новини
@zaporozhye_insider · 21,991
Telegram ranks this channel #30 of 87 here — alongside 86 others — read 20 September 2026
ЗАПОРІЖЖЯ.ІНФО🍁
@info_zp · 192,549
Telegram ranks this channel #30 of 83 here — alongside 82 others — read 11 August 2026
Оперативно → by HLEP
@operatyvnohlep · 173,958
Telegram ranks this channel #32 of 79 here — alongside 78 others — read 12 August 2026
it_is_zp
@it_is_zp_tg · 44,928
Telegram ranks this channel #33 of 70 here — alongside 69 others — read 28 August 2026
Это Запорожье 🇺🇦 Новости
@eto_zp · 174,735
Telegram ranks this channel #33 of 84 here — alongside 83 others — read 12 August 2026
Труха⚡️Запоріжжя
@truexazaporozie · 285,725
Telegram ranks this channel #33 of 82 here — alongside 81 others — read 10 August 2026
Типичный Шевчик - Запорожье | Запоріжжя 🇺🇦
@tpshev_zp · 30,201
Telegram ranks this channel #34 of 72 here — alongside 71 others — read 8 September 2026
🚨Запоріжжя | Оперативно | Аварійка
@avariyka_zaporizg · 49,925
Telegram ranks this channel #35 of 72 here — alongside 71 others — read 27 August 2026
Суспільне Дніпро
@suspilnednipro · 23,652
Telegram ranks this channel #36 of 90 here — alongside 89 others — read 20 September 2026
🇺🇦 Іван Федоров | Рада Оборони Запорізької обл.
@ivan_fedorov_zp · 52,192
Telegram ranks this channel #36 of 91 here — alongside 90 others — read 22 August 2026
БЕЗ БАЙДИ
@bezbaidy · 60,688
Telegram ranks this channel #38 of 86 here — alongside 85 others — read 22 August 2026
Хуевое Запорожье | Запоріжжя
@huevoe_zaporozhye · 24,623
Telegram ranks this channel #39 of 80 here — alongside 79 others — read 17 September 2026
БердянсЬк Сьогодні/Бердянск Сейчас
@brdVP · 18,472
Telegram ranks this channel #46 of 84 here — alongside 83 others — read 5 October 2026
Суспільне Івано-Франківськ
@suspilneivano_frankivsk · 23,325
Telegram ranks this channel #48 of 91 here — alongside 90 others — read 21 September 2026

This channel appears in 27 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.

Cross-platform identity — Wikidata

A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.

Q4186989 on Wikidata, read 15 November 2026
LabelSuspilne Zaporizhzhia
YouTubeUCZSashx8dRHivfiJuim_OHg
Official sitehttp://suspilne.media/zaporizhzhia

Referenced elsewhere

This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.

Wikipedia

One Wikipedia article names this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.

Славне (Запорізький район) (uk.wikipedia.org)
“…дронами, внаслідок чого загинув 59-річний чоловік{{Cite web |url=https://t.me/suspilnezaporizhzhya/54761 |title=Суспільне Запоріжжя |website=Telegram…”
read 1 November 2026

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

“Суспільне Запоріжжя” (@suspilnezaporizhzhya), 33,005 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/suspilnezaporizhzhya.

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.