Telegram RegisterThe public register of Telegram
Telegram profile photo for Strategic Control

Channel

Strategic Control

@strategicontrol

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

27,117subscribers

+2,543 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-1002070244584
TypeChannel
Username@strategicontrol
DescriptionКанал який спеціалізується на моніторингу стратегічної та військово-транспортної авіації ворога. Моніторинг повітряного простору та завчасне попередження населення про ймовірні загрози.
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 November 2026
Measurements held62
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/strategicontrol

Topic

Other / unclassifiable — 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 94% 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 1 other registered channel. 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
@patriot_monitoring/339523 Nov 2026, 15:57 UTC@strategicontrol/105962 · this entry3 Nov 2026, 15:57 UTC1.00under a minute
@strategicontrol/106776 · this entry7 Nov 2026, 15:10 UTC@patriot_monitoring/344227 Nov 2026, 15:13 UTC1.003 minutes
@patriot_monitoring/3479210 Nov 2026, 21:42 UTC@strategicontrol/107643 · this entry10 Nov 2026, 21:44 UTC1.002 minutes
@strategicontrol/108077 · this entry13 Nov 2026, 19:42 UTC@patriot_monitoring/3513913 Nov 2026, 19:43 UTC1.0072 seconds
@strategicontrol/108082 · this entry13 Nov 2026, 20:18 UTC@patriot_monitoring/3514413 Nov 2026, 20:18 UTC1.00under a minute
@strategicontrol/108083 · this entry13 Nov 2026, 20:36 UTC@patriot_monitoring/3514513 Nov 2026, 20:38 UTC1.002 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
@patriot_monitoring8 (8/8 hand-verifiable sample passed)0.9972 secondseven

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. 4 of the 4 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 336 comparable posts for this entry, running 6 August 2026 to 16 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 key clone_mutual, 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

24,57327,18325,87827,1177 August 202614 November 2026
62 measurements spanning 99 days, net +2,543. 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 24,182–27,575 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 62
Measured (UTC)SubscribersChange
14 Nov 2026, 21:0027,117-21
11 Nov 2026, 22:4527,138-12
10 Nov 2026, 03:1127,150-24
8 Nov 2026, 17:0027,174+4
7 Nov 2026, 13:5927,170+13
6 Nov 2026, 11:4727,157-26
5 Nov 2026, 09:4727,183+7
4 Nov 2026, 12:1027,176-4
3 Nov 2026, 10:2827,180+98
2 Nov 2026, 11:2827,082+25
1 Nov 2026, 09:1627,057+8
29 Oct 2026, 05:2827,049-4
28 Oct 2026, 04:0027,053-18
27 Oct 2026, 04:3727,071+24
26 Oct 2026, 06:5027,047-9
25 Oct 2026, 06:5427,056+5
24 Oct 2026, 06:0627,051+22
23 Oct 2026, 02:2827,029+33
21 Oct 2026, 22:3126,996+33
20 Oct 2026, 15:5926,963first reading

Engagement

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

ERR · 30 days
7.54%
avg views ÷ 27,117 subscribers
Avg views / post
2,040
1,160 posts measured
Reaction rate
0.568%
reactions ÷ views · ER floor
Posts in window
1,160
of 2,981 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,134 of 1,160 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 17 November 2026
Posts held2,981 (6 August 2026 – 17 November 2026)
Views total2,371,526
Reactions total13,322
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 04:58 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
≈1,670
Videos
≈342
Links
≈654

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

11,767 reactions across 973 posts, in 5 distinct kinds. The most used accounts for 89.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏10,49189.2%
😢5744.88%
❤4774.05%
👍1601.36%
🫡650.552%

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 978 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 11,767 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 22 October 2026 to 17 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
10
across the posts below
Posts paid on
2
of 1,000 we hold a reading for · 0.2%
Most on one post
8
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @strategicontrol. 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 22 October 2026 to 17 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: 27 of 1,160 posts held from the last 30 days (2.33%) 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).

17 Nov 2026, 04:56 UTC304 views0 reactionsread 17 November 2026

Тут без змін, тільки звичайних стало трішки більше.

17 Nov 2026, 04:54 UTC609 views14 reactionsread 17 November 2026

Ракети на Запоріжжя з півночі!

