Telegram RegisterThe public register of Telegram
Telegram profile photo for МЧС Запорожской области

Channel

МЧС Запорожской области

@mchs85

Not marked by Telegram, checked 30 September 2026

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

4,286subscribers

-86 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-1002172172378
TypeChannel
Username@mchs85
Created8 July 2024 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live9 November 2026
Measurements held22
Confirmed unchanged1 time, most recently 9 November 2026
On Telegramt.me/mchs85

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 13 September 2026 and assigned it the closest of 31 fixed categories, at 66% 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. This entry also sits inside a group of 5 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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 (4 of the pairs behind the counts below)
Posted firstThenOverlapGap
@mchs85/5465 · this entry5 Aug 2026, 08:20 UTC@vasylevka/400325 Aug 2026, 08:23 UTC1.003 minutes
@mchs85/5466 · this entry5 Aug 2026, 13:57 UTC@vasylevka/400495 Aug 2026, 14:54 UTC1.0057 minutes
@mchs85/5475 · this entry8 Aug 2026, 11:10 UTC@vasylevka/400848 Aug 2026, 15:07 UTC1.003.9 hours
@mchs85/5476 · this entry8 Aug 2026, 13:59 UTC@vasylevka/400858 Aug 2026, 15:07 UTC1.0068 minutes
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
@vasylevka6 (6/6 hand-verifiable sample passed)1.0062 minutesthis entry (6–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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 30 comparable posts for this entry, running 2 August 2026 to 8 August 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).

Of the group of 5 channels, the one whose matching posts we hold earliest is @mchs85 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 12 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.

Channels linked by matching posts

This channel is in a group of 5 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

4,2864,3724,3296 August 2026 — 4,372 subscribers6 August 2026 — 4,372 subscribers9 August 2026 — 4,368 subscribers12 August 2026 — 4,365 subscribers16 August 2026 — 4,362 subscribers19 August 2026 — 4,358 subscribers22 August 2026 — 4,357 subscribers25 August 2026 — 4,353 subscribers31 August 2026 — 4,355 subscribers3 September 2026 — 4,348 subscribers7 September 2026 — 4,342 subscribers11 September 2026 — 4,346 subscribers30 September 2026 — 4,334 subscribers7 October 2026 — 4,327 subscribers13 October 2026 — 4,324 subscribers18 October 2026 — 4,318 subscribers25 October 2026 — 4,315 subscribers28 October 2026 — 4,301 subscribers31 October 2026 — 4,298 subscribers3 November 2026 — 4,296 subscribers6 November 2026 — 4,292 subscribers9 November 2026 — 4,286 subscribers6 August 20269 November 2026
22 measurements spanning 95 days, net -86. 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,273–4,385 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 22
Measured (UTC)SubscribersChange
9 Nov 2026, 15:054,286-6
6 Nov 2026, 16:164,292-4
3 Nov 2026, 13:284,296-2
31 Oct 2026, 11:274,298-3
28 Oct 2026, 06:364,301-14
25 Oct 2026, 10:144,315-3
18 Oct 2026, 23:594,318-6
13 Oct 2026, 03:484,324-3
7 Oct 2026, 00:574,327-7
30 Sept 2026, 04:424,334-12
11 Sept 2026, 20:594,346+4
7 Sept 2026, 12:354,342-6
3 Sept 2026, 00:564,348-7
31 Aug 2026, 02:244,355+2
25 Aug 2026, 18:364,353-4
22 Aug 2026, 21:354,357-1
19 Aug 2026, 15:134,358-4
16 Aug 2026, 07:594,362-3
12 Aug 2026, 11:154,365-3
9 Aug 2026, 12:364,368first reading

Engagement

30 posts held, back to 2 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 6 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 30 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
15s
Average length
15s

Measured directly from 1 video 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

87 reactions across 25 posts, in 6 distinct kinds. The most used accounts for 31.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52311077909944167652731.0%
custom 54471915126663516792731.0%
😱1112.6%
🫡910.3%
❤78.05%
✍66.90%

Custom emoji. 2 of the rows above are 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 counts beside them are 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 30 of the 30 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 105 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 30 most recent posts we hold, published 2 August 2026 to 8 August 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

8 Aug 2026, 13:59 UTC≈1,050 views3 reactionsread 8 August 2026
Photo

⚡️⚡️⚡️⚡️ С 8 на 9 августа на территории региона ожидается: 🔔переменная облачность. Ночью преимущественно без осадков, днем местами кратковременный дождь, гроза. Ветер северной четверти 7-12 м/с, днем, в том числе при грозе, местами порывы 15-19 м/с. Температура воздуха ночью 20…25°; днем 30…35°, по югу до 37°. ⭕В западных районах чрезвычайная пожароопасность (5 класс); в восточных, юго-восточных и юго-западных райо…

