Telegram RegisterThe public register of Telegram
Telegram profile photo for ЗАПОРІЖЖЯ.НЕЗЛАМНЕ

Channel

ЗАПОРІЖЖЯ.НЕЗЛАМНЕ

@zapnovini

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

9,329subscribers

+336 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-1001811116300
TypeChannel
Username@zapnovini
DescriptionЗв'язок з нами @nezlamne_zaporizhzhia_bot
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 November 2026
Measurements held26
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/zapnovini

Topic

National news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 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 6 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
@zaporizka_sish/1150849 Aug 2026, 22:29 UTC@zapnovini/41072 · this entry9 Aug 2026, 22:30 UTC1.00under a minute
@zaporizka_sish/1252152 Nov 2026, 22:30 UTC@zapnovini/48093 · this entry2 Nov 2026, 22:31 UTC1.00under a minute
@zaporizka_sish/1252213 Nov 2026, 02:07 UTC@zapnovini/48097 · this entry3 Nov 2026, 02:09 UTC1.0072 seconds
@zaporizka_sish/1253174 Nov 2026, 05:35 UTC@zapnovini/48169 · this entry4 Nov 2026, 05:50 UTC1.0015 minutes
@zaporizka_sish/1253664 Nov 2026, 16:58 UTC@zapnovini/48202 · this entry4 Nov 2026, 18:53 UTC1.001.9 hours
@zaporizka_sish/1253824 Nov 2026, 20:18 UTC@zapnovini/48207 · this entry4 Nov 2026, 20:19 UTC1.0072 seconds
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
@zaporizka_sish16 (8/8 hand-verifiable sample passed)1.0072 seconds@zaporizka_sish (15–1)
@bezbaidy13 (8/8 hand-verifiable sample passed)0.9911 minutes@bezbaidy (9–4)
@etozp8 (7/8 hand-verifiable sample passed)0.966 minutes@etozp (5–3)
@zoda_gov_ua6 (6/6 hand-verifiable sample passed)0.9820 minutes@zoda_gov_ua (6–0)
@ivan_fedorov_zp5 (5/5 hand-verifiable sample passed)0.9822 minutes@ivan_fedorov_zp (5–0)
@info_zp5 (5/5 hand-verifiable sample passed)0.9814 minutesthis entry (5–0)

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. 40 of the 40 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 309 comparable posts for this entry, running 7 August 2026 to 15 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 16 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

8,9939,3429,167.57 August 2026 — 8,993 subscribers7 August 2026 — 8,993 subscribers8 August 2026 — 8,994 subscribers11 August 2026 — 9,030 subscribers14 August 2026 — 9,031 subscribers17 August 2026 — 9,060 subscribers21 August 2026 — 9,081 subscribers24 August 2026 — 9,091 subscribers27 August 2026 — 9,121 subscribers31 August 2026 — 9,125 subscribers3 September 2026 — 9,224 subscribers7 September 2026 — 9,227 subscribers12 September 2026 — 9,238 subscribers15 September 2026 — 9,216 subscribers5 October 2026 — 9,223 subscribers12 October 2026 — 9,252 subscribers15 October 2026 — 9,259 subscribers18 October 2026 — 9,293 subscribers21 October 2026 — 9,304 subscribers25 October 2026 — 9,305 subscribers28 October 2026 — 9,342 subscribers31 October 2026 — 9,329 subscribers3 November 2026 — 9,318 subscribers6 November 2026 — 9,334 subscribers10 November 2026 — 9,328 subscribers15 November 2026 — 9,329 subscribers9,3297 August 202615 November 2026
26 measurements spanning 100 days, net +336. 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 8,941–9,394 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
15 Nov 2026, 12:009,329+1
10 Nov 2026, 14:379,328-6
6 Nov 2026, 20:079,334+16
3 Nov 2026, 14:259,318-11
31 Oct 2026, 14:599,329-13
28 Oct 2026, 11:309,342+37
25 Oct 2026, 02:559,305+1
21 Oct 2026, 23:219,304+11
18 Oct 2026, 15:359,293+34
15 Oct 2026, 08:009,259+7
12 Oct 2026, 06:179,252+29
5 Oct 2026, 17:209,223+7
15 Sept 2026, 15:599,216-22
12 Sept 2026, 06:189,238+11
7 Sept 2026, 19:169,227+3
3 Sept 2026, 02:099,224+99
31 Aug 2026, 06:129,125+4
27 Aug 2026, 20:279,121+30
24 Aug 2026, 23:229,091+10
21 Aug 2026, 02:069,081first reading

