Telegram RegisterThe public register of Telegram
Telegram profile photo for Областной защитник

Channel

Областной защитник

@oblastdefender

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

39,630subscribers

+23,774 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-1003181174457
TypeChannel
Username@oblastdefender
DescriptionОбщий канал радаров Московской области Наш бот - @Knogin_bot ❗Выражаем огромную благодарность командам LPR , ВРВ и RDF Поддержать проект-https://pay.cloudtips.ru/p/b9c6cb0f
CreatedBetween 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/oblastdefender

Topic

National 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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
@RDFradar/1705716 Nov 2026, 05:24 UTC@oblastdefender/26989 · this entry16 Nov 2026, 05:24 UTC0.93under a minute
@RDFradar/108768 Aug 2026, 08:51 UTC@oblastdefender/13045 · this entry8 Aug 2026, 08:52 UTC0.92under a minute
@RDFradar/126583 Sept 2026, 09:23 UTC@oblastdefender/16789 · this entry3 Sept 2026, 09:23 UTC0.92under a minute
@oblastdefender/13134 · this entry9 Aug 2026, 09:55 UTC@RDFradar/109339 Aug 2026, 09:55 UTC0.88under a minute
@oblastdefender/15496 · this entry23 Aug 2026, 13:07 UTC@RDFradar/1199123 Aug 2026, 13:07 UTC0.87under a minute
@RDFradar/1582623 Oct 2026, 14:25 UTC@oblastdefender/24253 · this entry23 Oct 2026, 14:25 UTC0.87under 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
@RDFradar11 (8/8 hand-verifiable sample passed)0.89under a minute@RDFradar (11–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. 11 of the 11 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 369 comparable posts for this entry, running 6 August 2026 to 17 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_copy, last confirmed 18 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

15,85639,63027,7437 August 202617 November 2026
64 measurements spanning 102 days, net +23,774. 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 12,290–43,196 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
17 Nov 2026, 11:0139,630+631
14 Nov 2026, 02:0038,999+227
11 Nov 2026, 10:4038,772-5
9 Nov 2026, 16:5938,777+10
8 Nov 2026, 09:4138,767-22
7 Nov 2026, 00:4438,789+6
6 Nov 2026, 01:0538,783-17
3 Nov 2026, 23:0938,800+228
3 Nov 2026, 00:5738,572+169
1 Nov 2026, 22:3638,403+125
31 Oct 2026, 20:5438,278+229
30 Oct 2026, 22:1638,049+104
30 Oct 2026, 01:3637,945+247
29 Oct 2026, 01:4937,698+358
28 Oct 2026, 01:0137,340+385
26 Oct 2026, 22:3736,955+124
25 Oct 2026, 19:3636,831+119
24 Oct 2026, 20:3936,712+113
23 Oct 2026, 23:2636,599+551
23 Oct 2026, 00:1936,048first reading

Engagement

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

ERR · 30 days
19.5%
avg views ÷ 39,630 subscribers
Avg views / post
7,720
789 posts measured
Reaction rate
0.309%
reactions ÷ views · ER floor
Posts in window
789
of 2,303 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 777 of 789 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,303 (6 August 2026 – 17 November 2026)
Views total6,088,597
Reactions total18,743
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 11: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
448
Videos
365
Links
405

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. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
1m 33s
Average length
9s

Measured directly from 10 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

24,063 reactions across 957 posts, in 50 distinct kinds. The most used accounts for 43.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏10,53343.8%
❤3,96216.5%
custom 52489498410562822262,3139.61%
🤬1,3985.81%
😡8223.42%
😭6532.71%
😱4251.77%
👎3991.66%
😢3861.60%
👍3681.53%
🔥3451.43%
🤯3101.29%
😨2841.18%
🎉2481.03%
👏1740.723%
😍1480.615%
❤‍🔥1430.594%
👀1350.561%
💘1340.557%
🕊1330.553%
30 further kinds7503.12%

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 971 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 24,063 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 11 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.

Recent posts

Telegram’s own ‘edited’ marker: 33 of 789 posts held from the last 30 days (4.18%) 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, 18:52 UTC≈9,320 views236 reactionsread 18 November 2026

🟢На данный момент по обстановке тихо. Пусков БПЛА не фиксируем

❤107🙏82custom 524894984105628222638👍5👏3🔥1

17 Nov 2026, 10:43 UTC≈22,900 views98 reactionsread 18 November 2026

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

custom 524894984105628222648🙏24❤21😈2🍾1👏1😢1

17 Nov 2026, 09:27 UTC≈12,000 views36 reactionsread 18 November 2026

Источник радар ВРВ МО Истра Московская область Отбой опасности по БПЛА На территории региона опасность сохраняется

🙏25❤7❤‍🔥3👌1

17 Nov 2026, 09:17 UTC≈11,100 views15 reactionsread 18 November 2026

Источник радар RDF ✈️✅Аэропорт ВНУКОВО работает в штатном режиме Сняты введенные ограничения на использование воздушного пространства

🙏13❤1😡1

17 Nov 2026, 08:57 UTC≈10,400 views44 reactionsread 18 November 2026

На данный момент массовости не наблюдаем. Опасность по единичным фиксациям

🙏25❤12custom 52489498410562822267

17 Nov 2026, 08:43 UTC≈10,100 views14 reactionsread 18 November 2026

Источник радар RDF Можайск Уваровка и ближайшие (Можайский МО) БПЛА в вашем направлении

🙏14

17 Nov 2026, 08:31 UTC≈10,400 views33 reactionsread 18 November 2026

Источник радар RDF Можайский МО Волоколамский МО Наро-Фоминский ГО Троицкий АО ❗️Опасность по БПЛА повторно несколько БПЛА по вашему направлению

🤬23🙏9🥰1

17 Nov 2026, 08:30 UTC≈10,300 views27 reactionsread 18 November 2026

МО Истра Московская область Опасность по БПЛА Источник радар ВРВ

🤬16custom 52489498410562822266🙏5

17 Nov 2026, 08:16 UTC≈9,430 views24 reactionsread 18 November 2026

Источник радар RDF ✈️✈️Аэропорт ВНУКОВО Введены ограничения на использование воздушного пространства аэропорт принимает и отправляет рейсы по согласованию с соответствующими органами.

🤨13🙏7❤3👏1

17 Nov 2026, 05:52 UTC≈9,550 views261 reactionsread 18 November 2026

Источник радар RDF ❗️💥💪 В период с 17:00 16 ноября по 07:00 17 ноября в сторону Московского региона летели около 800 БПЛА. Большая часть из них уничтожена ВКС ПВО Минобороны на дальних рубежах. 321 беспилотник нейтрализован на подлёте к Москве. При защите города кроме сил ВКС ПВО Минобороны хорошо показали себя бойцы недавно созданного Барс Москва. За последние 2 дня ими сбито около 300 вражеских беспилотников. Молод…

custom 5248949841056282226133👍52🔥23❤22🙏15🗿6🥴6💘2

17 Nov 2026, 04:38 UTC≈9,900 views20 reactionsread 18 November 2026

МО Истра Отбой опасности по БПЛА

❤14😍5👎1

17 Nov 2026, 04:20 UTC≈8,830 views26 reactionsread 18 November 2026

Источник радар RDF ✈️✅Аэропорты ВНУКОВО, ЖУКОВСКИЙ и ДОМОДЕДОВО работают в штатном режиме Сняты введенные ограничения на использование воздушного пространства

🙏14😍7❤4👎1

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

@oblastdefender edited 2 posts 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
9 August 2026
Most recent edit
20 August 2026

Posts recorded as deleted after publishing

We recorded 2 posts on @oblastdefender as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
20 August 2026
Most recent seen missing
20 August 2026
Median time before seen missing
12 hours
Seen missing in the last 30 days
0

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

ШАТУРА РАДАР
@Shaturaradar · 7,796
100 posts
🚨Ногинск|Черноголовка|Электросталь тревоги БПЛА 🚨
@noginskbpla · 8,471
86 posts
ДОМОДЕДОВО| ПОДОЛЬСК РАДАР БПЛА
@domodedovobpla · 6,662
81 posts
ЧЕХОВ РАДАР
@Chekhovradar · 6,922
43 posts
Павловский Посад радар
@Pavlovskyposadradar · 5,887
31 posts
КОТЕЛЬНИКИ РАДАР
@Kotelnikiradar · 625
20 posts
ЛЮБЕРЦЫ РАДАР
@Lyubertsyradar · 1,100
20 posts
РЕУТОВ РАДАР
@Reutovradar · 143
20 posts
СЕРГИЕВ ПОСАД РАДАР
@SergievPosadradar · 193
20 posts
ХИМКИ/ЛОБНЯ/ДОЛГОПРУДНЫЙ РАДАР
@Khimkiradar · 1,124
19 posts
КРАСНОГОРСК РАДАР
@Krasnogorskradar · 264
19 posts
ТАЛДОМ РАДАР
@taldomradar · 44
19 posts
ВИДНОЕ РАДАР
@vidnoeradar · 167
19 posts
Балашиха/Железнодорожный радар
@Balashikharadar · 563
18 posts
ПУШКИНО РАДАР
@Pushkinoradar · 159
18 posts
РОШАЛЬ РАДАР
@Roshalradar · 180
18 posts
МЫТИЩИ/ЩЁЛКОВО РАДАР
@Mytishchiradar · 659
17 posts
ДМИТРОВ РАДАР
@Dmitrovradar · 145
16 posts
ДУБНА РАДАР
@Dubnaradar · 4,276
13 posts
КЛИН РАДАР
@Klinradar · 582
12 posts
ЛУХОВИЦЫ РАДАР
@Lukhovitsyradar · 116
11 posts
МОЖАЙСК РАДАР
@mozhayskradar · 780
11 posts
ОДИНЦОВО РАДАР
@odintsovoradar · 614
11 posts
Руза радар
@ruzaradar · 136
11 posts
ВОЛОКОЛАМСК РАДАР
@Volokolamskradarr · 216
10 posts
Воскресенск радар
@Voskresenskradar · 1,306
10 posts
ЗАРАЙСК РАДАР
@Zarayskradar · 157
10 posts
ИСТРА РАДАР
@istraradar · 2,477
10 posts
Зеленоград/Солнечногорск радар
@zelenogradradarr · 1,973
10 posts
ЕГОРЬЕВСК РАДАР
@Yegoryevskradar · 682
9 posts
ОРЕХОВО-ЗУЕВО РАДАР
@orekhovozuyevoradar · 1,829
9 posts
ТРОИЦК МОСКВА РАДАР
@troitskradar · 676
9 posts
НАРО-ФОМИНСК РАДАР
@Narofominskradar · 673
8 posts
БРОННИЦЫ РАДАР
@bronnitsyradar · 687
8 posts
РАМЕНСКОЕ/ЖУКОВСКИЙ РАДАР БПЛА
@remanskoebpla · 994
8 posts
Серпухов радар
@serpukhovradar · 1,421
8 posts
СТУПИНО|КАШИРА РАДАР
@stupinoradar · 1,225
8 posts
СЕРЕБРЯНЫЕ ПРУДЫ РАДАР
@SerebryanyePrudyradar · 35
7 posts
КОЛОМНА РАДАР
@colomnaradar · 1,579
6 posts
Жизнь Коши Юлиевой
@koshayulieva_music · 119
1 post
Ривердайджест
@riverdigest · 2,130
1 post

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 42 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

Named by

Channels on the register whose posts name this channel's handle.

ШАТУРА РАДАР
@Shaturaradar · 7,796
17 posts
🚨Ногинск|Черноголовка|Электросталь тревоги БПЛА 🚨
@noginskbpla · 8,471
13 posts
ДОМОДЕДОВО| ПОДОЛЬСК РАДАР БПЛА
@domodedovobpla · 6,662
7 posts
ЧЕХОВ РАДАР
@Chekhovradar · 6,922
6 posts
КОТЕЛЬНИКИ РАДАР
@Kotelnikiradar · 625
5 posts
КРАСНОГОРСК РАДАР
@Krasnogorskradar · 264
5 posts
Павловский Посад радар
@Pavlovskyposadradar · 5,887
5 posts
ПУШКИНО РАДАР
@Pushkinoradar · 159
5 posts
РЕУТОВ РАДАР
@Reutovradar · 143
5 posts
СЕРГИЕВ ПОСАД РАДАР
@SergievPosadradar · 193
5 posts
ТАЛДОМ РАДАР
@taldomradar · 44
5 posts
ВИДНОЕ РАДАР
@vidnoeradar · 167
5 posts
Балашиха/Железнодорожный радар
@Balashikharadar · 563
4 posts
ДМИТРОВ РАДАР
@Dmitrovradar · 145
4 posts
ХИМКИ/ЛОБНЯ/ДОЛГОПРУДНЫЙ РАДАР
@Khimkiradar · 1,124
4 posts
ЛУХОВИЦЫ РАДАР
@Lukhovitsyradar · 116
4 posts
ЛЮБЕРЦЫ РАДАР
@Lyubertsyradar · 1,100
4 posts
РОШАЛЬ РАДАР
@Roshalradar · 180
4 posts
ВОЛОКОЛАМСК РАДАР
@Volokolamskradarr · 216
4 posts
КЛИН РАДАР
@Klinradar · 582
3 posts
МОЖАЙСК РАДАР
@mozhayskradar · 780
3 posts
МЫТИЩИ/ЩЁЛКОВО РАДАР
@Mytishchiradar · 659
3 posts
Руза радар
@ruzaradar · 136
3 posts
Зеленоград/Солнечногорск радар
@zelenogradradarr · 1,973
3 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 17 November 2026 — this entry's latest reading, not the date you are reading this.

“Областной защитник” (@oblastdefender), 39,630 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/oblastdefender.

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.