Telegram RegisterThe public register of Telegram
Telegram profile photo for Радар Севастополь | Крым

Channel

Радар Севастополь | Крым

@radar_sevastopol_crimea

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

9,732subscribers

-26 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002746711778
TypeChannel
Username@radar_sevastopol_crimea
CreatedBetween 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live17 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/radar_sevastopol_crimea

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 43% 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.

Growth

9,7129,7779,744.56 August 2026 — 9,758 subscribers6 August 2026 — 9,758 subscribers7 August 2026 — 9,759 subscribers10 August 2026 — 9,746 subscribers13 August 2026 — 9,777 subscribers16 August 2026 — 9,770 subscribers19 August 2026 — 9,761 subscribers23 August 2026 — 9,750 subscribers26 August 2026 — 9,727 subscribers29 August 2026 — 9,743 subscribers1 September 2026 — 9,732 subscribers4 September 2026 — 9,712 subscribers10 September 2026 — 9,739 subscribers13 September 2026 — 9,729 subscribers17 September 2026 — 9,732 subscribers9,7326 August 202617 September 2026
15 measurements spanning 42 days, net -26. 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 9,702–9,787 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 23:169,732+3
13 Sept 2026, 18:569,729-10
10 Sept 2026, 02:379,739+27
4 Sept 2026, 11:159,712-20
1 Sept 2026, 05:499,732-11
29 Aug 2026, 15:339,743+16
26 Aug 2026, 12:129,727-23
23 Aug 2026, 18:129,750-11
19 Aug 2026, 21:559,761-9
16 Aug 2026, 15:579,770-7
13 Aug 2026, 04:059,777+31
10 Aug 2026, 14:389,746-13
7 Aug 2026, 06:349,759+1
6 Aug 2026, 22:459,758no change
6 Aug 2026, 22:379,758first reading

Engagement

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

ERR · 30 days
2.13%
avg views ÷ 9,732 subscribers
Avg views / post
208
80 posts measured
Reaction rate
0.63%
reactions ÷ views · ER floor
Posts in window
80
of 694 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 10 of 80 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 29 August 2026
Posts held694 (6 August 2026 – 29 August 2026)
Views total16,615
Reactions total15
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 05:21 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
1m 43s
Average length
21s

Measured directly from 5 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 reactions across 43 posts, in 9 distinct kinds. The most used accounts for 29.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1729.3%
🙏1322.4%
🤬1220.7%
❤‍🔥712.1%
👍58.62%
👨‍💻11.72%
🔥11.72%
😴11.72%
🤣11.72%

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 56 of the 694 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 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 694 most recent posts we hold, published 6 August 2026 to 29 August 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

29 Aug 2026, 04:15 UTC110 viewsread 29 August 2026

Красная Поляна Глебовка Черноморский район и далее в направлении Новоозерное, Евпатория Опасность по БПЛА

29 Aug 2026, 03:48 UTC135 viewsread 29 August 2026

Внуково примерно от Межводное, Возможно дальше на Донузлав в сторону трассы Опасность по БПЛА Республика Крым

29 Aug 2026, 03:33 UTC148 viewsread 29 August 2026

Бакальская коса, Славное, Стерегущее и близлежащие Опасность по БПЛА с моря Раздольненский район и далее в тыл

29 Aug 2026, 03:15 UTC167 viewsread 29 August 2026

пляж Кипчак, пролет бпла в сторону предположительно Красносельское Республика Крым

29 Aug 2026, 03:15 UTC166 viewsread 29 August 2026

Черноморский район Тревога по БПЛА Республика Крым

29 Aug 2026, 02:34 UTC191 viewsread 29 August 2026

Севастополь, Балаклава Сохраняется опасность по БпЛА

29 Aug 2026, 02:28 UTC187 views1 reactionsread 29 August 2026

Новофедоровка и близлежащие, тревога по БпЛА

❤1

29 Aug 2026, 02:07 UTC186 viewsread 29 August 2026

Евпатория и близлежащие, тревога по БпЛА

29 Aug 2026, 01:22 UTC190 viewsread 29 August 2026

Суворовское и близлежащие Опасность по БПЛА Республика Крым

29 Aug 2026, 01:16 UTC181 viewsread 29 August 2026

Джанкой Опасность по БПЛА Республика Крым

29 Aug 2026, 01:07 UTC175 viewsread 29 August 2026

Евпатория Соблюдаем меры безопасности Республика Крым

29 Aug 2026, 01:01 UTC172 viewsread 29 August 2026

Армянск Красноперекопск и близлежащие Опасность по БПЛА Республика Крым

Showing the 12 most recent of 694 posts we hold for @radar_sevastopol_crimea. 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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“Радар Севастополь | Крым” (@radar_sevastopol_crimea), 9,732 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/radar_sevastopol_crimea.

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.