Engagement

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

ERR · 30 days
16.9%
avg views ÷ 9,329 subscribers
Avg views / post
1,570
419 posts measured
Reaction rate
1.15%
reactions ÷ views · ER floor
Posts in window
419
of 869 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 415 of 419 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 15 November 2026
Posts held869 (7 August 2026 – 15 November 2026)
Views total659,272
Reactions total7,550
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 00:56 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
≈25,300
Videos
≈7,810
Links
≈547

Lifetime counters from Telegram’s own channel header, read 16 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
1h 39m
Average length
51s

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

16,575 reactions across 849 posts, in 15 distinct kinds. The most used accounts for 46.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤬7,75946.8%
😢3,51421.2%
❤1,89611.4%
👍1,0236.17%
🔥8395.06%
😱3702.23%
❤‍🔥3322.00%
🤔1821.10%
👎1781.07%
👏1390.839%
🤯1390.839%
😁1050.633%
💯640.386%
🍾190.115%
🎉160.097%

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 853 of the 869 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 16,575 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 869 most recent posts we hold, published 7 August 2026 to 15 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: 16 of 419 posts held from the last 30 days (3.82%) 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).

15 Nov 2026, 21:01 UTC998 views53 reactionsread 16 November 2026
Video

🙏Негайно виїджати з Кушугуму та Балабине закликають волонтери Влад Маховський та його колеги кажуть, що вже через тиждень сюди буде дуже важко потрапити, щоб допомогти цивільним.

😢47🤬4👍2

15 Nov 2026, 20:50 UTC≈1,020 views17 reactionsread 16 November 2026

❗️Загроза балістики

🤬17

15 Nov 2026, 20:16 UTC≈1,500 views27 reactionsread 16 November 2026

❗️Шевчик/околиці, КАБ

🤬26😱1

15 Nov 2026, 20:07 UTC≈1,600 views18 reactionsread 16 November 2026
Video

🔥 ББС «РОНІНИ» на Запорізькому напрямку Противник втрачає особовий склад, техніку та можливості для маневру. «У роботі наших екіпажів — ураження живої сили противника, квадроциклів, броньованого транспорту, логістичних маршрутів та ворожих укриттів. Кожна ціль — результат злагодженої роботи команди. Кожен виліт має свою мету», - зазначають «РОНІНИ».

🔥11👍4❤3

15 Nov 2026, 19:51 UTC≈1,650 views21 reactionsread 16 November 2026

❗️Військове містечко

🤬21

15 Nov 2026, 19:49 UTC≈1,640 views20 reactionsread 16 November 2026

❗️Новоолександрівка/Лежине

🤬20

15 Nov 2026, 19:46 UTC≈1,600 views21 reactionsread 16 November 2026

❗️У бік Комишувахи

🤬20❤1

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

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.

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.

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.

