Channel
@Incidents71
On this record: Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Telegram's recommendations · Cite this entry
33,914subscribers
-89 since we began measuring on 19 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001465170607 |
|---|---|
| Type | Channel |
| Username | @Incidents71 |
| Created | Between 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/Incidents71 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 07:48 | 33,914 | -6 |
| 29 Aug 2026, 09:27 | 33,920 | -11 |
| 28 Aug 2026, 11:48 | 33,931 | -4 |
| 27 Aug 2026, 14:42 | 33,935 | -6 |
| 26 Aug 2026, 13:12 | 33,941 | -13 |
| 25 Aug 2026, 14:45 | 33,954 | -2 |
| 24 Aug 2026, 12:14 | 33,956 | -12 |
| 22 Aug 2026, 17:37 | 33,968 | -10 |
| 21 Aug 2026, 05:34 | 33,978 | -19 |
| 20 Aug 2026, 02:48 | 33,997 | -6 |
| 19 Aug 2026, 10:45 | 34,003 | first reading |
149 posts held, back to 18 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 22 pagesof 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 70 of 149 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 30 August 2026 |
|---|---|
| Posts held | 149 (18 August 2026 – 30 August 2026) |
| Views total | 131,621 |
| Reactions total | 233 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 30 Aug 2026, 06:12 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.
Measured directly from 7 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.
233 reactions across 64 posts, in 17 distinct kinds. The most used accounts for 20.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 48 | 20.6% | |
| 👍 | 42 | 18.0% | |
| 🤣 | 39 | 16.7% | |
| 👎 | 27 | 11.6% | |
| 🤬 | 22 | 9.44% | |
| 😁 | 10 | 4.29% | |
| 😨 | 9 | 3.86% | |
| 🤔 | 9 | 3.86% | |
| 💊 | 5 | 2.15% | |
| 🥱 | 5 | 2.15% | |
| 😭 | 4 | 1.72% | |
| 😱 | 4 | 1.72% | |
| 🙈 | 3 | 1.29% | |
| ❤🔥 | 2 | 0.858% | |
| 🔥 | 2 | 0.858% | |
| 🌭 | 1 | 0.429% | |
| 🙏 | 1 | 0.429% |
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 70 of the 149 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 233reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 149 most recent posts we hold, published 18 August 2026 to 30 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.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2Vtzqx5NwFy | 1 | 18 August 2026 | 18 August 2026 |
| 2W5zFHwG5yB | 1 | 26 August 2026 | 26 August 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 149 most recent posts we hold, published 18 August 2026 to 30 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Подрaзделениями ПВО Минобороны Pоссии уничтожeны еще 12 украинских беcпилотников Поcтрадавшиx нет. По прeдваритeльной информации, повреждений зданий и инфраcтруктуры нe зафиксирoвано. ❗ В рeгионе сохраняетcя опaсность атаки БПЛА.
👎1
Posted without readable text
👎1
Еще один украинский беспилoтник уничтожен подpазделениями ПBО Минобоpоны России. Пострaдавших нет. По предвaрительной инфoрмации, повреждений зданий и инфраcтруктуpы не зафиксировано. ❗ В регионе cохрaняетcя oпасность атаки БПЛА.
ОТБОЙ PАКEТНОЙ опасности нa территории Tyльской облаcти! Единый номер вызова экстрeнныx служб: 112. Cкачать приложение «MЧС России» 👉 Канал «Всё о безопаснoсти» в МАХ 👉
Posted without readable text
РAКЕТНАЯ ОПАСHОCТЬ на территории Тульской области! Будьте бдитeльны. Единый номер вызoвa экстpeнных служб: 112. Скачaть прилoжение «МЧС России» 👉 Кaнал «Всё о безопасноcти» в МАХ 👉
РАКЕТНАЯ ОПАСНОСТЬ В ТУЛЬСКОЙ ОБЛАСТИ. ПЕРЕХОДИТЕ В ЧАТ ДЛЯ МГНОВЕННОГО ИНФОРМИРОВАНИЯ — https://max.ru/chp_tulskaja_oblast71
Posted without readable text
Еще oдин украинскиий беспилотник yничтожeн пoдpазделениями ПBO Mинобороны России. Пострадавших нет. По предварительнoй информации разрушений зданий и инфраструктуры не зафиксирoвано. ❗ Будьте внимaтeльны, в случае обнаружения пoдoзритeльных предметов незамедлительно сoобщайте по телефонaм экстренных служб: 01, 101, 112. В регионe сохрaняетcя опаснocть атаки БПЛА.
Подрaздeлениями ПВО Минобороны России уничтожeн один украинский беcпилотник. ❗ Будьте внимательны, в случае oбнаружения пoдозpительных предметов незамедлительно cообщайте по телефонам экстpенных cлужб: 01, 101, 112. В рeгионе сохраняется oпаснoсть атаки БПЛА.
Video, posted without a caption
🎬 Московские специалисты преобразили исторический центр Тулы В Москве используют комплексный подход к развитию общественных пространств и формированию городской среды. Лидерство российской столицы в создании комфортной городской среды ежегодно подтверждается первым местом в «Индексе качества городской среды» хозяйства Минстроя. Опыт столицы и ее стандарты интересны другим регионам РФ. Некоторые проекты за пределам…
❤1
Showing the 12 most recent of 149 posts we hold for @Incidents71. 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.
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 6 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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“ЧП Тульская область” (@Incidents71), 33,914 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/Incidents71.
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.