Telegram RegisterThe public register of Telegram
Telegram profile photo for Інсайдер ЗСУ 🔥

Channel

Інсайдер ЗСУ 🔥

@insider_zsy

Not marked by Telegram, checked 13 September 2026

On this record: Topic · Observations · Growth · Engagement · What this channel posts · View velocity · Reactions · Stars · Advertising · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Domains linked from posts · Cite this entry

18,099subscribers

-1,233,152 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001660226324
TypeChannel
Username@insider_zsy
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/insider_zsy

Topic

International 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 54% 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 5 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
@insider_zsy/46115 · this entry7 Sept 2026, 10:00 UTC@novini_ukrtg/882077 Sept 2026, 11:29 UTC0.9889 minutes
@novini_ukrtg/8850610 Sept 2026, 16:30 UTC@insider_zsy/46265 · this entry10 Sept 2026, 16:39 UTC0.989 minutes
@novini_ukrtg/898202 Oct 2026, 18:14 UTC@insider_zsy/47043 · this entry2 Oct 2026, 18:17 UTC0.983 minutes
@novini_ukrtg/9062715 Oct 2026, 16:35 UTC@insider_zsy/47551 · this entry15 Oct 2026, 16:59 UTC0.9725 minutes
@insider_zsy/46120 · this entry7 Sept 2026, 11:46 UTC@novini_ukrtg/882247 Sept 2026, 15:54 UTC0.974.1 hours
@insider_zsy/46531 · this entry18 Sept 2026, 14:00 UTC@novini_ukrtg/8892818 Sept 2026, 14:04 UTC0.965 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
@novini_ukrtg13 (8/8 hand-verifiable sample passed)0.9629 minutesthis entry (8–5)
@novynu_ukraina10 (8/8 hand-verifiable sample passed)0.9749 minutes@novynu_ukraina (7–3)
@DerhachiLIVE6 (6/6 hand-verifiable sample passed)0.9445 minutesthis entry (6–0)
@NovynaUKR5 (5/5 hand-verifiable sample passed)0.902.7 hoursthis entry (4–1)
@tgsn_ua5 (5/5 hand-verifiable sample passed)0.974.7 hours@tgsn_ua (3–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. 14 of the 14 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,348 comparable posts for this entry, running 5 August 2026 to 19 October 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).

Views per post sit far above this size band

148,000 average views per post against 18,393 subscribers — an engagement rate of 806.7%. Across the 1,578 registered channels in the same cohort — 10,011–31,608 subscribers, posting mainly in Ukrainian — the middle half sit between 11.6% and 32.2%, with a median of 19.6%.

What this was computed from
Window30 days (6 October 2026 – 5 November 2026)
Posts measured445 of 445 published in the window (0 exact, 445 rounded by Telegram)
Views totalled66,031,210
Mature posts only837.6% over 401 posts read at least 24h after publication
Subscribers18,393 measured 5 November 2026
Cohortb10000:ukr · 1,578 channels · p10 6.79% · p25 11.6% · p50 19.6% · p75 32.2% · p90 50.0%
Position in cohort100.000th percentile · 41.2× the cohort median
Uncertainty±0.157% of the figure, from Telegram’s rounding
Post languageUkrainian · 100.0% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

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

18,0931,283,980651,036.518,0996 August 202614 November 2026
65 measurements spanning 101 days, net -1,233,152. 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”.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
14 Nov 2026, 21:1018,099-5
11 Nov 2026, 22:0618,104+11
10 Nov 2026, 01:2118,093-50
8 Nov 2026, 14:0918,143-71
7 Nov 2026, 08:5418,214-77
6 Nov 2026, 06:0118,291-102
5 Nov 2026, 07:1118,393-85
4 Nov 2026, 04:4918,478-132
3 Nov 2026, 07:4418,610-129
2 Nov 2026, 06:2818,739-123
1 Nov 2026, 02:3918,862-22
31 Oct 2026, 05:1918,884-15
30 Oct 2026, 06:3618,899-15
29 Oct 2026, 04:3818,914-22
27 Oct 2026, 23:1618,936-10
27 Oct 2026, 01:1818,946-21
25 Oct 2026, 21:3918,967-14
24 Oct 2026, 21:2718,981-22
23 Oct 2026, 23:4619,003-13
23 Oct 2026, 02:4019,016first reading

