Telegram RegisterThe public register of Telegram
Telegram profile photo for UA HiMARS 18+🫡

Channel

UA HiMARS 18+🫡

@war_ua_22

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

19,468subscribers

+750 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001779652047
TypeChannel
Username@war_ua_22
Description🇺🇦Канал новин України і не тільки. 📌Посилання на канал: https://t.me/war_ua_22 📝Зворотній зв'язок @BilkoUA_bot На біржі: adsell.io/r/ToiBHC
Created27 February 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live11 November 2026
Measurements held61
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/war_ua_22

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 64% 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 8 other registered channels. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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
@huevuy_nmsk/10349813 Aug 2026, 13:44 UTC@war_ua_22/190268 · this entry13 Aug 2026, 13:44 UTC1.00under a minute
@huevuy_nmsk/10366817 Aug 2026, 13:32 UTC@war_ua_22/190366 · this entry17 Aug 2026, 14:33 UTC1.0061 minutes
@huevuy_nmsk/10367817 Aug 2026, 15:30 UTC@war_ua_22/190367 · this entry17 Aug 2026, 15:37 UTC1.007 minutes
@huevuy_nmsk/10371918 Aug 2026, 15:32 UTC@war_ua_22/190405 · this entry18 Aug 2026, 15:50 UTC1.0017 minutes
@huevuy_nmsk/10414627 Aug 2026, 04:57 UTC@war_ua_22/190675 · this entry27 Aug 2026, 05:44 UTC1.0047 minutes
@huevuy_nmsk/10425828 Aug 2026, 15:30 UTC@war_ua_22/190739 · this entry28 Aug 2026, 17:29 UTC1.002.0 hours
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
@huevuy_nmsk39 (8/8 hand-verifiable sample passed)1.0023 minutes@huevuy_nmsk (30–9)
@sinelnikovoraion14 (8/8 hand-verifiable sample passed)1.0023 minutes@sinelnikovoraion (12–2)
@dnipropetrovskaODA58 (8/8 hand-verifiable sample passed)1.0023 minutes@dnipropetrovskaODA (58–0)
@oborona_kr8 (8/8 hand-verifiable sample passed)1.0026 minutes@oborona_kr (5–3)
@prikhist28 (8/8 hand-verifiable sample passed)0.9931 minutes@prikhist (22–6)
@kudy_letyt7 (7/7 hand-verifiable sample passed)0.9972 seconds@kudy_letyt (7–0)
@ptrkmedia7 (7/7 hand-verifiable sample passed)1.0032 minutesthis entry (4–3)
@pavlogradmrada7 (7/7 hand-verifiable sample passed)1.0031 minutes@pavlogradmrada (5–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. 34 of the 34 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 235 comparable posts for this entry, running 6 August 2026 to 12 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 3 channels, the one whose matching posts we hold earliest is @war_ua_22 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual, last confirmed 13 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 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. 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

18,71819,46819,0937 August 202611 November 2026
61 measurements spanning 96 days, net +750. 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 18,606–19,581 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 61
Measured (UTC)SubscribersChange
11 Nov 2026, 16:4619,468+6
9 Nov 2026, 19:5919,462+15
8 Nov 2026, 10:5619,447-9
7 Nov 2026, 08:1019,456+24
6 Nov 2026, 09:2419,432+15
5 Nov 2026, 11:3019,417+26
4 Nov 2026, 12:0819,391+50
3 Nov 2026, 11:0919,341+17
2 Nov 2026, 12:2819,324+18
1 Nov 2026, 14:0819,306-8
31 Oct 2026, 17:0819,314-13
30 Oct 2026, 17:1119,327-21
29 Oct 2026, 19:5119,348-18
28 Oct 2026, 22:0619,366+9
27 Oct 2026, 23:0719,357-12
27 Oct 2026, 00:1619,369-10
26 Oct 2026, 02:0719,379-11
23 Oct 2026, 21:1719,390+30
22 Oct 2026, 21:4019,360-11
21 Oct 2026, 18:1719,371first reading

Engagement

1,160 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 77 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
13.8%
avg views ÷ 19,468 subscribers
Avg views / post
2,690
404 posts measured
Reaction rate
1.53%
reactions ÷ views · ER floor
Posts in window
404
of 1,160 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 13 November 2026
Posts held1,160 (6 August 2026 – 13 November 2026)
Views total1,087,185
Reactions total16,632
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Nov 2026, 16:25 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
≈56,700
Videos
≈17,000
Links
≈6,510

Lifetime counters from Telegram’s own channel header, read 13 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
14m 49s
Average length
31s

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

58,894 reactions across 999 posts, in 20 distinct kinds. The most used accounts for 47.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏27,71147.1%
🤬15,74826.7%
😢3,2035.44%
❤2,3283.95%
👍1,9023.23%
custom 54136324592815396121,8683.17%
custom 54609920801070200361,4902.53%
🔥1,1992.04%
🤣8461.44%
🖕7341.25%
💯6981.19%
🤔4070.691%
💔2790.474%
👀2220.377%
🫡1110.188%
custom 5359348316087814702420.071%
😎290.049%
👎270.046%
custom 5936175850008349890260.044%
❤‍🔥240.041%

Custom emoji. 4 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

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 58,894 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 11 August 2026 to 13 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.

Telegram Stars

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

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @war_ua_22. 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 11 August 2026 to 13 November 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.

Recent posts

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

13 Nov 2026, 16:07 UTC382 views8 reactionsread 13 November 2026

🟢 Дніпровський район — відбій повітряної тривоги

🙏5👍3

13 Nov 2026, 15:53 UTC876 views21 reactionsread 13 November 2026

🔴 Дніпровський район — повітряна тривога, червоний рівень

🤬12🙏9

13 Nov 2026, 14:27 UTC≈1,490 views25 reactionsread 13 November 2026

🟢 Дніпровський район — відбій повітряної тривоги

🙏20👍5

13 Nov 2026, 14:21 UTC≈1,610 views20 reactionsread 13 November 2026

🔴 Дніпровський район — повітряна тривога, червоний рівень

🤬13🙏7

13 Nov 2026, 13:26 UTC≈1,900 views20 reactionsread 13 November 2026

🟢 Дніпровський район — відбій повітряної тривоги

🙏16👍4

13 Nov 2026, 13:13 UTC≈2,030 views19 reactionsread 13 November 2026

🔴 Дніпровський район — повітряна тривога, червоний рівень

🙏14🤬5

13 Nov 2026, 12:21 UTC≈2,160 views18 reactionsread 13 November 2026

🟢 Дніпровський район — відбій повітряної тривоги

🙏12👍6

13 Nov 2026, 12:00 UTC≈2,280 views21 reactionsread 13 November 2026

🔴 Дніпровський район — повітряна тривога, червоний рівень

🙏15🤬5❤1

13 Nov 2026, 11:38 UTC≈2,340 views23 reactionsread 13 November 2026

🟢 Дніпровський район — відбій повітряної тривоги

🙏21👍2

13 Nov 2026, 10:22 UTC≈2,600 views33 reactionsread 13 November 2026

🔴 Дніпровський район — повітряна тривога, червоний рівень

🙏20🤬13

13 Nov 2026, 07:53 UTC≈2,810 views33 reactionsread 13 November 2026

🟢 Дніпровський район — відбій повітряної тривоги

🙏31👍2

13 Nov 2026, 06:45 UTC≈3,000 views42 reactionsread 13 November 2026

🔴 Дніпровський район — повітряна тривога, червоний рівень

🤬25🙏16❤1

Showing the 12 most recent of 1,160 posts we hold for @war_ua_22. 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

@war_ua_22 edited 1 post 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
8 August 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

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.

Дніпро Alerts 🚀 🚨
@dnipro_alerts · 810,349
#1
НУ І ДНІПРО! 🇺🇦
@ny_i_dnipro · 290,015
#2
Николаевский Ванёк
@vanek_nikolaev · 2,575,491
#3
ХДніпро 🇺🇦
@hyevuy_dnepr · 520,728
#4
Лачен пише
@lachentyt · 1,578,193
#5
Труха⚡️Дніпро | Новини
@truexadnepr · 393,175
#6
Дніпро Оперативний 🇺🇦| Війна
@dnepr_operativ · 312,964
#7
Повітряні Сили ЗС України / Air Force of the Armed Forces of Ukraine
@kpszsu · 939,064
#8
Труха⚡️Україна
@truexanewsua · 3,165,061
#9
monitor
@war_monitor · 958,987
#10
Реальна Війна | Україна | Новини
@voynareal · 1,543,423
#11
Дніпро ОПЕРАТИВНИЙ 🇺🇦
@dneproperatyv · 189,122
#12
💙💛ОПЕРАТИВНА БІЛКА 🐿️
@operativnabilka · 7,596
#13
∆✙🍒Гнила черешня🇺🇦✙∆
@gnilayachereha · 412,985
#14
INSIDER UA | Україна | Новини
@insiderukr · 2,146,024
#15
Скринька Пандори
@pandoras_box_ua · 157,920
#16
Всевидящее ОКО (миллион подписчиков)
@oko_ua · 1,408
#17
STERNENKO
@ssternenko · 879,724
#18
✙ 🔼Вертикаль
@vert2026 · 113,724
#19
Хуевый Днепр | Дніпро
@huevyi_dnepr · 168,431
#20
ЦАПЛІЄНКО_UKRAINE FIGHTS
@Tsaplienko · 319,843
#21
Marmuletik🇺🇦
@marmuletik · 49,859
#22
Куди летить? | Тривога
@radar_raketaa · 491,787
#23
Pravda Gerashchenko
@Pravda_Gerashchenko · 303,850
#24
Strategic Control
@strategicontrol · 27,138
#25
НУ І НОВІК
@ny_i_novik · 20,886
#26
Україна Online: Новини | Політика
@UaOnlii · 1,538,096
#27
Інформатор Дніпро | Радар
@dnipro_informator · 29,695
#28
✙ Хамелеон
@xameleon_ua · 24,226
#29
На повестке Днепр
@napovestkeDn · 61,495
#30
🔊⚠️єРадар | Повітряна тривога | Ракетна небезпека
@eRadarrua · 410,896
#31
Донбас Оперативний
@Operatyvnyi_Donbas · 82,204
#32
Тарас Григорович повідомляє
@tgp_news · 58,693
#33
Дніпровський пише
@dnipro_pishet · 52,332
#34
Радар⚡️Дніпро
@RadarDnepr · 14,807
#35
Батальйон Монако
@batalionmonako · 712
#36
✈️Стратегічна авіація
@StrategicaviationT · 132,906
#37
Дніпро TV | Новини | Україна
@dniprotv · 17,387
#38
Радар⚡️Запоріжжя
@radar_zaporizhzhya · 88,923
#39
Оккупация✙Окупація
@kherson_info_ks · 1,481
#40
СКАДОВСЬКИЙ ЗАХИСНИК
@defender_skdvsk · 43,871
#41
Anonymous✙Новини/Монiторинг🇺🇦
@a24nonymous · 11,436
#42
🇺🇦 ANTIZOMBI24 🇺🇦
@anti_zombie24 · 2,012
#43
⚔️БРАТЧУК
@Bratchuk_Sergey · 154,718
#44
Небо Спротиву
@NeboSportyvu · 1,909
#45
Kyiv Alerts 🚀 🚨
@kyiv_alerts · 49,041
#46
Фашик Донецький
@gistapapapa · 104,042
#47
БУТУСОВ ПЛЮС
@ButusovPlus · 348,079
#48
Тополя NEWS
@Topoli_News · 2,801
#49
Олександр Ганжа / Дніпропетровська ОДА (ОВА)
@dnipropetrovskaODA · 47,186
#50
Тотальна Зрада
@totallzrada · 266,456
#51
ДНІПРО LIVE 24/7 🇺🇦 ДНЕПР РАДАР ТРИВОГА
@live_dnepr · 25,406
#52
Грибник🇺🇦
@gribnik_ukr · 6,417
#53
РІА Південь | Запоріжжя | Мелітополь | Україна | Новини
@riamelitopolua · 26,158
#54
Маріуполь.Спротив 🤫
@mrplSprotyv · 23,492
#55
Дніпро Обласний🔝
@dniprooblcentr · 31,216
#56
🇺🇦 SIGNAL 🇺🇦
@signal_ukraine · 9,821
#57
ХПобеда 🇺🇦
@hyevaya_pobeda · 16,247
#58
Інформатор Дніпро
@dp_informator_ua · 47,548
#59
monitoring
@monitorwarr · 85,177
#60
Доброго вечора, ми з Дніпра👋🏻
@we_from_dnipro · 182
#61
НУ І КРИВИЙ РІГ
@ny_i_kryvyi_rih · 9,484
#62
Airborne Division
@airborne1126 · 27,684
#63
🇺🇦🏴‍☠️ "ТРАВ" - 🚨 Тривоги / 🚀 Ракети / 🛩 Авіація / 🇺🇦 Війна в Україні 🇺🇦🏴‍☠️
@wartrav · 18,897
#64
Дивізіон-«ТІВАЗ»
@tivaz_artillery · 41,277
#65
🚀 РАКЕТА UA | Тривога України
@war_raketaua · 85,868
#66
Політмен Покровськ, Костянтинівка, Гуляйполе
@politman_ua · 5,839
#67
Андрій Смолій
@smolii_ukraine · 523,797
#68
Тривога України | Радар
@kiev_nebo · 540,698
#69
Оперативно → by HLEP
@operatyvnohlep · 173,086
#70
Андрющенко Time
@andriyshTime · 29,895
#71
Бросок Мангуста 🇺🇦
@brosok_mangusta · 119,003
#72
Українська Фея🧚🏻‍♀️
@ukranian_fairy88 · 8,610
#73
Включатель Днепр⚡️
@vklyuchatel_dnepr_svet · 194,276
#74
‼️СИРЕНА. ДНІПРО‼️
@sirena_dp · 242,758
#75
Бахмутський Демон 👹
@bahshiddemon · 169,777
#76
Дніпро Аварійна служба (Світло | Графіки)
@avariykaaa · 84,146
#77
Крымский ветер
@Crimeanwind · 223,159
#78
Где повестки Днепр?
@agendaDnepr · 407,030
#79
Дика Кропива 🇺🇦🔱
@DikaKropiva · 6,540
#80

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

НУ І НОВІК
@ny_i_novik · 20,886
Telegram ranks this channel #26 of 78 here — alongside 77 others — read 30 September 2026
Інформатор Дніпро | Радар
@dnipro_informator · 29,695
Telegram ranks this channel #28 of 77 here — alongside 76 others — read 6 September 2026
Новік NOW 🇺🇦 Самар | Новомосковськ
@nashemisto_now · 24,751
Telegram ranks this channel #36 of 73 here — alongside 72 others — read 17 September 2026
ДНІПРО LIVE 24/7 🇺🇦 ДНЕПР РАДАР ТРИВОГА
@live_dnepr · 25,406
Telegram ranks this channel #37 of 78 here — alongside 77 others — read 14 September 2026
Повестки Днепр
@povestki_dnepr_TSK · 39,810
Telegram ranks this channel #37 of 71 here — alongside 70 others — read 31 August 2026
ПОЛУАВТОБИЯ
@poluavtobia · 54,198
Telegram ranks this channel #38 of 82 here — alongside 81 others — read 29 September 2026
НУ І ДНІПРО! 🇺🇦
@ny_i_dnipro · 290,015
Telegram ranks this channel #40 of 72 here — alongside 71 others — read 10 August 2026
На повестке Днепр
@napovestkeDn · 61,495
Telegram ranks this channel #42 of 70 here — alongside 69 others — read 22 August 2026
Дніпропетровський Купол
@alerts_dniproo · 38,805
Telegram ranks this channel #43 of 78 here — alongside 77 others — read 29 August 2026
Дніпровський пише
@dnipro_pishet · 52,332
Telegram ranks this channel #43 of 79 here — alongside 78 others — read 24 August 2026
Включатель Днепр⚡️
@vklyuchatel_dnepr_svet · 194,276
Telegram ranks this channel #46 of 69 here — alongside 68 others — read 12 August 2026
Дніпро ОПЕРАТИВНИЙ 🇺🇦
@dneproperatyv · 189,122
Telegram ranks this channel #48 of 82 here — alongside 81 others — read 11 August 2026
Хуевый Днепр | Дніпро
@huevyi_dnepr · 168,431
Telegram ranks this channel #52 of 82 here — alongside 81 others — read 12 August 2026
Бабуся Світуся
@babusya_svitusya · 54,440
Telegram ranks this channel #63 of 82 here — alongside 81 others — read 29 August 2026
Дніпро Обласний🔝
@dniprooblcentr · 31,216
Telegram ranks this channel #67 of 83 here — alongside 82 others — read 5 September 2026
Доброго вечора, ми з Дніпра👋🏻
@we_from_dnipro · 182
Telegram ranks this channel #80 of 85 here — alongside 84 others — read 18 August 2026

This channel appears in 16 seed channels' Telegram-generated recommendation lists in total. 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 11 November 2026 — this entry's latest reading, not the date you are reading this.

“UA HiMARS 18+🫡” (@war_ua_22), 19,468 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/war_ua_22.

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.