✍1custom 52311077909944167651custom 54471915126663516791

8 Aug 2026, 11:10 UTC≈1,670 views3 reactionsread 8 August 2026
Photo

❗❗❗ Штормовое предупреждение о комплексе метеорологических явлений В период 14-16 часов и до конца суток 8 августа, в течение суток 9 августа местами в Запорожской области ожидается комплекс метеорологических явлений: сильный дождь, ливень в сочетании с грозой, градом и сильным ветром 20-25 м/с. По данным ФГБУ «Северо-Кавказское УГМС» Будь внимателен и осторожен! Телефон экстренной службы «101». МЧС Запорожской о…

😱1custom 52311077909944167651custom 54471915126663516791

8 Aug 2026, 08:18 UTC255 views3 reactionsread 8 August 2026
Photo

❗❗❗ Экстренное предупреждение Во второй половине дня 9 августа по Азовскому морю ожидается усиление северного ветра 12-17 м/с порывы до 22 м/с. Высота волн 1,3-1,5 м. По данным ФГБУ «Крымское УГМС» Существует вероятность возникновения чрезвычайных ситуаций и происшествий, связанных с: ⭕затоплением причалов и оградительных молов, прибрежных участков (зданий и сооружений); ⭕повреждением судов у причалов и береговых …

😱1custom 52311077909944167651custom 54471915126663516791

8 Aug 2026, 07:29 UTC≈1,330 views3 reactionsread 8 August 2026
Photo

