Telegram RegisterThe public register of Telegram
Telegram profile photo for Розвідка України

Channel

Розвідка України

@Ukrainian_Intelligence

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 · Cite this entry

66,423subscribers

+2,939 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001884189327
TypeChannel
Username@Ukrainian_Intelligence
DescriptionНе офіційне джерело. Інформація по моніторингу повітряних загроз. Сітка каналів: https://t.me/sitkakanaliv 📬 Бот для зв’язку — @Ukrainian_Intelligence_Bot Підтримати нас: https://base.monobank.ua/6ypNgk9v7d9Cys
Created25 March 2024 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live11 November 2026
Measurements held63
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/Ukrainian_Intelligence

Topic

International 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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 2 other registered channels. This entry also sits inside a group of 7 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
@Ukrainian_Intelligence/144230 · this entry17 Aug 2026, 23:03 UTC@sectorv666/5404317 Aug 2026, 23:03 UTC1.00under a minute
@Ukrainian_Intelligence/145253 · this entry25 Aug 2026, 12:12 UTC@sectorv666/5474525 Aug 2026, 12:12 UTC1.00under a minute
@Ukrainian_Intelligence/146706 · this entry30 Aug 2026, 13:16 UTC@sectorv666/5573430 Aug 2026, 13:16 UTC1.00under a minute
@Ukrainian_Intelligence/159742 · this entry6 Nov 2026, 02:12 UTC@sectorv666/651176 Nov 2026, 02:12 UTC1.00under a minute
@Ukrainian_Intelligence/160021 · this entry9 Nov 2026, 02:01 UTC@sectorv666/653909 Nov 2026, 02:01 UTC1.00under a minute
@Ukrainian_Intelligence/160024 · this entry9 Nov 2026, 02:51 UTC@sectorv666/653939 Nov 2026, 02:51 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
@sectorv66639 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (39–0)
@bezpechniyregion5 (5/5 hand-verifiable sample passed)1.00under a minutethis 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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 569 comparable posts for this entry, running 7 August 2026 to 11 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 7 channels, the one whose matching posts we hold earliest is @kudy_letyt. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 12 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 7 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

63,48466,92165,202.566,4237 August 202611 November 2026
63 measurements spanning 96 days, net +2,939. 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 62,968–67,437 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)SubscribersChange
11 Nov 2026, 16:4966,423-68
9 Nov 2026, 19:4666,491-48
8 Nov 2026, 11:5966,539-64
7 Nov 2026, 07:3466,603-33
6 Nov 2026, 09:5166,636-40
5 Nov 2026, 09:0566,676-53
4 Nov 2026, 05:1766,729-50
3 Nov 2026, 01:4666,779+65
2 Nov 2026, 04:5066,714+66
1 Nov 2026, 03:5066,648-27
31 Oct 2026, 00:3666,675-32
30 Oct 2026, 02:1966,707-50
29 Oct 2026, 01:5766,757-46
28 Oct 2026, 03:4066,803-21
27 Oct 2026, 00:5766,824-14
25 Oct 2026, 23:2866,838-37
24 Oct 2026, 20:0066,875-29
23 Oct 2026, 19:1166,904-17
22 Oct 2026, 18:2966,921+19
21 Oct 2026, 17:2666,902first reading

Engagement

3,834 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 199 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
12.3%
avg views ÷ 66,423 subscribers
Avg views / post
8,150
1,142 posts measured
Reaction rate
0.709%
reactions ÷ views · ER floor
Posts in window
1,142
of 3,834 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 1,140 of 1,142 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 12 November 2026
Posts held3,834 (6 August 2026 – 12 November 2026)
Views total9,306,428
Reactions total65,953
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Nov 2026, 22:45 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
≈4,130
Videos
≈91
Links
≈44,100

Lifetime counters from Telegram’s own channel header, read 12 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.

Reaction mix

58,387 reactions across 995 posts, in 9 distinct kinds. The most used accounts for 79.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏46,15279.0%
😢5,7859.91%
❤3,0285.19%
custom 52021575038061869842,1113.62%
💯5700.976%
😁5160.884%
🫡1440.247%
😭560.096%
💔250.043%

Custom emoji. One row above is a 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 count beside it is 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 998 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,387 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 18 October 2026 to 12 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: 87 of 1,142 posts held from the last 30 days (7.62%) 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).

12 Nov 2026, 22:34 UTC≈1,020 views13 reactionsread 12 November 2026

Харківщина: реактивний на Берестин Вінниччина: реактивний на Оратів