Engagement

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

ERR · 30 days
546.8%
avg views ÷ 18,099 subscribers
Avg views / post
99,000
21 posts measured
Reaction rate
1.96%
reactions ÷ views · ER floor
Posts in window
21
of 2,048 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 19 October 2026
Posts held2,048 (5 August 2026 – 19 October 2026)
Views total2,078,150
Reactions total40,758
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken19 Oct 2026, 08:05 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
3h 20m
Average length
29s

Measured directly from 414 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

View velocity

How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.

8 most recently posted, with a view-velocity reading
PostReadingsLatest readingCurve24h reachHalf of last-observed views by
/4768519 Oct 2026, 07:57 UTC18 minutes – 8 minutes old9,950 views ~288 reactionsno checkpoint reading yetnot yet at 24hnot measurable yet
/4768419 Oct 2026, 07:51 UTC113 minutes – 13 minutes old16,800 views ~382 reactionsno checkpoint reading yetnot yet at 24hnot measurable yet
/4768319 Oct 2026, 07:28 UTC22 minutes – 36 minutes old29,800 views ~461 reactionsno checkpoint reading yetnot yet at 24h17 minutesprovisional — final view count still climbing
/4768219 Oct 2026, 07:16 UTC214 minutes – 48 minutes old38,100 views ~893 reactionsno checkpoint reading yetnot yet at 24h17 minutesprovisional — final view count still climbing
/4768119 Oct 2026, 06:52 UTC44 minutes – 73 minutes old49,800 views ~1,701 reactions60 minutes: 44,167 interp.still climbing at last readingnot yet at 24h25 minutesprovisional — final view count still climbing
/4768019 Oct 2026, 06:14 UTC511 minutes – 1.8 hours old67,400 views ~1,374 reactions60 minutes: 47,459 interp.still climbing at last readingnot yet at 24h37 minutesprovisional — final view count still climbing
/4767919 Oct 2026, 05:37 UTC613 minutes – 2.5 hours old79,600 views ~1,678 reactions60 minutes: 50,978 interp.still climbing at last readingnot yet at 24h40 minutesprovisional — final view count still climbing
/4767719 Oct 2026, 05:03 UTC717 minutes – 3.0 hours old90,100 views ~1,967 reactions60 minutes: 53,124 interp. → 3.0 hours: 90,100still climbing at last readingnot yet at 24h46 minutesprovisional — final view count still climbing

Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.

Reaction mix

2,359,174 reactions across 1,000 posts, in 14 distinct kinds. The most used accounts for 40.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤬949,96240.3%
🙏321,08513.6%
👍236,41210.0%
❤214,4349.09%
🔥190,8518.09%
😢146,6486.22%
🤡125,5555.32%
😁87,7303.72%
😱29,8031.26%
👎23,7841.01%
🤯16,1430.684%
👏10,8430.46%
🤔3,8970.165%
😍2,0270.086%

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 2,359,174 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 14 September 2026 to 19 October 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
120
across the posts below
Posts paid on
79
of 1,000 we hold a reading for · 8%
Most on one post
8
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @insider_zsy. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 14 September 2026 to 19 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Advertising

Ad load
0.1%
1 of 1,000 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
126,000
over 1 measured post
Median views · rest
155,000
over 999 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. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 14 September 2026 to 19 October 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: 18 of 21 posts held from the last 30 days (85.7%) 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).

19 Oct 2026, 07:57 UTC≈9,950 views288 reactionsread 19 October 2026
Video

🤬 Контактний зоопарк «Звірополіс» пошкоджено внаслідок удару по ТРЦ Cosmo Multimal Інсайдер ЗСУ

🤬202😢78❤7🙏1

19 Oct 2026, 07:51 UTC≈16,800 views382 reactionsread 19 October 2026
Photo

❗️Мішенню були енергетика та інфраструктура: за цю ніч пошкоджено понад 10 об’єктів, — Зеленський Президент також підтвердив, що уночі не було попередження про балістичну атаку. Інсайдер ЗСУ