❗❗❗ Штормовое предупреждение о чрезвычайной пожароопасности До конца суток 8 августа, в течение суток 9 августа в Запорожской области чрезвычайная пожароопасность (5 класс) ожидается в западных районах (город областного значения Энергодар, Каменско-Днепровский, Васильевский, Михайловский, Токмакский районы); высокая пожароопасность (4 класс) - в восточных (Пологовский, Черниговский, Куйбышевский), юго-восточных (При…

😱1custom 52311077909944167651custom 54471915126663516791

8 Aug 2026, 06:21 UTC247 views3 reactionsread 8 August 2026

🚒Оперативная информация за сутки Подробнее читай тут МЧС Запорожской области | MAX | ВК Подписывайся на МЧС России в MAX | ВК

🫡1custom 52311077909944167651custom 54471915126663516791

7 Aug 2026, 13:59 UTC≈3,630 views4 reactionsread 8 August 2026
Photo

⚡️⚡️⚡️⚡️ С 7 на 8 августа на территории региона ожидается: 🔔переменная облачность. Ночью без существенных осадков, днем в отдельных районах кратковременный дождь, гроза. Ветер восточной четверти 7-12 м/с, днем местами, в том числе при грозе, порывы 15-18 м/с. Температура воздуха ночью 20…25°, днем 32…37°, во второй половине дня сильная жара 40°, в прибрежных районах 38°. ⭕В западных районах чрезвычайная пожароопасн…

✍1❤1custom 52311077909944167651custom 54471915126663516791

7 Aug 2026, 11:19 UTC358 views3 reactionsread 8 August 2026
Photo

❗Как действовать при атаке БПЛА Изучи памятку МЧС России по Запорожской области. Важные правила для всех: ⭕не подходи к обломкам; ⭕не трогай неизвестные предметы; ⭕не снимай БПЛА и места их падения. ✅Будьте внимательны и берегите себя! МЧС Запорожской области | MAX | ВК Подписывайся на МЧС России в MAX | ВК

✍1custom 52311077909944167651custom 54471915126663516791

7 Aug 2026, 08:42 UTC379 views4 reactionsread 8 August 2026
Photo

❗❗❗ Экстренное предупреждение Днем 7 августа по Азовскому морю сохранится восточный ветер 12-15 м/с. Высота волн 1,3-1,5 м. По данным ФГБУ «Крымское УГМС» Существует вероятность возникновения чрезвычайных ситуаций и происшествий, связанных с: ⭕затоплением причалов и оградительных молов, прибрежных участков (зданий и сооружений); ⭕повреждением судов у причалов и береговых сооружений; ⭕затруднением швартовки судов, …

custom 52311077909944167652✍1custom 54471915126663516791

7 Aug 2026, 07:15 UTC≈3,940 views4 reactionsread 8 August 2026
Photo

❗❗❗ Экстренное предупреждение о чрезвычайной пожароопасности До конца суток 7 августа, в течение суток 8 августа в Запорожской области чрезвычайная пожароопасность (5 класс) ожидается в западных районах (город областного значения Энергодар, Каменско-Днепровский, Васильевский, Михайловский, Токмакский районы); высокая пожароопасность (4 класс) — в восточных (Пологовский, Черниговский, Куйбышевский) и юго-западных (го…

custom 52311077909944167652😱1custom 54471915126663516791

7 Aug 2026, 06:58 UTC359 views3 reactionsread 8 August 2026

🚒Оперативная информация за сутки Подробнее читай тут МЧС Запорожской области | MAX | ВК Подписывайся на МЧС России в MAX | ВК

🫡1custom 52311077909944167651custom 54471915126663516791

5 Aug 2026, 13:57 UTC≈6,450 views3 reactionsread 8 August 2026
Photo

⚡️⚡️⚡️⚡️ С 5 на 6 августа на территории региона ожидается: 🔔переменная облачность. Преимущественно без осадков. Ветер восточной четверти 7-12 м/с. Температура воздуха ночью 19…24°, днем 32…37°, во второй половине дня сильная жара 40°, в прибрежных районах 38°. ⭕В западных районах чрезвычайная пожароопасность (5 класс); в восточных и юго-западных районах высокая пожароопасность (4 класс). 👩‍🚒МЧС России: соблюдай пр…

❤1custom 52311077909944167651custom 54471915126663516791

5 Aug 2026, 08:20 UTC≈8,270 views4 reactionsread 8 August 2026
Video

❗❗❗ Сильная жара 40° ожидается в Запорожской области Штормовое предупреждение об опасном явлении: днем 6, 7 и 8 августа в Запорожской области ожидается сильная жара 40°, в прибрежных районах 38°. По данным ФГБУ «Северо-Кавказское УГМС» МЧС России напоминает: ⭕пей больше воды; ⭕носи одежду из натуральных тканей светлых оттенков; ⭕надевай головной убор. МЧС Запорожской области | MAX | ВК Подписывайся на МЧС России …

custom 54471915126663516792✍1custom 52311077909944167651

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

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.

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.

Триколор над Запорожьем
@tricolourzaporogye · 49,450
Telegram ranks this channel #5 of 94 here — alongside 93 others — read 26 August 2026
Главное в Бердянске
@berdyansk_ru · 38,783
Telegram ranks this channel #16 of 85 here — alongside 84 others — read 1 September 2026
Главное в Энергодаре
@energodar_ru · 39,211
Telegram ranks this channel #19 of 87 here — alongside 86 others — read 1 September 2026
РИА Мелитополь
@riamelitopol · 18,841
Telegram ranks this channel #21 of 84 here — alongside 83 others — read 4 October 2026
«Запорожьеэнерго» филиал АО «Юго-Западная ЭСК»
@yuzesk_zp · 20,073
Telegram ranks this channel #24 of 58 here — alongside 57 others — read 28 September 2026
Запорожское Агентство Новостей
@zonewsru · 30,191
Telegram ranks this channel #26 of 96 here — alongside 95 others — read 8 September 2026
ЗaТВ. Новости Запорожской области
@za_tv_ru · 26,842
Telegram ranks this channel #27 of 79 here — alongside 78 others — read 11 September 2026
ЭНЕРГОДАРСКИЙ СВЯЗНОЙ🇷🇺
@zaporojie24 · 18,651
Telegram ranks this channel #29 of 57 here — alongside 56 others — read 4 October 2026
Запорожский Важный
@MELITOPOL_185 · 29,789
Telegram ranks this channel #30 of 74 here — alongside 73 others — read 8 September 2026
Главное в Мелитополе
@melitopol_ru · 100,867
Telegram ranks this channel #31 of 73 here — alongside 72 others — read 15 August 2026
Запорожский Телеграф
@zo_telegraf · 42,094
Telegram ranks this channel #33 of 67 here — alongside 66 others — read 29 August 2026
Будем жить 🎶
@budem_zhit · 24,217
Telegram ranks this channel #35 of 96 here — alongside 95 others — read 15 September 2026
ЗАПОРОЖСКИЙ ВЕСТНИК
@zpvestnik · 58,001
Telegram ranks this channel #36 of 79 here — alongside 78 others — read 22 August 2026
Бердянск. Официально
@glava_brd · 29,892
Telegram ranks this channel #47 of 54 here — alongside 53 others — read 7 September 2026
Балицкий Евгений
@BalitskyEV · 58,472
Telegram ranks this channel #57 of 82 here — alongside 81 others — read 22 August 2026
Артём Чехович | ПОЖАРНЫЙ
@artem0limp95 · 23,961
Telegram ranks this channel #59 of 72 here — alongside 71 others — read 16 September 2026
Триколор над Херсоном
@tricolourkherson · 45,817
Telegram ranks this channel #80 of 95 here — alongside 94 others — read 29 August 2026

This channel appears in 17 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 9 November 2026 — this entry's latest reading, not the date you are reading this.

“МЧС Запорожской области” (@mchs85), 4,286 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/mchs85.

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.