🙏13

12 Nov 2026, 22:15 UTC≈2,010 views24 reactionsread 12 November 2026

Суми - реактив ⚠️

🙏22❤1😢1

12 Nov 2026, 22:06 UTC≈3,070 views80 reactionsread 12 November 2026

Конотоп під атакою, енергетика 😔

🙏39😢24custom 520215750380618698417

12 Nov 2026, 22:00 UTC≈3,190 views46 reactionsread 12 November 2026

2 шаха на Конотоп ⚠️

🙏30custom 520215750380618698410😢6

12 Nov 2026, 21:44 UTC≈3,920 views42 reactionsread 12 November 2026

Вінниця - реактив ⚠️

🙏34😢7❤1

12 Nov 2026, 21:34 UTC≈4,300 views40 reactionsread 12 November 2026

Рівне - реактив ⚠️

🙏30😢6custom 52021575038061869843❤1

12 Nov 2026, 21:33 UTC≈4,740 views37 reactionsread 12 November 2026

Кіровоградщина: реактивний біля Кропа Вінниччина: реактивний на Ладижин Харківщина: реактивний на Чугуїв, реактивний на Лозову Дніпропетровщина: реактивний на Кривий Ріг Чернігівщина: реактивний на Кіпті

🙏27😢7❤3

12 Nov 2026, 20:49 UTC≈5,640 views46 reactionsread 12 November 2026

Чернігівщина: 2 повз Кіпті на Київщину, 1 на Корюківку (реактивні)

🙏42😢4

12 Nov 2026, 20:35 UTC≈7,090 views55 reactionsread 12 November 2026

Чернігівщина: 2 на Городню з рф, 1 на Куликівку (реактивні) Дніпропетровщина: 2 реактивних поблизу Дніпра

🙏50😢5

12 Nov 2026, 20:20 UTC≈7,800 views44 reactionsread 12 November 2026

Чернігівщина: реактивний на Сновськ з Брянщини Житомирщина: реактивний на Олевськ Київщина: реактивний на Білу Церкву зі сходу

🙏33😢11

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

@Ukrainian_Intelligence 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
26 August 2026
Most recent edit
26 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

Named by 8 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.

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.