ЗАПОРІЗЬКА СІЧ
@zaporizka_sish · 26,322
Telegram ranks this channel #7 of 81 here — alongside 80 others — read 13 September 2026
Типичный Шевчик - Запорожье | Запоріжжя 🇺🇦
@tpshev_zp · 30,167
Telegram ranks this channel #9 of 72 here — alongside 71 others — read 8 September 2026
Типичное Запорожье
@typzp · 21,905
Telegram ranks this channel #13 of 81 here — alongside 80 others — read 21 September 2026
🚨Запоріжжя | Оперативно | Аварійка
@avariyka_zaporizg · 49,925
Telegram ranks this channel #13 of 72 here — alongside 71 others — read 27 August 2026
Анатолій Куртєв
@kurtievofficial · 47,143
Telegram ranks this channel #14 of 80 here — alongside 79 others — read 26 August 2026
ЗАПОРІЖЖЯ.ІНФО🍁
@info_zp · 191,930
Telegram ranks this channel #16 of 83 here — alongside 82 others — read 11 August 2026
АТ "Запоріжжяобленерго"
@Zaporizhzhyaoblenergo_news · 94,455
Telegram ranks this channel #18 of 83 here — alongside 82 others — read 17 August 2026
Запоріжжя ⚡️Новини
@zaporozhye_insider · 22,035
Telegram ranks this channel #20 of 87 here — alongside 86 others — read 20 September 2026
БЕЗ БАЙДИ
@bezbaidy · 60,642
Telegram ranks this channel #20 of 86 here — alongside 85 others — read 22 August 2026
Славне Запоріжжя 🇺🇦 | Світло
@slavne_zaporizhia · 21,460
Telegram ranks this channel #21 of 81 here — alongside 80 others — read 20 September 2026
Суспільне Запоріжжя
@suspilnezaporizhzhya · 33,005
Telegram ranks this channel #21 of 87 here — alongside 86 others — read 5 September 2026
5 РЕДАКЦІЯ | Новини Запоріжжя
@five_redakcia · 25,613
Telegram ranks this channel #22 of 83 here — alongside 82 others — read 15 September 2026
it_is_zp
@it_is_zp_tg · 44,928
Telegram ranks this channel #22 of 70 here — alongside 69 others — read 28 August 2026
▵ Очі Всюди | Дніпро ▵
@eyes_everywhere_dnipro · 23,361
Telegram ranks this channel #23 of 77 here — alongside 76 others — read 4 October 2026
Хуевое Запорожье | Запоріжжя
@huevoe_zaporozhye · 24,712
Telegram ranks this channel #23 of 80 here — alongside 79 others — read 17 September 2026
ЗАПОРІЖЖЯ НОВИНИ | ЗАПОРОЖЬЕ НОВОСТИ 🇺🇦 | РАДАР | CВЕТ
@pro_zp_2023 · 26,073
Telegram ranks this channel #25 of 82 here — alongside 81 others — read 12 September 2026
ЗаБор Запоріжжя
@zaborzp · 109,041
Telegram ranks this channel #36 of 90 here — alongside 89 others — read 15 August 2026
Труха⚡️Запоріжжя
@truexazaporozie · 284,647
Telegram ranks this channel #36 of 82 here — alongside 81 others — read 10 August 2026
БердянсЬк Сьогодні/Бердянск Сейчас
@brdVP · 18,500
Telegram ranks this channel #45 of 84 here — alongside 83 others — read 5 October 2026
БАЗА ПІБ | ФОТО ПОЛОНЕНИХ ✠ [РЕЗЕРВ]
@edynaUA · 30,771
Telegram ranks this channel #46 of 67 here — alongside 66 others — read 7 September 2026
ПОЛОНЕНІ | Пошук зниклих
@poloneni_ukr · 21,041
Telegram ranks this channel #48 of 59 here — alongside 58 others — read 24 September 2026
🇺🇦Запоріжжя Новини🇺🇦Запорожье Новости
@etozp · 73,585
Telegram ranks this channel #52 of 88 here — alongside 87 others — read 19 August 2026
Никополь/Марганец/Энергодар/Обстрелы
@other_nikopol · 21,473
Telegram ranks this channel #53 of 86 here — alongside 85 others — read 22 September 2026
✙ ЗСУ HUB ✙
@ukraine_3CY_HUB · 36,283
Telegram ranks this channel #53 of 77 here — alongside 76 others — read 1 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.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 15 November 2026 — this entry's latest reading, not the date you are reading this.

“ЗАПОРІЖЖЯ.НЕЗЛАМНЕ” (@zapnovini), 9,329 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/zapnovini.

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.