Telegram RegisterThe public register of Telegram
Telegram profile photo for "Радар Жуковский"

Channel

"Радар Жуковский"

@radarzhukovsky

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

41,253subscribers

-1,187 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-1002373628352
TypeChannel
Username@radarzhukovsky
Description📡 Канал создан для оперативного информирования жителей городского округа Жуковский о случаях возникновения угроз различного характера. 🔔 Включите обязательно уведомления, чтобы получать точную и оперативную информацию
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live22 October 2026
Measurements held47
Confirmed unchanged1 time, most recently 22 October 2026
On Telegramt.me/radarzhukovsky

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

41,25342,44041,846.57 August 2026 — 42,440 subscribers7 August 2026 — 42,440 subscribers7 August 2026 — 42,434 subscribers8 August 2026 — 42,420 subscribers9 August 2026 — 42,402 subscribers10 August 2026 — 42,386 subscribers12 August 2026 — 42,374 subscribers12 August 2026 — 42,349 subscribers14 August 2026 — 42,332 subscribers16 August 2026 — 42,305 subscribers17 August 2026 — 42,286 subscribers18 August 2026 — 42,250 subscribers19 August 2026 — 42,228 subscribers20 August 2026 — 42,213 subscribers21 August 2026 — 42,200 subscribers22 August 2026 — 42,191 subscribers24 August 2026 — 42,167 subscribers25 August 2026 — 42,156 subscribers26 August 2026 — 42,141 subscribers27 August 2026 — 42,123 subscribers28 August 2026 — 42,112 subscribers29 August 2026 — 42,097 subscribers30 August 2026 — 42,093 subscribers31 August 2026 — 42,080 subscribers1 September 2026 — 42,060 subscribers2 September 2026 — 42,045 subscribers3 September 2026 — 42,032 subscribers5 September 2026 — 41,994 subscribers9 September 2026 — 41,954 subscribers11 September 2026 — 41,924 subscribers13 September 2026 — 41,900 subscribers15 September 2026 — 41,885 subscribers17 September 2026 — 41,859 subscribers19 September 2026 — 41,823 subscribers26 September 2026 — 41,640 subscribers4 October 2026 — 41,531 subscribers9 October 2026 — 41,462 subscribers13 October 2026 — 41,409 subscribers14 October 2026 — 41,393 subscribers15 October 2026 — 41,379 subscribers16 October 2026 — 41,348 subscribers17 October 2026 — 41,330 subscribers18 October 2026 — 41,309 subscribers19 October 2026 — 41,296 subscribers20 October 2026 — 41,290 subscribers21 October 2026 — 41,275 subscribers22 October 2026 — 41,253 subscribers7 August 202622 October 2026
47 measurements spanning 76 days, net -1,187. 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 41,075–42,618 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 47
Measured (UTC)SubscribersChange
22 Oct 2026, 21:5741,253-22
21 Oct 2026, 17:1641,275-15
20 Oct 2026, 13:4641,290-6
19 Oct 2026, 14:1041,296-13
18 Oct 2026, 15:5941,309-21
17 Oct 2026, 16:4041,330-18
16 Oct 2026, 15:4041,348-31
15 Oct 2026, 18:4741,379-14
14 Oct 2026, 17:5041,393-16
13 Oct 2026, 10:3041,409-53
9 Oct 2026, 06:0041,462-69
4 Oct 2026, 17:3941,531-109
26 Sept 2026, 17:4041,640-183
19 Sept 2026, 15:4041,823-36
17 Sept 2026, 06:5841,859-26
15 Sept 2026, 05:3941,885-15
13 Sept 2026, 11:5841,900-24
11 Sept 2026, 17:4041,924-30
9 Sept 2026, 04:4141,954-40
5 Sept 2026, 23:1841,994first reading

Engagement

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

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 25 March 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
26

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

Reaction mix

4,349 reactions across 20 posts, in 8 distinct kinds. The most used accounts for 74.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏3,22874.2%
🫡3137.20%
🤔2646.07%
👍2395.50%
❤‍🔥1473.38%
🤝952.18%
🔥410.943%
👏220.506%

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

Measured over the 20 most recent posts we hold, published 22 February 2026 to 25 March 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

25 Mar 2026, 10:03 UTC≈77,400 views243 reactionsread 23 October 2026

В 12-45 временные введены ограничения на приём и вылет воздушных судов в аэропорту "Жуковский" .

🙏170🤔32🫡19🤝11❤‍🔥7🔥3👏1

16 Mar 2026, 07:50 UTC≈100,000 views219 reactionsread 23 October 2026

В 10-50 временные ограничения на приём и вылет воздушных судов в аэропорту "Жуковский" сняты.

🙏154👍28🫡17🤝7🤔6❤‍🔥4🔥3

16 Mar 2026, 06:43 UTC≈102,000 views180 reactionsread 23 October 2026

В 09-30 введены временные ограничения на приём и вылет воздушных судов в аэропорту "Жуковский".

🙏132🫡18🤔12🤝9👍5❤‍🔥4

16 Mar 2026, 05:54 UTC≈99,500 views173 reactionsread 23 October 2026

В 08-40 временные ограничения на приём и вылет воздушных судов в аэропорту "Жуковский" сняты.

🙏122🫡15👍13❤‍🔥10🤔7🤝4🔥2

16 Mar 2026, 04:12 UTC≈84,400 views207 reactionsread 23 October 2026

В 06-50 введены временные ограничения на приём и вылет воздушных судов в аэропорту "Жуковский".

🙏153🤔16🫡13🤝9❤‍🔥8👍8

15 Mar 2026, 08:28 UTC≈68,800 views199 reactionsread 23 October 2026

В11-23 временные ограничения на приём и вылет воздушных судов в аэропорту "Жуковский" сняты.

🙏149👍20🫡17❤‍🔥8🤔5

15 Mar 2026, 07:20 UTC≈64,600 views181 reactionsread 23 October 2026

В10-17 введены временные ограничения на приём и вылет воздушных судов в аэропорту "Жуковский".

🙏140🤔20🫡16❤‍🔥4🔥1

14 Mar 2026, 15:49 UTC≈62,200 views201 reactionsread 23 October 2026

В 18:40 сняты временные ограничения на прием и вылет воздушных судов в аэропорту "Жуковский".

🙏162🫡16🤔9👍5🔥5❤‍🔥4

14 Mar 2026, 15:17 UTC≈55,800 views183 reactionsread 23 October 2026

В17:46 введены временные ограничения на приём и вылет воздушных судов в аэропорту "Жуковский".

🙏133🫡24🤔13❤‍🔥5👍4👏4

14 Mar 2026, 13:14 UTC≈50,600 views191 reactionsread 23 October 2026

В 16:10 сняты временные ограничения на прием и вылет воздушных судов в аэропорту "Жуковский".

🙏154❤‍🔥12🫡11🤔8👍6

14 Mar 2026, 11:22 UTC≈44,700 views253 reactionsread 23 October 2026

В14:15 введены временные ограничения на приём и вылет воздушных судов в аэропорту "Жуковский".

🙏206🤔28🫡12❤‍🔥5👍2

8 Mar 2026, 18:41 UTC≈62,600 views210 reactionsread 23 October 2026

В 21:29 сняты временные ограничения на прием и вылет воздушных судов в аэропорту "Жуковский".

🙏168🫡17👍14🤔6❤‍🔥5

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

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

“"Радар Жуковский"” (@radarzhukovsky), 41,253 subscribers as measured 22 October 2026. Telegram Register, tgregister.com/channel/radarzhukovsky.

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.