Channel
@skoraya125
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
20subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003679081197 |
|---|---|
| Type | Channel |
| Username | @skoraya125 |
| Description | 🚨 Служба аварийных комиссаров «Скорая страховая помощь» ⏰ Выезд на ДТП за 15 минут 📄 Оформление полиса страхования ☎️ +7-967-388-88-89 ‼️ Материалы могут быть использованы только с согласия правообладателя и указанием источника информации |
| Created | 14 February 2026 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/skoraya125 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 16:01 | 20 | no change |
| 7 Aug 2026, 19:09 | 20 | first reading |
8 posts held, back to 14 February 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 1 pageof 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 8 posts for this entry, the most recent from 2 July 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 4 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.
8 reactions across 4 posts, in 4 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 50.0% | |
| 🏆 | 2 | 25.0% | |
| 😱 | 1 | 12.5% | |
| 🤬 | 1 | 12.5% |
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 4 of the 8 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 8reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 14 February 2026 to 2 July 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.
🆘 Бесконтактное ДТП произошло во Владивостоке в районе Второй речки. 🚘 Водитель рогатого транспортного средства поворачивал по маршруту в сторону конечной тысячекоечной больницы, следом двигался Mitsubishi Eclipse, которому и досталось: от троллейбусных рогов отлетел соединительный элемент, данный весомый предмет пробил лобовое стекло Mitsubishi. 🆘 По счастливой случайности в результате данного ДТП никто не пострад…
🤬1😱1
🆘 Дорожные изменения на Бородинской 👮♂️ Выполненные работы: Нанесена новая дорожная разметка Фактически перекрыт поворот на улицу Героев-Варяга Ограничен проезд к колледжу с улицы Героев-Варяга 🆘 Текущие проблемы: Водители игнорируют новые ограничения Совершаются повороты через сплошную линию разметки Создается потенциально опасная ситуация 👮♂️ Важно знать: Водителям рекомендуется соблюдать новые правила движ…
🆘 ДТП на 3-й Рабочей: 👮♂️ оперативная сводка 🚗 Очередной инцидент на перекрестке с круговым движением показал, насколько важно быть внимательным за рулём! 📞 Как вызвать аварийного комиссара: Телефон: +7-967-388-88-89; Telegram: Скорая страховая помощь Наш сайт: komissar125.ru. 📌 Сохраняйте контакты службы аварийных комиссаров «Скорая страховая помощь» — пусть наш номер будет под рукой на случай непредвиденных…
🆘 ДТП в районе 3‑й Рабочей: момент аварии попал на камеры наблюдения 🎥 Городские камеры видеонаблюдения зафиксировали момент дорожно‑транспортного происшествия в районе 3‑й Рабочей. 👮♀️ Информация предоставлена аварийным комиссаром службы «Скорая страховая помощь». 🚘 Вызов аварийного комиссара: зачем и когда? Доверьте оформление профессионалам! Аварийный комиссар приедет за 15 минут и: оформит ДТП по правилам; з…
🏆2
🆘 В службу аварийных комиссаров «Скорая страховая помощь» поступил вызов о том, что в районе Гоголя, 7, предположительно в нетрезвом состоянии водитель Harrier устроил массовое ДТП. Вёл себя данный персонаж неадекватно, размахивал удостоверением, представлялся военнослужащим, и ничего ему не будет. 👮♂️ Аварийный комиссар незамедлительно обратился в госавтоинспекцию и сообщил о происходящем, оформлением ДТП будут за…
❤2
Posted without readable text
🚓 ДТП на перекрестке Адмирала Горшкова. 🆘 Незаменимый специалист прибыл из дружественной страны покорять город у моря, но всё пошло не по плану. 👉 На его голову свалилось сразу 2 беды: незнание ПДД, выезжая со второстепенной дороги, не уступил дорогу двигающемуся по главной Toyota Probox 🆘 Беда вторая — снег на голову свалился специалиста. 👉 В ДТП транспортные средства получили сильные механические повреждения и…
❤2
Channel created
Showing the 8 most recent of 8 posts we hold for @skoraya125. 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.
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.
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“🚨 Скорая Страховая Помощь” (@skoraya125), 20 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/skoraya125.
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.