Strategic Control
@strategicontrol · 27,138
#1
✈️Стратегічна авіація
@StrategicaviationT · 132,906
#2
Повітряні Сили ЗС України / Air Force of the Armed Forces of Ukraine
@kpszsu · 939,064
#3
monitor
@war_monitor · 958,987
#4
🔊⚠️єРадар | Повітряна тривога | Ракетна небезпека
@eRadarrua · 410,896
#5
Tracking
@the_first_online · 8,077
#6
Око України - Захід.
@eyeukrainew · 24,800 (as read 21 August 2026)
#7
monitoring
@monitorwarr · 85,253
#8
Лачен пише
@lachentyt · 1,578,193
#9
Андрій Смолій
@smolii_ukraine · 523,797
#10
ОПЕРАТИВНИЙ ІНФОРМ
@operinform · 135,911
#11
MonitorZagroz / Моніторинг 24/7
@UkraineMonitorZagroz · 4,647
#12
Київ ІНФО | Новини Україна 🇺🇦
@kievinfo_kyiv · 1,258,994
#13
Повітряний простір України 🇺🇦
@monikppy · 229,138
#14
ППО радар | Напрямок ракет | Напрямок шахедів |
@mon1tor_ua · 264,047
#15
monitorwar
@monitoringwar · 26,405
#16
Веселий Південь
@veselyy_pivden · 37,474
#17
Ринда моніторить
@kudy_letyt · 159,190
#18
AviVector
@avivector · 6,886
#19
Тотальна Зрада
@totallzrada · 266,456
#20
𝗪𝗕 | Вакансії та робота
@work_balance_ua · 1,932 (as read 21 August 2026)
#21
ПІВНІЧ
@pivnic · 2,968
#22
Чому тривога | Радар
@raketa_trevoga · 473,200
#23
УСЕ ПРО ВСЕ ВІДРАЗУ: КИЇВЩИНА , ПОЛТАВЩИНА
@useprovse1 · 31,716
#24
Реальна Війна | Україна | Новини
@voynareal · 1,543,423
#25
Карта повітряних тривог 🇺🇦
@alarmua · 941,284
#26
Що в повітрі? | Моніторинг
@monitoringwarua · 12,112
#27
STERNENKO
@ssternenko · 880,350
#28
Карта повітряних тривог ‼️ Вибухи ‼️ Ракети ‼️
@povitryanatrivogaaa · 729,360
#29
Бойова Україна — monitoring
@RadaUaxRn · 1,477
#30
Небо Спротиву
@NeboSportyvu · 1,909
#31
ППО UA | РАДАР📡
@PpoUaRadar0 · 35,850
#32
Куди летить? | Тривога
@radar_raketaa · 491,787
#33
‼️ТРИВОГА ~ РАДАР🚀ДЕ РАКЕТА? ДЕ ШАХЕД? ДЕ ТРИВОГА?
@truvogaradar · 21,137
#34
∆✙🍒Гнила черешня🇺🇦✙∆
@gnilayachereha · 412,985
#35
Київський купол | Графіки
@nebo_raketa · 543,748
#36
Північний Сич 🦉
@Northern_Sich_ukr · 109,428
#37
kyiv_monit0ring
@kyiv_m0nitoring · 50
#38
Україна Online: Новини | Політика
@UaOnlii · 1,538,096
#39
Авіа Моніторинг
@avia_monitoring · 850
#40
ЧП СтратАвиа 🇺🇦
@CPSTRATAVIA · 461
#41
Strategic Overhead
@ru_avia · 5,000
#42
ЗАХІДНИЙ РАДАР
@zahidnuiradar · 8,286
#43
Aeris Rimor
@AerisRimor · 163,362
#44
🇺🇦НАШЕ ППО 🚀Де Ракета|Де Шахед📡
@Nashee_PPO · 33,273
#45
monitorsmu
@monitorsmy · 37
#46
НУ І ДНІПРО! 🇺🇦
@ny_i_dnipro · 290,015
#47
Легіон Диванної Розвідки 🇺🇦🔱
@couch_iu · 30,810
#48
🔊Чому тривога?🚨| Повітряна тривога | Ракетна небезпека | єРадар |
@tryvoga_chomu · 272,338
#49
🚀 РАКЕТА UA | Тривога України
@war_raketaua · 85,868
#50
🇺🇦🏴‍☠️ "ТРАВ" - 🚨 Тривоги / 🚀 Ракети / 🛩 Авіація / 🇺🇦 Війна в Україні 🇺🇦🏴‍☠️
@wartrav · 18,897
#51
єРадіоефір
@air_radioefir · 1,433
#52
Вибухи та бавовна
@vybuhy_bavovna · 82,144
#53
Тривога України | Радар
@kiev_nebo · 540,698
#54
AirGuard
@airguardua · 7,497 (as read 21 August 2026)
#55
Офіцер
@officer_33 · 179,469
#56
Повітряна Тривога
@air_alert_ua · 226,758
#57
Kyiv | Monitoring
@Kyiv_Monitoring1 · 32,572
#58
Женьок Вещає…
@ZhenyokSay · 157,839
#59
🚀 Ракетна небезпека | України | шахеди | вибухи |
@vibuxaviasia · 56,724
#60
AviMonitor
@avimonitor · 2,946
#61
Реальний Київ | Украина
@kievreal1 · 1,552,209
#62
INSIDER UA | Україна | Новини
@insiderukr · 2,146,024
#63
Труха⚡️Україна
@truexanewsua · 3,168,131
#64
✙ 🔼Вертикаль
@vert2026 · 113,724
#65
Всевидящее ОКО (миллион подписчиков)
@oko_ua · 1,408
#66
Скринька Пандори
@pandoras_box_ua · 157,920
#67
Говорять Снайпер ꑭ
@stanislav_osman · 288,854
#68
Вмикач Київ | Світло💡
@kiev_svet · 236,798
#69
Киевский Движ
@k_dvizh · 470,907
#70
Бавовна
@ukrbavovna · 801,855
#71
Труха⚡️Київ
@truexakyiv · 972,159
#72
Левый Берег Киев
@kiev_levyy_bereg · 493,259
#73
Дніпро Alerts 🚀 🚨
@dnipro_alerts · 810,349
#74
Крымский ветер
@Crimeanwind · 223,159
#75
єСвітло💡Київ | Світло
@esvitlo_kyiv_ua · 168,159
#76
Військово-Морські Сили ЗС України | UA Navy
@ukrainian_navy · 12,372
#77
Без Анестезии
@bez_anestesii · 346
#78
УС: Україна, новини, політика, війна
@u_now · 1,400,989
#79
Бахмутський Демон 👹
@bahshiddemon · 169,777
#80
Батальйон Монако
@batalionmonako · 712
#81
Ту-95МС
@tu95mc · 1,648
#82
Air - Love Ukrainе ❤️
@Aviation_airspace · 59 (as read 21 August 2026)
#83

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