🙏14

17 Nov 2026, 04:53 UTC910 views5 reactionsread 17 November 2026

Друзі, завдяки вашій підтримці канал продовжує працювати та стає кращим, будемо вдячні! Реквізити (MonoBank): — Картка: 4441 1111 2699 9154 — Банка: https://send.monobank.ua/jar/8ZtS6hSm8J Реквізити (Privat Bank): — Картка: 5168752137586957 — Конверт: https://www.privat24.ua/send/25ikq

🙏5

17 Nov 2026, 04:48 UTC≈1,210 views20 reactionsread 17 November 2026

Черкаси та область - теж чисто.

🙏19❤1

17 Nov 2026, 04:47 UTC≈1,220 views18 reactionsread 17 November 2026

Дніпро та область - чисто по крилатим ракетам.

🙏17❤1

17 Nov 2026, 04:46 UTC≈1,520 views19 reactionsread 17 November 2026

Дніпро - проліт ракети над містом!

🙏18❤1

17 Nov 2026, 04:45 UTC≈1,520 views15 reactionsread 17 November 2026

Загалом: Сміла, Черкаси, Запоріжжя, Дніпро, Павлоград - поки максимальна увага.

🙏15

17 Nov 2026, 04:45 UTC≈1,520 views16 reactionsread 17 November 2026

Одна з ракет полетіла на Павлоград.

🙏16

17 Nov 2026, 04:45 UTC≈1,520 views12 reactionsread 17 November 2026

Запоріжжя - увага.

🙏11❤1

17 Nov 2026, 04:44 UTC≈1,520 views8 reactionsread 17 November 2026

Деякі пролітають на Смілу - може бути гучно!

🙏8

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

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.

