Channel
@srochno_zaporozhye
On this record: Topic · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Polls · Citations · Telegram's recommendations · Cite this entry
8,017subscribers
-63 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001635256063 |
|---|---|
| Type | Channel |
| Username | @srochno_zaporozhye |
| Description | Вся Запорожская область тут 🇷🇺🇷🇺🇷🇺 По поводу рекламы: @Olegmgtg Все вопросы, предложения и новости пишите в наш бот: @zaporozhye_srochno_bot Ссылка для друзей https://t.me/+qVHNfrprTd0wYWIy |
| Created | 29 August 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/srochno_zaporozhye |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 57% 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.
This channel is in a group of 2 registered channels linked by matching posts. 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Nov 2026, 21:56 | 8,017 | -8 |
| 2 Nov 2026, 06:31 | 8,025 | -13 |
| 26 Oct 2026, 17:09 | 8,038 | -22 |
| 23 Oct 2026, 22:54 | 8,060 | -17 |
| 21 Oct 2026, 01:37 | 8,077 | -2 |
| 18 Oct 2026, 06:58 | 8,079 | -8 |
| 14 Oct 2026, 20:39 | 8,087 | +4 |
| 11 Oct 2026, 18:38 | 8,083 | -16 |
| 5 Oct 2026, 16:35 | 8,099 | -22 |
| 27 Sept 2026, 15:37 | 8,121 | -10 |
| 18 Sept 2026, 03:41 | 8,131 | -13 |
| 13 Sept 2026, 17:57 | 8,144 | -7 |
| 9 Sept 2026, 21:59 | 8,151 | +5 |
| 4 Sept 2026, 19:37 | 8,146 | -11 |
| 1 Sept 2026, 08:14 | 8,157 | +12 |
| 29 Aug 2026, 07:23 | 8,145 | -13 |
| 26 Aug 2026, 08:04 | 8,158 | +24 |
| 23 Aug 2026, 14:12 | 8,134 | -3 |
| 20 Aug 2026, 06:53 | 8,137 | +4 |
| 17 Aug 2026, 12:45 | 8,133 | first reading |
209 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 44 pages of Telegram’s post history, 20 posts per page.
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 38 of 79 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 10 November 2026 |
|---|---|
| Posts held | 209 (2 August 2026 – 10 November 2026) |
| Views total | 84,680 |
| Reactions total | 79 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Nov 2026, 17:05 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.
Lifetime counters from Telegram’s own channel header, read 10 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.
Measured directly from 19 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.
608 reactions across 145 posts, in 11 distinct kinds. The most used accounts for 23.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👎 | 140 | 23.0% | |
| 🔥 | 122 | 20.1% | |
| ❤ | 114 | 18.8% | |
| 🙏 | 89 | 14.6% | |
| 👍 | 82 | 13.5% | |
| 😁 | 22 | 3.62% | |
| 😢 | 17 | 2.80% | |
| 👏 | 9 | 1.48% | |
| 🤔 | 6 | 0.987% | |
| 😭 | 5 | 0.822% | |
| 😍 | 2 | 0.329% |
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 153 of the 209 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 608 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 209 most recent posts we hold, published 2 August 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’s own ‘edited’ marker: 31 of 79 posts held from the last 30 days (39.2%) 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).
❗️В Абу-Даби завершился первый день трехсторонних переговоров России, США и Украины, посвященных урегулированию украинского конфликта — РБК «Встреча продолжалась более четырех часов. Второй день переговоров запланирован на 11 ноября», — сообщают СМИ. Срочно Запорожье ⚡️ Наш бот
Евгений Балицкий проведет Прямую линию Губернатор анонсировал вторую прямую линию с жителями Запорожской области. Задать их можно заранее по номеру 8 800 30 22 222 с 09:00 до 18:00, а также через Телеграм-бот, MAX, ВКонтакте и Госуслуги. Трансляция пройдёт на телеканале «ЗаТВ» и «ЗаРадио». Глазами Мелитопольца Глазами Мелитотольца MAX
❗️Делегация в Абу-Даби будет принимать решение — связываться с Путиным с площадки переговоров или же подготовить комплексный доклад — в зависимости от хода переговоров — Песков Срочно Запорожье ⚡️ Наш бот
❤1👍1
⚡️️️️Кадры начала переговоров России, США и Украины в Абу-Даби Срочно Запорожье ⚡️ Наш бот
❤2
❗️Опасность БпЛА по г. Мелитополь и Мелитопольскому району Срочно Запорожье ⚡️ Наш бот
🙏2
Дроппер вернёт пенсионерке из Мелитополя 160 тысяч рублей В марте 2025 года мошенник, представившись сотрудником банка, убедил пенсионерку перевести деньги на «безопасный счёт». Женщина отправила 160 тысяч рублей на счёт другого человека. Найти мошенников не удалось, но прокуратура установила владельца счёта, через который прошли деньги. Суд взыскал с него всю сумму в пользу пенсионерки и ещё 5 800 рублей госпошлин…
❗️Российская делегация вылетела в Абу-Даби, где запланированы трехсторонние переговоры между Россией, США и Украиной — источник РИА Новости Срочно Запорожье ⚡️ Наш бот
🤔1
Нейрохирурги Мелитопольской областной больницы прооперировали 34-летнего пациента с опухолью правой глазницы Опухоль размером почти 4 сантиметра проросла в полость черепа и верхнечелюстную пазуху, сдавливала глазное яблоко и зрительный нерв. У мужчины были сильные головные боли, ухудшилось зрение и выпячивался правый глаз. Обследование показало, что опухоль в глазнице — метастаз новообразования в лёгком. Хирурги уд…
❤4😍1
❗️Опасность БпЛА Мелитополь, Мелитопольский район Срочно Запорожье ⚡️ Наш бот
Posted without readable text
Токмакский район Опасность по БПЛА Срочно Запорожье ⚡️ Наш бот
❗️Утром в Энергодаре в результате удара FPV-дрона по автомобилю «Славута» погиб 59-летний мужчина По сообщению, это произошло на перекрёстке улиц Комсомольской и Курчатова. Мужчина скончался на месте. Срочно Энергодар
😢3
Showing the 12 most recent of 209 posts we hold for @srochno_zaporozhye. 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.
We recorded 7 posts on @srochno_zaporozhye as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
The 6 most recent of 15 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
Поддерживаете решение?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
А вы делали прививку?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
У вас дома тепло?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
У вас есть свет?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Какой церковный праздник совпадает с Днём народного единства?
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
В каком году был учреждён День народного единства в современной России?
Shares as published. No per-option vote count is published by Telegram, so none is 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 209 most recent posts we hold, published 2 August 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 5 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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.
This channel appears in 13 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“Срочно Запорожье” (@srochno_zaporozhye), 8,017 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/srochno_zaporozhye.
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.