Telegram RegisterThe public register of Telegram
Telegram profile photo for RDS-prostir

Channel

RDS-prostir

@rdsprostir

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Polls · Citations · Telegram's recommendations · Cite this entry

48,305subscribers

+1,078 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001956362666
TypeChannel
Username@rdsprostir
DescriptionКанал з актуальною безпековою ситуацією по загрозам з неба https://base.monobank.ua/DowXyjyUDSsPFo
Created24 May 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/rdsprostir

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 56% 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

47,22748,70147,96448,3056 August 202610 November 2026
65 measurements spanning 97 days, net +1,078. 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 47,006–48,922 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
10 Nov 2026, 17:1048,305-3
9 Nov 2026, 02:3948,308+6
7 Nov 2026, 21:1848,302-6
6 Nov 2026, 22:5648,308+4
5 Nov 2026, 21:2648,304-22
4 Nov 2026, 20:2048,326-22
3 Nov 2026, 22:3648,348-25
3 Nov 2026, 00:5748,373-20
2 Nov 2026, 00:5048,393+18
1 Nov 2026, 02:5948,375+65
31 Oct 2026, 02:5648,310+12
30 Oct 2026, 05:3048,298-19
29 Oct 2026, 03:2948,317-21
28 Oct 2026, 00:0148,338-7
26 Oct 2026, 23:3748,345-10
25 Oct 2026, 22:3448,355-29
24 Oct 2026, 20:4848,384-33
23 Oct 2026, 22:2548,417-12
22 Oct 2026, 23:0748,429-12
21 Oct 2026, 22:5548,441first reading

Engagement

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

ERR · 30 days
11.8%
avg views ÷ 48,305 subscribers
Avg views / post
5,680
1,176 posts measured
Reaction rate
2.04%
reactions ÷ views · ER floor
Posts in window
1,176
of 3,715 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 1,171 of 1,176 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 10 November 2026
Posts held3,715 (5 August 2026 – 10 November 2026)
Views total6,681,957
Reactions total136,283
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 01:39 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
≈2,010
Videos
≈971
Links
≈1,680

Lifetime counters from Telegram’s own channel header, read 11 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
1m 30s
Average length
18s

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

116,300 reactions across 994 posts, in 46 distinct kinds. The most used accounts for 65.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏76,21565.5%
🤬18,67216.1%
❤12,98611.2%
💯1,2281.06%
😢1,1781.01%
👍1,0310.887%
😡9600.825%
😁8590.739%
❤‍🔥6380.549%
🔥5560.478%
🥰3460.298%
👎3250.279%
🤯2000.172%
😭1700.146%
😱1350.116%
👀1060.091%
🤝960.083%
🤔940.081%
🫡830.071%
😍790.068%
26 further kinds3430.295%

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 996 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 116,300 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 16 October 2026 to 10 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.

Telegram Stars

Stars received
27
across the posts below
Posts paid on
17
of 1,000 we hold a reading for · 2%
Most on one post
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @rdsprostir. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 16 October 2026 to 10 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

Telegram’s own ‘edited’ marker: 162 of 1,176 posts held from the last 30 days (13.8%) 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).

10 Nov 2026, 21:26 UTC≈2,690 views118 reactionsread 11 November 2026

Любі , тихої ночі Мушу вас залишити

❤68🙏45🏆3❤‍🔥1🫡1

10 Nov 2026, 21:17 UTC≈3,070 views77 reactionsread 11 November 2026

Повітряна тривога

🙏52🤬25

10 Nov 2026, 21:03 UTC≈3,360 views70 reactionsread 11 November 2026

Суми відбій повітряної тривоги

🙏63❤6👍1

10 Nov 2026, 20:57 UTC≈3,690 views94 reactionsread 11 November 2026

Суми можлива поява fpv на оптоволокні

🙏66🤬25😡3

10 Nov 2026, 20:40 UTC≈4,390 views132 reactionsread 11 November 2026

Загроза балістики

🙏99🤬32❤1

10 Nov 2026, 20:40 UTC≈4,360 views94 reactionsread 11 November 2026

Повітряна тривога

🙏73🤬21

