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

Channel

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

@oblastdefender

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

29,516subscribers

+13,660 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-1003181174457
TypeChannel
Username@oblastdefender
DescriptionОбщий канал радаров Московской области Наш бот - @Knogin_bot ❗Выражаем огромную благодарность командам LPR , ВРВ и RDF Поддержать проект-https://pay.cloudtips.ru/p/b9c6cb0f
CreatedBetween 1 September 2025 and 31 December 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live4 October 2026
Measurements held34
Confirmed unchanged1 time, most recently 4 October 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 why it has no browse page of its own yet.

Growth

15,85629,51622,6867 August 2026 — 15,856 subscribers8 August 2026 — 16,052 subscribers9 August 2026 — 16,168 subscribers10 August 2026 — 16,241 subscribers11 August 2026 — 16,404 subscribers12 August 2026 — 16,426 subscribers13 August 2026 — 16,444 subscribers14 August 2026 — 16,466 subscribers16 August 2026 — 17,188 subscribers17 August 2026 — 17,869 subscribers18 August 2026 — 20,551 subscribers19 August 2026 — 21,529 subscribers20 August 2026 — 21,956 subscribers21 August 2026 — 22,179 subscribers23 August 2026 — 22,564 subscribers24 August 2026 — 22,873 subscribers25 August 2026 — 22,903 subscribers26 August 2026 — 23,215 subscribers28 August 2026 — 23,229 subscribers29 August 2026 — 23,288 subscribers30 August 2026 — 23,412 subscribers31 August 2026 — 23,451 subscribers1 September 2026 — 23,522 subscribers2 September 2026 — 23,645 subscribers3 September 2026 — 25,068 subscribers5 September 2026 — 25,500 subscribers8 September 2026 — 25,707 subscribers11 September 2026 — 25,907 subscribers13 September 2026 — 25,990 subscribers14 September 2026 — 25,989 subscribers16 September 2026 — 25,972 subscribers19 September 2026 — 26,941 subscribers25 September 2026 — 29,231 subscribers4 October 2026 — 29,516 subscribers7 August 20264 October 2026
34 measurements spanning 58 days, net +13,660. 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 13,807–31,565 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
4 Oct 2026, 09:4129,516+285
25 Sept 2026, 23:0029,231+2,290
19 Sept 2026, 04:5626,941+969
16 Sept 2026, 16:0025,972-17
14 Sept 2026, 19:1925,989-1
13 Sept 2026, 08:2125,990+83
11 Sept 2026, 08:1825,907+200
8 Sept 2026, 10:5925,707+207
5 Sept 2026, 03:4125,500+432
3 Sept 2026, 09:5325,068+1,423
2 Sept 2026, 07:1723,645+123
1 Sept 2026, 05:5423,522+71
31 Aug 2026, 09:0723,451+39
30 Aug 2026, 06:2423,412+124
29 Aug 2026, 03:2523,288+59
28 Aug 2026, 00:5223,229+14
26 Aug 2026, 21:4723,215+312
25 Aug 2026, 18:4322,903+30
24 Aug 2026, 21:3522,873+309
23 Aug 2026, 07:0322,564first reading

Engagement

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

ERR · 30 days
19.6%
avg views ÷ 29,516 subscribers
Avg views / post
5,790
263 posts measured
Reaction rate
0.439%
reactions ÷ views · ER floor
Posts in window
263
of 1,075 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 256 of 263 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 4 October 2026
Posts held1,075 (6 August 2026 – 4 October 2026)
Views total1,522,301
Reactions total6,650
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken4 Oct 2026, 11:34 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
356
Videos
311
Links
320

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

Video runtime
2m 35s
Average length
10s

Measured directly from 15 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,035 reactions across 962 posts, in 62 distinct kinds. The most used accounts for 43.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏10,37843.2%
❤4,11417.1%
🤬2,52810.5%
😭8613.58%
😱7853.27%
👍6302.62%
custom 52489498410562822266242.60%
😢6172.57%
😡4251.77%
🔥3551.48%
👎3021.26%
🎉2981.24%
👏2721.13%
🤯2561.07%
🕊1880.782%
❤‍🔥1870.778%
💔1240.516%
🍌1230.512%
💘1140.474%
🤔1050.437%
42 further kinds7493.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 969 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,035 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 8 August 2026 to 4 October 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

4 Oct 2026, 11:20 UTC≈1,210 views10 reactionsread 4 October 2026

Истра МО Рузский МО Волоколамский МО Одинцовский ГО Можайский МО Соблюдаем меры безопасности. Еще фиксации в вашем направлении

🙏7🤬3

4 Oct 2026, 11:19 UTC≈1,210 views10 reactionsread 4 October 2026

Источник радар RDF 💥На территории региона ведется работа по уничтожению реактивных БПЛА Меры предосторожности

🙏10

4 Oct 2026, 11:17 UTC≈1,390 views5 reactionsread 4 October 2026

Источник радар RDF Наро-Фоминский ГО ГО Одинцово Троицкий АО меры предосторожности

🙏3😡2

4 Oct 2026, 11:17 UTC≈1,390 views6 reactionsread 4 October 2026

МО Истра 💥Работа ПВО по БПЛА

🙏3😭2😡1

4 Oct 2026, 11:16 UTC≈1,500 views8 reactionsread 4 October 2026

Источник радар RDF Волоколамский МО Рузский МО 💥Работа ПВО по БПЛА

