Telegram RegisterThe public register of Telegram
Telegram profile photo for Monitoring SKYWATCH

Channel

Monitoring SKYWATCH

@rocketskyiv

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

25,003subscribers

+4,086 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-1002975794606
TypeChannel
Username@rocketskyiv
DescriptionКанал про вихід балістики/рух ракет від Моніторинг Київ | Аналітика. https://base.monobank.ua/6SBzaiAWx3nqhs
CreatedBetween 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live30 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 30 September 2026
On Telegramt.me/rocketskyiv

Topic

National 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 10 August 2026 and assigned it the closest of 31 fixed categories, at 49% 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 why it has no browse page of its own yet.

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.

Views per post sit far above this size band

27,900 average views per post against 25,003 subscribers — an engagement rate of 111.6%. Across the 461 registered channels in the same cohort — 10,332–31,590 subscribers, posting mainly in Ukrainian — the middle half sit between 10.1% and 27.7%, with a median of 17.4%.

What this was computed from
Window30 days (2 September 2026 – 2 October 2026)
Posts measured35 of 35 published in the window (0 exact, 35 rounded by Telegram)
Views totalled976,900
Mature posts only112.5% over 34 posts read at least 24h after publication
Subscribers25,003 measured 30 September 2026
Cohortb10000:ukr · 461 channels · p10 5.72% · p25 10.1% · p50 17.4% · p75 27.7% · p90 41.5%
Position in cohort99.565th percentile · 6.4× the cohort median
Uncertainty±0.017% of the figure, from Telegram’s rounding
Post languageUkrainian · 96.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 key err_high, last confirmed 2 October 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

20,91725,00322,9607 August 2026 — 20,917 subscribers7 August 2026 — 20,917 subscribers7 August 2026 — 20,954 subscribers8 August 2026 — 21,051 subscribers10 August 2026 — 21,167 subscribers10 August 2026 — 21,146 subscribers12 August 2026 — 21,148 subscribers13 August 2026 — 21,224 subscribers14 August 2026 — 21,193 subscribers16 August 2026 — 21,176 subscribers17 August 2026 — 21,155 subscribers18 August 2026 — 21,151 subscribers19 August 2026 — 21,129 subscribers20 August 2026 — 22,339 subscribers21 August 2026 — 22,304 subscribers23 August 2026 — 22,239 subscribers25 August 2026 — 22,199 subscribers26 August 2026 — 22,144 subscribers26 August 2026 — 22,097 subscribers27 August 2026 — 22,005 subscribers28 August 2026 — 21,985 subscribers30 August 2026 — 21,952 subscribers30 August 2026 — 21,930 subscribers31 August 2026 — 21,910 subscribers1 September 2026 — 21,886 subscribers3 September 2026 — 21,887 subscribers4 September 2026 — 21,863 subscribers7 September 2026 — 21,852 subscribers10 September 2026 — 22,537 subscribers12 September 2026 — 22,495 subscribers14 September 2026 — 22,497 subscribers15 September 2026 — 22,476 subscribers18 September 2026 — 22,361 subscribers30 September 2026 — 25,003 subscribers7 August 202630 September 2026
34 measurements spanning 54 days, net +4,086. 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 20,304–25,616 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
30 Sept 2026, 20:1625,003+2,642
18 Sept 2026, 05:1822,361-115
15 Sept 2026, 20:3822,476-21
14 Sept 2026, 06:4222,497+2
12 Sept 2026, 15:3722,495-42
10 Sept 2026, 17:5522,537+685
7 Sept 2026, 17:1921,852-11
4 Sept 2026, 19:2021,863-24
3 Sept 2026, 01:3821,887+1
1 Sept 2026, 23:5621,886-24
31 Aug 2026, 21:0621,910-20
30 Aug 2026, 22:2521,930-22
30 Aug 2026, 01:4521,952-33
28 Aug 2026, 22:1821,985-20
27 Aug 2026, 20:4222,005-92
26 Aug 2026, 23:1322,097-47
26 Aug 2026, 02:1622,144-55
25 Aug 2026, 00:3422,199-40
23 Aug 2026, 09:2322,239-65
21 Aug 2026, 20:1722,304first reading

Engagement

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

ERR · 30 days
112.2%
avg views ÷ 25,003 subscribers
Avg views / post
28,100
35 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
35
of 100 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 1 October 2026
Posts held100 (30 July 2026 – 1 October 2026)
Views total981,800
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Oct 2026, 18:24 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

Lifetime counters from Telegram’s own channel header, read 2 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

1 Oct 2026, 17:37 UTC≈21,700 viewsread 2 October 2026

Розвідспільнота США попереджає про масований обстріл ЗОКРЕМА Київського регіону у наступні 72 години. Зафіксований підвоз 23х балістичних ракет до місць вірогідного розгортання пускових установок.

30 Sept 2026, 18:08 UTC≈18,800 viewsread 2 October 2026

❗️Надійшло попередження на найближчі 48 годин. Під загрозу підпадають Полтавщина і Кривий Ріг. ❗️Проте, плани ворога ніхто не знає точно. Ми проінформуємо.

30 Sept 2026, 00:31 UTC≈19,900 viewsread 2 October 2026

Весь запас балістики відстріляли. Сюрпризів не повинно бути. До відбою ніні!

30 Sept 2026, 00:12 UTC≈19,400 viewsread 2 October 2026

Ось вам і пристрілочка та розрядка ППО 🥲

29 Sept 2026, 19:28 UTC≈23,500 viewsread 2 October 2026

✅ Попередження про будь які атаки відсутні станом на цей вечір.

29 Sept 2026, 16:12 UTC≈24,900 viewsread 2 October 2026
Photo

❗️❗️Уточнено дані щодо нічного обстрілу. Ворог зробив тестовий пуск ракети Іскандер-М нової модифікації. Ракета повинна бути більш точною та маневреною щоб обходити ППО, також присутні непідтверджені дані щодо збільшення її дальності польоту. Сили ППО збили цю ракету.

28 Sept 2026, 23:02 UTC≈19,700 viewsread 2 October 2026

Масованої супер-пупер атаки не було. Більш схоже на «розрядку ППО», проте є інформація що деякі не збиті ракети можливо впали в області.

28 Sept 2026, 22:29 UTC≈19,600 viewsread 2 October 2026

Працюють системи протиракетної оборони. Цілком успішно 👍

28 Sept 2026, 22:19 UTC≈19,600 viewsread 2 October 2026

3 ракети Балістика на Київ/передмістя.

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

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.

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

“Monitoring SKYWATCH” (@rocketskyiv), 25,003 subscribers as measured 30 September 2026. Telegram Register, tgregister.com/channel/rocketskyiv.

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.