10 Nov 2026, 19:43 UTC≈5,900 views101 reactionsread 11 November 2026

Відбій повітряної тривоги

🙏92❤4👍4❤‍🔥1

10 Nov 2026, 19:40 UTC≈5,950 views85 reactionsread 11 November 2026

Відбій загрози балістики

🙏79👍6

10 Nov 2026, 19:32 UTC≈6,930 views94 reactionsread 11 November 2026

Недригайлів > Липова Долина реактивний UPD: далі Полтавщина

🙏77🤬12❤‍🔥3😡2

10 Nov 2026, 19:26 UTC≈6,950 views111 reactionsread 11 November 2026

Далі Недригайлів

🙏84🤬27

10 Nov 2026, 19:23 UTC≈7,490 views95 reactionsread 11 November 2026

Буринь > Біжівка реактивний

🙏73🤬22

Showing the 12 most recent of 3,715 posts we hold for @rdsprostir. 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

@rdsprostir edited 1 post 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
8 August 2026
Most recent edit
8 August 2026

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

30 Oct 2026, 11:32 UTCAnonymous Poll138 voters

Як для вас зручно підтримувати роботу каналу ?

  1. Монобаза20%
  2. Банка на каву58%
  3. PayPal7%
  4. Нащо надо, не цікаво21%

The shares total 106%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 1,000 most recent posts we hold (the sample is capped at 1,000), published 16 October 2026 to 10 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

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 3 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.

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