🤬278😢59🙏32❤9😁4

19 Oct 2026, 07:28 UTC≈29,800 views461 reactionsread 19 October 2026

❗️Реактивний БПЛА повз Бровари: у Києві та області оголосили жовтий рівень небезпеки Інсайдер ЗСУ

🤬300🙏135❤12😢10😱3🔥1

19 Oct 2026, 07:16 UTC≈38,100 views893 reactionsread 19 October 2026

⚡️російський обстріл знищив дата-центр «Датагруп» у Києві, відновити його неможливо "Датагруп" забезпечувала інтернет, зв'язок, дата-центри та хмарні сервіси для бізнесу, державних установ та приватних клієнтів. Інсайдер ЗСУ

🤬660😢118😱42🙏39❤24🔥10

19 Oct 2026, 06:52 UTC≈49,800 views1,701 reactionsread 19 October 2026

❗️США готують чергове послаблення санкцій проти РФ: йдеться про зняття обмежень із танкерів, газу, окремих компаній та осіб, крім того, шукають можливість перебрати контроль над замороженими активами Інсайдер ЗСУ

🤬1,560🙏47😢32❤27🔥18😱17

19 Oct 2026, 06:14 UTC≈67,400 views1,374 reactionsread 19 October 2026
Video

⚡️Руснявий дрон впав поруч з АТБ біля Львова: до цього він годину кружляв навколо міста Інсайдер ЗСУ

🤬1,020😢185🙏119❤28😱15🔥7

19 Oct 2026, 05:37 UTC≈79,600 views1,678 reactionsread 19 October 2026
Video

❗️Сильні руйнування у ТЦ "Космополіт" у Києві після обстрілу Інсайдер ЗСУ

🤬1,160😢300🙏95😱66❤47🔥10

19 Oct 2026, 05:03 UTC≈90,100 views1,967 reactionsread 19 October 2026
Video

⚡️Станція метро «Чернігівська» після російської атаки Під час нічної атаки у Києві загинула людина, ще 8 постраждали. Інсайдер ЗСУ

🤬1,360😢416🙏132❤46🔥8👏5

19 Oct 2026, 04:47 UTC≈94,500 views1,592 reactionsread 19 October 2026
Photo

⚡️Серйозно пошкоджено ТЦ «Cosmo Multimall» у Солом’янському районі Києва Інсайдер ЗСУ

🤬1,200🙏174😢145❤47😱15👏11

19 Oct 2026, 04:18 UTC≈99,100 views2,721 reactionsread 19 October 2026

❗️США знову не передали інформацію про пуски балістики, яка летіла вночі по Києву, — «Радіо Свобода» Інсайдер ЗСУ

🤬2,420🙏140😢87❤39😁19😱16

19 Oct 2026, 03:37 UTC≈110,000 views1,684 reactionsread 19 October 2026
Photo

❗️Крилаті ракети на Київ/область: оголошено «червону» тривогу Ворог пустив 5 ракет «Іскандер-К»: вибухи пролунали в Ірпені та передмісті. Інсайдер ЗСУ

🙏937🤬611❤68😢53👏9👍6

19 Oct 2026, 00:18 UTC≈121,000 views2,283 reactionsread 19 October 2026
Video

⚡️Пошкоджено станцію метро «Чернігівська» внаслідок російської атаки, — Кличко. Інсайдер ЗСУ

🤬1,630🙏374😢193❤70🔥11👍5

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

@insider_zsy edited 340 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
8 August 2026
Most recent edit
19 October 2026

Posts recorded as deleted after publishing

We recorded 136 posts on @insider_zsy 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
7 August 2026
Most recent seen missing
18 October 2026
Median time before seen missing
5.6 hours
Seen missing in the last 30 days
1

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 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Domains linked from posts

3 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.

www.facebook.comregistrable domain: facebook.com2 posts · 6 August 2026 – 7 August 2026 · example post
24tv.ua1 post · 6 August 2026 – 6 August 2026 · example post
www.youtube.comregistrable domain: youtube.com1 post · 5 August 2026 – 5 August 2026 · example post

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

“Інсайдер ЗСУ 🔥” (@insider_zsy), 18,099 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/insider_zsy.

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.