Channel
@incidentoren
On this record: Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry
16,493subscribers
-31 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001113338052 |
|---|---|
| Type | Channel |
| Username | @incidentoren |
| Created | 30 January 2017 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/incidentoren |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 00:14 | 16,493 | -13 |
| 12 Aug 2026, 19:13 | 16,506 | -5 |
| 11 Aug 2026, 15:41 | 16,511 | -4 |
| 10 Aug 2026, 12:18 | 16,515 | -7 |
| 9 Aug 2026, 12:37 | 16,522 | -1 |
| 8 Aug 2026, 15:45 | 16,523 | +3 |
| 7 Aug 2026, 14:07 | 16,520 | -4 |
| 6 Aug 2026, 14:30 | 16,524 | no change |
| 6 Aug 2026, 14:29 | 16,524 | first reading |
183 posts held, back to 6 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 18 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 55 of 183 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 13 August 2026 |
|---|---|
| Posts held | 183 (6 August 2026 – 13 August 2026) |
| Views total | 66,238 |
| Reactions total | 111 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 15:10 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 18 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.
111 reactions across 55 posts, in 10 distinct kinds. The most used accounts for 20.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤡 | 23 | 20.7% | |
| 👍 | 21 | 18.9% | |
| 👎 | 16 | 14.4% | |
| custom 5433686606479397010 | 15 | 13.5% | |
| 💩 | 10 | 9.01% | |
| custom 5433906568934497197 | 9 | 8.11% | |
| 🔥 | 5 | 4.50% | |
| 🤬 | 5 | 4.50% | |
| 🥴 | 5 | 4.50% | |
| 🖕 | 2 | 1.80% |
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 areTelegram’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 55 of the 183 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 111reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 183 most recent posts we hold, published 6 August 2026 to 13 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 |
|---|---|---|---|
| 2W5zFJ4nPh3 | 1 | 8 August 2026 | 8 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 183 most recent posts we hold, published 6 August 2026 to 13 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.
🚛 Загородное шоссе в Оренбурге встало в пробке из-за ДТП с грузовиком Авария случилась на участке у поворота на улицу Тихую. Тягач с сельхозтехникой столкнулся с легковушкой. В результате на трассе образовался серьёзный затор, который растянулся на большое расстояние. 🔞 Инцидент в MAXe ✅ Поделиться новостью (платим за эксклюзив) 🚀 Дать буст каналу
💅Топ мастеру требуются МОДЕЛИ на педикюр с покрытием Luxio для создания портфолио 1099₽ вместо 2500₽ Занятость не более 60 мин Запись ТГ @kristka1987
👎1
🔨 В Оренбурге осудили мужчину за похищение, вымогательство и удушение Областной суд вынес приговор по резонансному делу. Преступник похитил человека, требовал деньги и душил свою жертву. Приговор ещё не вступил в законную силу — защита может его обжаловать. 🔞 Инцидент в MAXe ✅ Поделиться новостью (платим за эксклюзив) 🚀 Дать буст каналу
🛴 Оренбуржец устроил разборки с электросамокатом и вышел победителем Камера домофона в одном из дворов города засняла необычную сцену. Местный житель не стал обходить препятствие, а решил разобраться с ним радикально — просто сбил двухколёсный транспорт с ног. Самокат остался валяться на боку, а мужчина с чувством выполненного долга отправился дальше по своим делам. Видео: Telegram-канал «Оренбург очевидец». 🔞 И…
🔥1
⚡️ Медики Оренбуржья обеспечены бензином в полном объёме Необходимый запас топлива поступил во все лечебные учреждения области. Бригады скорой помощи работают без сбоев — по заверению замминистра здравоохранения Павла Орлова, отклик будет на каждый поступивший вызов. Горючее также получили автомобили, перевозящие пациентов на процедуры гемодиализа и перитонеального диализа. Не остались без внимания амбулаторные слу…
🚦 В Орске на площади Гагарина меняют светофор, который не работал несколько недель Оборудование, регулирующее поток машин с «нижней» дороги, вышло из строя, из-за чего движение было затруднено и для водителей, и для пешеходов. Сегодня, 13 августа, рабочие уже нанесли разметку, начали менять светофоры и дорожные знаки. В администрации города сообщили, что работы ведутся в рамках реконструкции площади, новые светофор…
🚨 В Бугурусланском районе перевернулась Lada Granta: водитель в больнице Авария случилась сегодня утром, 13 августа, около 07:30 на 137-м километре трассы Бугуруслан — Бузулук. 37-летний житель Самарской области ехал за рулём Lada Granta в сторону Бузулука. По предварительным данным, он не справился с управлением — машину снесло в кювет, где она опрокинулась. Водитель получил серьёзные травмы. Отмечается, что в мо…
🥴1
🚧 Жители дома на улице Котова жалуются на раскопки, которые не могут закончить с мая Жильцы дома №103 по улице Котова в Оренбурге возмущены состоянием дороги после ремонта труб. Рабочие оставили после себя открытую траншею, которая так и не была закопана. По словам местных, раскопки ведутся с конца мая — начала июня. Раньше здесь был ровный асфальт, а теперь на этом месте яма, в которой легко получить травму. Никто…
custom 54336866064793970101
Posted without readable text
💩1
🌡️ Жара и грозы: оренбуржцев ждёт резкая смена погоды В пятницу, 14 августа, в регионе заметно испортится погода. Синоптики обещают усиление ветра — его порывы будут достигать 15–19 метров в секунду, а также грозу. При этом жара никуда не денется: воздух в области прогреется до +30…+31°C. 🔞 Инцидент в MAXe ✅ Поделиться новостью (платим за эксклюзив) 🚀 Дать буст каналу
🌿 Детская площадка на улице Липовой в Оренбурге заросла и разрушается Местные жители пожаловались на запущенное состояние игровой зоны. Территория полностью заросла травой, по всей площадке разбросан мусор. Скамейки сломаны, а малые архитектурные формы повреждены и исписаны надписями. Приводить детей на такую площадку, по словам оренбуржцев, просто опасно. 🔞 Инцидент в MAXe ✅ Поделиться новостью (платим за экск…
💩1
🚨 В Оренбурге Porsche Macan вылетел в кювет и перевернулся: пострадали две женщины Авария случилась 13 августа на улице Баргузинской. Напротив дома №4 44-летняя водительница кроссовера при повороте направо не справилась с управлением — машина съехала в кювет и опрокинулась. В результате ДТП автоледи и её 37-летняя пассажирка получили травмы. Обеих доставили в больницу. Сейчас обстоятельства происшествия устанавлив…
👍1🤡1
Showing the 12 most recent of 183 posts we hold for @incidentoren. 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.
Citation-graph rank — 983,865 of 1,189,255entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 2 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.
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 2 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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“Оренбург Инцидент 🚨” (@incidentoren), 16,493 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/incidentoren.
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.