SUMYLIKE TG
@sumyliketop · 161,492
#1
Женьок Вещає…
@ZhenyokSay · 157,836
#2
Sumyregion △
@sumyregion · 192,200
#3
Сумська Хунта 🏴
@sumskahunta · 5,831
#4
🇺🇦Олексій Дрозденко
@drozdenko_sumy · 2,833
#5
Сумська міська рада
@sumskamiskarada · 8,171
#6
СУМИ / SUMY GO ∆
@sumygo · 193,081
#7
Авіа Моніторинг
@avia_monitoring · 850
#8
News Sumy🇺🇦
@news_sumy24 · 70,090
#9
СУМЩИНА 🇺🇦
@sumy_novyny · 26,682
#10
Поліція Cумської області🇺🇦
@police_su_region · 4,486
#11
Небо Спротиву
@NeboSportyvu · 1,909
#12
Повітряні Сили ЗС України / Air Force of the Armed Forces of Ukraine
@kpszsu · 939,552
#13
Сумська обласна військова адміністрація
@Sumy_news_ODA · 27,084
#14
Сіверські Націоналісти𓃟
@pivnichmmedia · 14,227
#15
Суспільне Суми
@suspilnesumy · 140,369
#16
Прокуратура Сумщини
@prokuraturasumy · 1,319
#17
⚡️Resident ППО ⚡️
@residenttsss · 13,691 (as read 4 September 2026)
#18
Кордон.Медіа
@kordonmedia · 45,106
#19
ДСНС Сумщини
@dsns_sumy · 5,592
#20
Здрасьте, приїхали!!!💬
@dkskdowoqpjjjjm · 20,025
#21
🔊⚠️єРадар | Повітряна тривога | Ракетна небезпека
@eRadarrua · 411,089
#22
MonitorZagroz / Моніторинг 24/7
@UkraineMonitorZagroz · 4,672
#23
monitor
@war_monitor · 959,922
#24
🇺🇦Новини міста Суми🇺🇦
@sumy_2022_ua · 25,317
#25
Сумы | Суми
@sumy_sumy1 · 86,347
#26
Лачен пише
@lachentyt · 1,579,508
#27
117 окрема бригада ТрО ЗСУ
@trozsusumy117 · 1,340
#28
❗️Тривога. Сумська область
@surenasumy · 85,891
#29
Тривога Старкон !!!!
@grup223m · 35,614
#30
Повітряний простір України 🇺🇦
@monikppy · 229,138
#31
Карта повітряних тривог ‼️ Вибухи ‼️ Ракети ‼️
@povitryanatrivogaaa · 729,798
#32
Патрульна поліція Сумської області
@patrolpolicesumy · 1,793
#33
Бойова Україна — monitoring
@RadaUaxRn · 1,477
#34
TLk News
@tlknewsua · 640,447
#35
Данкор | Суми UA
@dancorsumyua · 2,684
#36
💼 Сумка Лисенка
@Lysenko_bag · 4,226
#37
Дивізіон-«ТІВАЗ»
@tivaz_artillery · 41,309
#38
УСЕ ПРО ВСЕ ВІДРАЗУ: КИЇВЩИНА , ПОЛТАВЩИНА
@useprovse1 · 31,730
#39
SUMYLIKE TG для дорослих😁😏
@sumylike18 · 8,765
#40
Сумські Дебати
@debaty_sumy_ua · 3,811
#41
Тотальна Зрада
@totallzrada · 266,865
#42
STERNENKO
@ssternenko · 880,350
#43
ППО Полтавщина: Нічні мисливці
@ppo_Poltava · 34,263
#44
Північний Сич 🦉
@Northern_Sich_ukr · 109,159
#45
Sumy Region News
@sumyregion_news · 16,561
#46
Білопілля INFO
@bilopillya_info · 7,751
#47
Ринда моніторить
@kudy_letyt · 158,861
#48
ППО радар | Напрямок ракет | Напрямок шахедів |
@mon1tor_ua · 264,254
#49
monitorwar
@monitoringwar · 26,432
#50
✈️Стратегічна авіація
@StrategicaviationT · 132,792
#51
Білопілля 🎄 Ворожба ❄️ Район 🎅 Прикордоння
@myblp · 6,742
#52
✙DeepState✙🇺🇦
@deepstateua · 751,881
#53
0542.ua
@sumy0542 · 10,323
#54
ЧЕРНІГІВ 🔥 АНОНІМНО
@CHERNIHIV_ANONIMNO · 266
#55
ОПЕРАТИВНИЙ ІНФОРМ
@operinform · 135,988
#56
Глухів (важливо)
@glukhovalarm · 6,272
#57
△ Конотоп LIVE 🔴 Сумщина
@konotop_live · 49,183
#58
Олександр ЛИСЕНКО / Сумський міський голова
@golova_lysenko · 2,984
#59
Bilopillia.City
@bilopilliaCity · 1,653
#60
Avia OM | monitoring
@aviaOM · 266
#61
Я военный корреспондент (ЯВК)
@war_korrespondent · 768
#62
Tracking
@the_first_online · 8,077
#63
AviMonitor
@avimonitor · 2,946
#64
Бавовна
@ukrbavovna · 802,218
#65
Сирени Сумщини (тривога)
@sumyalarmnotifications · 1,953
#66
Суми_діско_партизани
@sumyduscopartizanu · 1,669
#67
Сумський гідрометцентр 🌍☀️
@sumy_hmc · 3,140
#68
Управление Z 🇷🇺
@control_sigma · 31,385
#69
Оренда квартир у місті Суми
@sumy_rent · 2,545
#70
Оренда квартир. Суми. АН "Прем'єр"
@premiersumy · 5,557
#71
Робота у Сумах — Work.ua
@workua_sumy · 1,034
#72
Робота / SUMY GO
@sumygowork · 5,776
#73

Read from Telegram’s recommendation API, most recently 4 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

ППО Полтавщина: Нічні мисливці
@ppo_Poltava · 34,263
Telegram ranks this channel #16 of 71 here — alongside 70 others — read 4 September 2026
Тривога Старкон !!!!
@grup223m · 35,614
Telegram ranks this channel #17 of 75 here — alongside 74 others — read 10 September 2026
Молниеносные новости 🗞️
@Rostov_Krasnodar1 · 23,947
Telegram ranks this channel #18 of 39 here — alongside 38 others — read 22 September 2026
Здрасьте, приїхали!!!💬
@dkskdowoqpjjjjm · 20,025
Telegram ranks this channel #48 of 82 here — alongside 81 others — read 24 September 2026
СУМЩИНА 🇺🇦
@sumy_novyny · 26,682
Telegram ranks this channel #53 of 84 here — alongside 83 others — read 10 September 2026

This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“RDS-prostir” (@rdsprostir), 48,305 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/rdsprostir.

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.