🙏6👎1😡1

4 Oct 2026, 11:16 UTC≈1,550 views8 reactionsread 4 October 2026

Клин ГО Солнечногорский район Зеленоград Внимание по БПЛА

🙏6😡2

4 Oct 2026, 11:15 UTC≈1,390 views5 reactionsread 4 October 2026

Источник радар RDF Западная часть Московская область Еще пролеты БПЛА Меры предосторожности

🤬4🙏1

4 Oct 2026, 11:13 UTC≈1,570 views8 reactionsread 4 October 2026

Источник радар ВРВ Кубинка Московская область Меры безопасности

🤩3👎2🙏2😡1

4 Oct 2026, 11:11 UTC≈1,820 views7 reactionsread 4 October 2026

Источник радар RDF Волоколамский МО 💥Работа ПВО по БПЛА

🙏7

4 Oct 2026, 11:10 UTC≈1,950 views10 reactionsread 4 October 2026

Источник радар RDF ГО Одинцово 💥Работа ПВО по БПЛА

🙏6custom 52489498410562822263🤩1

4 Oct 2026, 11:08 UTC≈1,750 views10 reactionsread 4 October 2026

МО Руза 💥Работа ПВО по БПЛА

🙏8custom 52489498410562822262

4 Oct 2026, 11:06 UTC≈1,880 views12 reactionsread 4 October 2026

Источник радар RDF МО Истра 💥Работа ПВО по БПЛА

🙏12

Showing the 12 most recent of 1,075 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

Forward network

Republished by

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

КОТЕЛЬНИКИ РАДАР
@Kotelnikiradar · 455
20 posts
ЛЮБЕРЦЫ РАДАР
@Lyubertsyradar · 774
20 posts
РЕУТОВ РАДАР
@Reutovradar · 55
20 posts
СЕРГИЕВ ПОСАД РАДАР
@SergievPosadradar · 164
20 posts
ШАТУРА РАДАР
@Shaturaradar · 7,616
20 posts
ХИМКИ/ЛОБНЯ/ДОЛГОПРУДНЫЙ РАДАР
@Khimkiradar · 835
19 posts
КРАСНОГОРСК РАДАР
@Krasnogorskradar · 216
19 posts
ТАЛДОМ РАДАР
@taldomradar · 29
19 posts
ВИДНОЕ РАДАР
@vidnoeradar · 114
19 posts
Балашиха/Железнодорожный радар
@Balashikharadar · 404
18 posts
ПУШКИНО РАДАР
@Pushkinoradar · 87
18 posts
РОШАЛЬ РАДАР
@Roshalradar · 180
18 posts
МЫТИЩИ/ЩЁЛКОВО РАДАР
@Mytishchiradar · 519
17 posts
ДМИТРОВ РАДАР
@Dmitrovradar · 49
16 posts
ДУБНА РАДАР
@Dubnaradar · 3,148
13 posts
КЛИН РАДАР
@Klinradar · 397
12 posts
Павловский Посад радар
@Pavlovskyposadradar · 5,355
12 posts
🚨Ногинск|Черноголовка|Электросталь тревоги БПЛА 🚨
@noginskbpla · 8,063
12 posts
ЛУХОВИЦЫ РАДАР
@Lukhovitsyradar · 97
11 posts
МОЖАЙСК РАДАР
@mozhayskradar · 400
11 posts
ОДИНЦОВО РАДАР
@odintsovoradar · 436
11 posts
Руза радар
@ruzaradar · 59
11 posts
ВОЛОКОЛАМСК РАДАР
@Volokolamskradarr · 121
10 posts
Воскресенск радар
@Voskresenskradar · 1,100
10 posts
ЗАРАЙСК РАДАР
@Zarayskradar · 143
10 posts
ИСТРА РАДАР
@istraradar · 1,327
10 posts
Зеленоград/Солнечногорск радар
@zelenogradradarr · 1,185
10 posts
ЕГОРЬЕВСК РАДАР
@Yegoryevskradar · 677
9 posts
ОРЕХОВО-ЗУЕВО РАДАР
@orekhovozuyevoradar · 1,736
9 posts
ТРОИЦК МОСКВА РАДАР
@troitskradar · 298
9 posts
НАРО-ФОМИНСК РАДАР
@Narofominskradar · 405
8 posts
БРОННИЦЫ РАДАР
@bronnitsyradar · 553
8 posts
РАМЕНСКОЕ/ЖУКОВСКИЙ РАДАР БПЛА
@remanskoebpla · 885
8 posts
Серпухов радар
@serpukhovradar · 941
8 posts
СТУПИНО|КАШИРА РАДАР
@stupinoradar · 1,178
8 posts
СЕРЕБРЯНЫЕ ПРУДЫ РАДАР
@SerebryanyePrudyradar · 28
7 posts
КОЛОМНА РАДАР
@colomnaradar · 1,245
6 posts
ДОМОДЕДОВО| ПОДОЛЬСК РАДАР БПЛА
@domodedovobpla · 4,946
4 posts
ЧЕХОВ РАДАР
@Chekhovradar · 5,731
3 posts
Жизнь Коши Юлиевой
@koshayulieva_music · 117
1 post
Ривердайджест
@riverdigest · 2,019
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 39 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.

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

“Областной защитник” (@oblastdefender), 29,516 subscribers as measured 4 October 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.