✈️Стратегічна авіація
@StrategicaviationT · 132,886
#1
Повітряні Сили ЗС України / Air Force of the Armed Forces of Ukraine
@kpszsu · 938,428
#2
monitor
@war_monitor · 958,023
#3
🔊⚠️єРадар | Повітряна тривога | Ракетна небезпека
@eRadarrua · 410,667
#4
Tracking
@the_first_online · 8,054
#5
#SK# говорить🇺🇦
@SK_DM_SK · 191,904
#6
Український | ППОшник
@ukrainsiyppohnik · 10,627
#7
monitoring
@monitorwarr · 85,150
#8
eyeukrainew
@eyeukrainew · 8
#9
Ринда моніторить
@kudy_letyt · 159,456
#10
MonitorZagroz / Моніторинг 24/7
@UkraineMonitorZagroz · 4,647
#11
Андрій Смолій
@smolii_ukraine · 523,723
#12
Лачен пише
@lachentyt · 1,576,100
#13
ОПЕРАТИВНИЙ ІНФОРМ
@operinform · 135,692
#14
Повітряний простір України 🇺🇦
@monikppy · 228,243
#15
monitorwar
@monitoringwar · 26,384
#16
Київ ІНФО | Новини Україна 🇺🇦
@kievinfo_kyiv · 1,261,551
#17
AviVector
@avivector · 6,918
#18
ПІВНІЧ
@pivnic · 2,960
#19
ППО радар | Напрямок ракет | Напрямок шахедів |
@mon1tor_ua · 263,748
#20
Тотальна Зрада
@totallzrada · 265,783
#21
Полковник ГШ
@war_home · 15,352
#22
Небо Спротиву
@NeboSportyvu · 1,902
#23
Чому тривога | Радар
@raketa_trevoga · 471,573
#24
STERNENKO
@ssternenko · 879,121
#25
Карта повітряних тривог ‼️ Вибухи ‼️ Ракети ‼️
@povitryanatrivogaaa · 728,432
#26
Авіа Моніторинг
@avia_monitoring · 850
#27
Карта повітряних тривог 🇺🇦
@alarmua · 940,548
#28
TLk News
@tlknewsua · 640,966
#29
ЗАХІДНИЙ РАДАР
@zahidnuiradar · 8,217
#30
Моніторинг Київ | Аналітика
@kyiv_m0nitoring · 112,199
#31
⚡️Resident ППО ⚡️
@residenttsss · 13,584 (as read 13 September 2026)
#32
Дніпро Alerts 🚀 🚨
@dnipro_alerts · 809,443
#33
Бавовна
@ukrbavovna · 800,178
#34
Північний Сич 🦉
@Northern_Sich_ukr · 109,616
#35
ППО UA | РАДАР📡
@PpoUaRadar0 · 35,757
#36
∆✙🍒Гнила черешня🇺🇦✙∆
@gnilayachereha · 412,798
#37
Бойова Україна — monitoring
@RadaUaxRn · 1,474
#38
Куди летить? | Тривога
@radar_raketaa · 490,712
#39
ЧП СтратАвиа 🇺🇦
@CPSTRATAVIA · 461
#40
‼️ТРИВОГА ~ РАДАР🚀ДЕ РАКЕТА? ДЕ ШАХЕД? ДЕ ТРИВОГА?
@truvogaradar · 21,075
#41
Strategic Overhead
@ru_avia · 4,986
#42
Женьок Вещає…
@ZhenyokSay · 157,813
#43
🚀 Ракетна небезпека | України | шахеди | вибухи |
@vibuxaviasia · 56,554
#44
НУ І ДНІПРО! 🇺🇦
@ny_i_dnipro · 289,947
#45
🇺🇦 Служба Моніторингу України
@monitorsmy · 60,142
#46
Aeris Rimor
@AerisRimor · 163,167
#47
єРадіоефір
@air_radioefir · 1,425
#48
🚀 РАКЕТНА неБЕЗПЕКА 🚀
@rocket_danger_lviv · 398,152
#49
🇺🇦НАШЕ ППО 🚀Де Ракета|Де Шахед📡
@Nashee_PPO · 33,202
#50
Повітряний простір | Напрямок ракет
@ukraine_pyxx · 209,538
#51
War Monitoring
@WarrMonitoring · 3,429
#52
🔊Чому тривога?🚨| Повітряна тривога | Ракетна небезпека | єРадар |
@tryvoga_chomu · 271,891
#53
🚀 РАКЕТА UA | Тривога України
@war_raketaua · 85,686
#54
✙DeepState✙🇺🇦
@deepstateua · 750,207
#55
AviMonitor
@avimonitor · 2,922
#56
Сіверські Націоналісти𓃟
@pivnichmmedia · 14,166
#57
Реальний Київ | Украина
@kievreal1 · 1,550,018
#58
Ту-95МС
@tu95mc · 1,636
#59
INSIDER UA | Україна | Новини
@insiderukr · 2,141,667
#60
Труха⚡️Україна
@truexanewsua · 3,165,345
#61
Що в повітрі? | Моніторинг
@monitoringwarua · 12,202
#62
Скринька Пандори
@pandoras_box_ua · 157,764
#63
✙ 🔼Вертикаль
@vert2026 · 113,508
#64
Всевидящее ОКО (миллион подписчиков)
@oko_ua · 1,751
#65
Реальна Війна | Україна | Новини
@voynareal · 1,541,547
#66
Україна Online: Новини | Політика
@UaOnlii · 1,536,697
#67
Військово-Морські Сили ЗС України | UA Navy
@ukrainian_navy · 12,389
#68
Крымский ветер
@Crimeanwind · 222,849
#69
Київський купол | Графіки
@nebo_raketa · 542,733
#70
Киевский Движ
@k_dvizh · 470,624
#71
Труха⚡️Київ
@truexakyiv · 972,266
#72
Захід Головне
@zahid_golovne_ua · 602,810
#73
Без Анестезии
@bez_anestesii · 346
#74
Легіон Диванної Розвідки 🇺🇦🔱
@couch_iu · 30,608
#75
Бахмутський Демон 👹
@bahshiddemon · 169,645
#76
Левый Берег Киев
@kiev_levyy_bereg · 492,701
#77
Соняшник🦅
@soniah_hub · 42,193
#78
єСвітло💡Київ | Світло
@esvitlo_kyiv_ua · 167,857
#79
Вмикач Київ | Світло💡
@kiev_svet · 235,748
#80

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

Appears in Telegram’s recommendations for other channels

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

