Telegram RegisterThe public register of Telegram
Telegram profile photo for ЧЕХОВ РАДАР

Channel

ЧЕХОВ РАДАР

@Chekhovradar

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

6,922subscribers

+4,465 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002960602569
TypeChannel
Username@Chekhovradar
DescriptionКанал для оповещений об опасности БПЛА Прислать сообщение @Knogin_bot Основной канал https://t.me/oblastdefender Поддержать канал-https://pay.cloudtips.ru/p/b9c6cb0f
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 live14 November 2026
Measurements held25
Confirmed unchanged2 times, most recently 14 November 2026
On Telegramt.me/Chekhovradar

Topic

Local community — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 72% 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.

Growth

2,4576,9344,695.57 August 2026 — 2,457 subscribers8 August 2026 — 2,487 subscribers12 August 2026 — 2,723 subscribers15 August 2026 — 2,773 subscribers17 August 2026 — 3,325 subscribers21 August 2026 — 3,819 subscribers24 August 2026 — 3,959 subscribers27 August 2026 — 3,988 subscribers31 August 2026 — 4,009 subscribers2 September 2026 — 4,029 subscribers7 September 2026 — 4,203 subscribers12 September 2026 — 4,205 subscribers15 September 2026 — 4,206 subscribers28 September 2026 — 5,731 subscribers5 October 2026 — 5,770 subscribers12 October 2026 — 5,999 subscribers16 October 2026 — 6,372 subscribers18 October 2026 — 6,604 subscribers21 October 2026 — 6,609 subscribers25 October 2026 — 6,769 subscribers27 October 2026 — 6,837 subscribers30 October 2026 — 6,910 subscribers2 November 2026 — 6,928 subscribers6 November 2026 — 6,934 subscribers9 November 2026 — 6,922 subscribers6,9227 August 20269 November 2026
25 measurements spanning 94 days, net +4,465. 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 1,785–7,606 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 25
Measured (UTC)SubscribersChange
9 Nov 2026, 23:216,922-12
6 Nov 2026, 05:506,934+6
2 Nov 2026, 23:556,928+18
30 Oct 2026, 19:476,910+73
27 Oct 2026, 23:206,837+68
25 Oct 2026, 01:176,769+160
21 Oct 2026, 21:486,609+5
18 Oct 2026, 22:486,604+232
16 Oct 2026, 02:476,372+373
12 Oct 2026, 16:365,999+229
5 Oct 2026, 23:015,770+39
28 Sept 2026, 21:365,731+1,525
15 Sept 2026, 18:584,206+1
12 Sept 2026, 02:384,205+2
7 Sept 2026, 09:184,203+174
2 Sept 2026, 23:264,029+20
31 Aug 2026, 00:174,009+21
27 Aug 2026, 21:353,988+29
24 Aug 2026, 18:163,959+140
21 Aug 2026, 02:543,819first reading

Engagement

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

ERR · 30 days
29.0%
avg views ÷ 6,922 subscribers
Avg views / post
2,010
148 posts measured
Reaction rate
0.276%
reactions ÷ views · ER floor
Posts in window
148
of 168 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 123 of 148 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 held168 (5 August 2026 – 17 November 2026)
Views total297,315
Reactions total688
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 03:48 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
≈167
Videos
≈156
Links
≈1,110

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

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

910 reactions across 134 posts, in 35 distinct kinds. The most used accounts for 43.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏39343.2%
❤14616.0%
👎717.80%
😢515.60%
😭384.18%
😱363.96%
👍272.97%
🤯192.09%
🔥131.43%
🤬111.21%
💘101.10%
💔90.989%
🤡90.989%
💯80.879%
🍌70.769%
💩70.769%
🙈70.769%
👀60.659%
👏60.659%
👌40.44%
15 further kinds323.52%

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

Measured over the 168 most recent posts we hold, published 5 August 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.

Recent posts

Telegram’s own ‘edited’ marker: 2 of 148 posts held from the last 30 days (1.35%) 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, 10:43 UTC≈1,450 views5 reactionsread 18 November 2026

🟢Московская область-отбой опасности по БПЛА

❤4🙏1

17 Nov 2026, 00:42 UTC≈2,390 views6 reactionsread 18 November 2026

МО Чехов 💥Работа ПВО по БПЛА

🙏6

16 Nov 2026, 23:57 UTC≈2,450 views0 reactionsread 18 November 2026

МО Чехов 💥Работа ПВО по БПЛА

16 Nov 2026, 23:52 UTC≈2,450 views6 reactionsread 18 November 2026

МО Чехов Готовимся к сбитию

🙏5❤1

16 Nov 2026, 23:49 UTC≈2,430 views6 reactionsread 18 November 2026

МО Чехов БПЛА в небе низко!

🙏5👏1

16 Nov 2026, 23:48 UTC≈2,290 viewsread 18 November 2026

МО Чехов 💥Работа ПВО по БПЛА

16 Nov 2026, 23:43 UTC≈2,160 views6 reactionsread 18 November 2026

МО Чехов 💥Продолжается работа ПВО по БПЛА Меры безопасности

🍌4❤2

16 Nov 2026, 23:43 UTC≈1,950 views6 reactionsread 18 November 2026

МО Чехов Готовимся к сбитию

🍌3🔥2👀1

16 Nov 2026, 23:40 UTC≈1,840 views4 reactionsread 18 November 2026

МО Чехов 💥Работа ПВО по БПЛА

❤2🥱2

16 Nov 2026, 23:38 UTC≈1,760 views2 reactionsread 18 November 2026

Источник радар RDF Троицкий АО/Троицк Наро-Фоминский ГО МО Чехов ГО Подольск 💥идет активная работа ПВО по вашему направлению

👏2

16 Nov 2026, 23:33 UTC≈1,260 views0 reactionsread 18 November 2026

МО Чехов 💥Работа ПВО по БПЛА

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

Republishes

Channels on the register whose posts this channel has forwarded.

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

Names

Channels on the register whose handles appear in this channel's posts.

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

“ЧЕХОВ РАДАР” (@Chekhovradar), 6,922 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/Chekhovradar.

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.