Telegram RegisterThe public register of Telegram
Telegram profile photo for РИА Мелитополь | Оповещения

Channel

РИА Мелитополь | Оповещения

@riamelitopol_sos

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

4,393subscribers

-22 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002228532331
TypeChannel
Username@riamelitopol_sos
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live17 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/riamelitopol_sos

Topic

National news — 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 11 August 2026 and assigned it the closest of 31 fixed categories, at 87% 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

4,3934,4154,4046 August 2026 — 4,415 subscribers7 August 2026 — 4,411 subscribers10 August 2026 — 4,404 subscribers13 August 2026 — 4,397 subscribers17 August 2026 — 4,393 subscribers6 August 202617 August 2026
5 measurements spanning 11 days, net -22. 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 4,390–4,418 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 10:234,393-4
13 Aug 2026, 14:084,397-7
10 Aug 2026, 17:264,404-7
7 Aug 2026, 21:234,411-4
6 Aug 2026, 22:024,415first reading

Engagement

20 posts held, back to 7 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 6 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
74.3%
avg views ÷ 4,393 subscribers
Avg views / post
3,260
6 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
6
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 August 2026
Posts held20 (7 July 20263 August 2026)
Views total19,580
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 18:16 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.

Recent posts

3 Aug 2026, 19:34 UTC≈1,700 viewsread 8 August 2026
Photo

❗️❗️❗️Почему нельзя снимать работу ПВО и атаки БПЛА В Запорожской области запрещено снимать и распространять кадры беспилотников, работы ПВО и РЭБ, мест падения обломков и последствий атак. Даже короткое видео может содержать важные данные: время съёмки, направление движения, характерные здания, линии электропередачи, вывески, вспышки и звуки. При сопоставлении с картами и другими публикациями эти сведения могут по

3 Aug 2026, 19:31 UTC≈1,650 viewsread 8 August 2026

Мелитополь тревога по БПЛА, сохраняйте спокойствие, будьте предельно осторожны

26 Jul 2026, 19:35 UTC≈3,610 viewsread 8 August 2026

🗣Опасность БпЛА Мелитополь. БпЛА заходит в город с северо - запада

21 Jul 2026, 19:11 UTC≈5,390 viewsread 8 August 2026

Запорожская область РФ опасность БПЛА

18 Jul 2026, 19:44 UTC≈5,980 viewsread 8 August 2026

Опасность БпЛА по всей Запорожской области

18 Jul 2026, 19:36 UTC≈5,710 viewsread 8 August 2026

Противник готовит крайне массовый запуск БПЛА в направлении Запорожской области РФ, ЛДНР, Харьковской области РФ и далее в тыловые регионы, сообщает Lpr 1

13 Jul 2026, 20:11 UTC≈6,890 viewsread 8 August 2026

🗣Мелитополь и близлежащие, тревога по БпЛА

13 Jul 2026, 18:18 UTC≈6,710 viewsread 8 August 2026

🗣Мелитополь тревога по БПЛА. Меры безопасности

13 Jul 2026, 18:07 UTC≈6,340 viewsread 8 August 2026

🗣Запорожская область РФ Тревога по БПЛА

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

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

“РИА Мелитополь | Оповещения” (@riamelitopol_sos), 4,393 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/riamelitopol_sos.

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.