eyeukrainew
@eyeukrainew · 8
Telegram ranks this channel #1 of 82 here — alongside 81 others — read 13 September 2026
monitoring захід
@monitoring_zaxid · 161,909
Telegram ranks this channel #1 of 77 here — alongside 76 others — read 23 August 2026
Розвідка України
@Ukrainian_Intelligence · 66,242
Telegram ranks this channel #1 of 83 here — alongside 82 others — read 21 August 2026
Північний Сич 🦉
@Northern_Sich_ukr · 109,616
Telegram ranks this channel #1 of 85 here — alongside 84 others — read 16 August 2026
✈️Стратегічна авіація
@StrategicaviationT · 132,886
Telegram ranks this channel #1 of 84 here — alongside 83 others — read 15 August 2026
Повітряний простір України 🇺🇦
@monikppy · 228,243
Telegram ranks this channel #1 of 80 here — alongside 79 others — read 14 August 2026
‼️ТРИВОГА ~ РАДАР🚀ДЕ РАКЕТА? ДЕ ШАХЕД? ДЕ ТРИВОГА?
@truvogaradar · 21,075
Telegram ranks this channel #2 of 73 here — alongside 72 others — read 22 September 2026
🇺🇦НАШЕ ППО 🚀Де Ракета|Де Шахед📡
@Nashee_PPO · 33,202
Telegram ranks this channel #2 of 78 here — alongside 77 others — read 3 September 2026
ППО UA | РАДАР📡
@PpoUaRadar0 · 35,757
Telegram ranks this channel #3 of 79 here — alongside 78 others — read 31 August 2026
monitorwar
@monitoringwar · 26,384
Telegram ranks this channel #4 of 84 here — alongside 83 others — read 12 September 2026
Моніторинг Київ | Аналітика
@kyiv_m0nitoring · 112,199
Telegram ranks this channel #4 of 84 here — alongside 83 others — read 16 August 2026
Каменський Пацюк 🇺🇦🫡
@stone_rat · 34,233
Telegram ranks this channel #5 of 78 here — alongside 77 others — read 14 September 2026
#SK# говорить🇺🇦
@SK_DM_SK · 191,904
Telegram ranks this channel #5 of 89 here — alongside 88 others — read 14 August 2026
🇺🇦 Служба Моніторингу України
@monitorsmy · 60,142
Telegram ranks this channel #6 of 81 here — alongside 80 others — read 27 August 2026
ППО РАДАР 🇺🇦 | Карта тривог | Моніторинг
@PpoUaRadar · 27,374
Telegram ranks this channel #7 of 81 here — alongside 80 others — read 9 September 2026
УСЕ ПРО ВСЕ ВІДРАЗУ: КИЇВЩИНА , ПОЛТАВЩИНА
@useprovse1 · 31,656
Telegram ranks this channel #7 of 82 here — alongside 81 others — read 5 September 2026
Тривога Старкон !!!!
@grup223m · 35,941
Telegram ranks this channel #8 of 75 here — alongside 74 others — read 10 September 2026
ППО радар | Напрямок ракет | Напрямок шахедів |
@mon1tor_ua · 263,748
Telegram ranks this channel #9 of 90 here — alongside 89 others — read 14 August 2026
🇺🇦🏴‍☠️ "ТРАВ" - 🚨 Тривоги / 🚀 Ракети / 🛩 Авіація / 🇺🇦 Війна в Україні 🇺🇦🏴‍☠️
@wartrav · 18,825
Telegram ranks this channel #12 of 79 here — alongside 78 others — read 23 September 2026
Ракети
@ua_rockets · 71,802
Telegram ranks this channel #13 of 81 here — alongside 80 others — read 21 August 2026
Злі Полісяни Житомир
@Angry_Pol · 63,696
Telegram ranks this channel #16 of 67 here — alongside 66 others — read 23 August 2026
Ukraine 24/7 ⚠️
@Ukraine_UA_24_7 · 76,958
Telegram ranks this channel #16 of 84 here — alongside 83 others — read 20 August 2026
КОРАБЕЛИ
@korabely_media · 156,615
Telegram ranks this channel #16 of 87 here — alongside 86 others — read 14 August 2026
Де ракета Тривога
@trivoga6 · 36,562
Telegram ranks this channel #18 of 80 here — alongside 79 others — read 31 August 2026

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

“Strategic Control” (@strategicontrol), 27,117 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/strategicontrol.

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.