Appears in Telegram’s recommendations for other channels

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

✈️Стратегічна авіація
@StrategicaviationT · 132,906
Telegram ranks this channel #2 of 84 here — alongside 83 others — read 15 August 2026
Повітряний простір України 🇺🇦
@monikppy · 229,138
Telegram ranks this channel #3 of 80 here — alongside 79 others — read 14 August 2026
Північний Сич 🦉
@Northern_Sich_ukr · 109,428
Telegram ranks this channel #9 of 85 here — alongside 84 others — read 16 August 2026
kyiv_monit0ring
@kyiv_m0nitoring · 50
Telegram ranks this channel #12 of 84 here — alongside 83 others — read 16 August 2026
#SK# говорить🇺🇦
@SK_DM_SK · 191,986
Telegram ranks this channel #12 of 89 here — alongside 88 others — read 14 August 2026
monitoring захід
@monitoring_zaxid · 161,561
Telegram ranks this channel #13 of 77 here — alongside 76 others — read 23 August 2026
ППО радар | Напрямок ракет | Напрямок шахедів |
@mon1tor_ua · 264,047
Telegram ranks this channel #16 of 90 here — alongside 89 others — read 14 August 2026
Чисте небо Київська область та Київ.
@chyste_nebo · 272,477
Telegram ranks this channel #17 of 83 here — alongside 82 others — read 14 August 2026
monitorsmu
@monitorsmy · 37
Telegram ranks this channel #22 of 81 here — alongside 80 others — read 27 August 2026
Вартові Півдня 🔱
@pivden_varta · 120,480
Telegram ranks this channel #22 of 73 here — alongside 72 others — read 16 August 2026
Ракети
@ua_rockets · 71,850
Telegram ranks this channel #26 of 81 here — alongside 80 others — read 21 August 2026
Ukraine 24/7 ⚠️
@Ukraine_UA_24_7 · 77,235
Telegram ranks this channel #26 of 84 here — alongside 83 others — read 20 August 2026
КОРАБЕЛИ
@korabely_media · 156,508
Telegram ranks this channel #32 of 87 here — alongside 86 others — read 14 August 2026
🚀 РАКЕТА UA | Тривога України
@war_raketaua · 85,868
Telegram ranks this channel #34 of 87 here — alongside 86 others — read 17 August 2026
🚀 Ракетна небезпека | України | шахеди | вибухи |
@vibuxaviasia · 56,724
Telegram ranks this channel #42 of 87 here — alongside 86 others — read 22 August 2026
monitoring
@monitorwarr · 85,253
Telegram ranks this channel #43 of 90 here — alongside 89 others — read 18 August 2026
Вибухи та бавовна
@vybuhy_bavovna · 82,144
Telegram ranks this channel #46 of 86 here — alongside 85 others — read 18 August 2026
Радар ППО🚀| Карта тривог
@raketa_rakety_de · 51,174
Telegram ranks this channel #49 of 78 here — alongside 77 others — read 24 August 2026
Тактична Рукавичка/НІЖИН
@taktychna_rukavuchkaa · 47,391
Telegram ranks this channel #50 of 66 here — alongside 65 others — read 27 August 2026
Злі Полісяни Житомир
@Angry_Pol · 63,691
Telegram ranks this channel #50 of 67 here — alongside 66 others — read 23 August 2026
НАШЕ ППО 🇺🇦 | Радар ракет, шахедів
@nashe_ppo_monitoring · 43,014
Telegram ranks this channel #52 of 86 here — alongside 85 others — read 28 August 2026
Женьок Вещає…
@ZhenyokSay · 157,839
Telegram ranks this channel #53 of 94 here — alongside 93 others — read 14 August 2026
Старокостянтинів 24/7
@starkon_24_7 · 73,792
Telegram ranks this channel #66 of 82 here — alongside 81 others — read 21 August 2026
Повітряна Тривога 🚀 Карта Київська
@ukrainar · 105,691
Telegram ranks this channel #69 of 87 here — alongside 86 others — read 19 August 2026

This channel appears in 26 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 11 November 2026 — this entry's latest reading, not the date you are reading this.

“Розвідка України” (@Ukrainian_Intelligence), 66,423 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/Ukrainian_Intelligence.

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.