🔴🔴🔴Стал свидетелем ДТП, ЧП, пожара, неправильной парковки , или просто хочешь поделиться какой-то историей или несправедливостью с широкой аудиторией , тогда смело пиши нам в бот @yoshkachp_bot Проголосовать за канал: голос! 🚀 Йошкар-Ола. Происшествия 📲Прислать новость: @yoshkachp_bot

Channel
Йошкар-Ола. Происшествия
@yoshka12_chp
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry
58,694subscribers
-253 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001228617798 |
|---|---|
| Type | Channel |
| Username | @yoshka12_chp |
| Description | ЧП - Что Произошло? Новости Йошкар-Олы и республики Марий Эл в одном месте. 🤝Реклама: https://telega.in/c/yoshka12_chp |
| Created | 29 July 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 29 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/yoshka12_chp |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 21:58 | 58,694 | -35 |
| 4 Sept 2026, 11:36 | 58,729 | +15 |
| 3 Sept 2026, 00:24 | 58,714 | -15 |
| 1 Sept 2026, 21:27 | 58,729 | +4 |
| 31 Aug 2026, 22:04 | 58,725 | -9 |
| 30 Aug 2026, 18:53 | 58,734 | -10 |
| 29 Aug 2026, 17:34 | 58,744 | -56 |
| 28 Aug 2026, 20:37 | 58,800 | -28 |
| 27 Aug 2026, 23:33 | 58,828 | -22 |
| 26 Aug 2026, 20:54 | 58,850 | -3 |
| 26 Aug 2026, 00:07 | 58,853 | -17 |
| 24 Aug 2026, 22:12 | 58,870 | -19 |
| 23 Aug 2026, 05:07 | 58,889 | -33 |
| 21 Aug 2026, 19:07 | 58,922 | +16 |
| 20 Aug 2026, 15:54 | 58,906 | +1 |
| 19 Aug 2026, 17:41 | 58,905 | -6 |
| 18 Aug 2026, 14:52 | 58,911 | -2 |
| 17 Aug 2026, 18:23 | 58,913 | -20 |
| 16 Aug 2026, 16:08 | 58,933 | -7 |
| 14 Aug 2026, 21:24 | 58,940 | first reading |
Engagement
343 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 71 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 9.86%
- avg views ÷ 58,694 subscribers
- Avg views / post
- 5,790
- 299 posts measured
- Reaction rate
- 0.182%
- reactions ÷ views · ER floor
- Posts in window
- 299
- of 343 held
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 276 of 299 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 9 September 2026 |
|---|---|
| Posts held | 343 (6 August 2026 – 9 September 2026) |
| Views total | 1,730,751 |
| Reactions total | 2,935 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Sept 2026, 20:50 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.
What this channel posts
- Photos
- ≈17,500
- Videos
- ≈4,510
- Links
- ≈13,500
Lifetime counters from Telegram’s own channel header, read 9 September 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.
- Video runtime
- 16m 23s
- Average length
- 45s
Measured directly from 22 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.
Reaction mix
3,787 reactions across 302 posts, in 55 distinct kinds. The most used accounts for 26.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1,003 | 26.5% | |
| 🤡 | 519 | 13.7% | |
| 👎 | 350 | 9.24% | |
| 🤣 | 327 | 8.63% | |
| 🔥 | 170 | 4.49% | |
| 😢 | 152 | 4.01% | |
| 👍 | 151 | 3.99% | |
| 🙏 | 136 | 3.59% | |
| 😭 | 117 | 3.09% | |
| 🤬 | 104 | 2.75% | |
| 🕊 | 98 | 2.59% | |
| ❤🔥 | 70 | 1.85% | |
| 🫡 | 58 | 1.53% | |
| 😁 | 54 | 1.43% | |
| 🥱 | 47 | 1.24% | |
| 👌 | 41 | 1.08% | |
| 😱 | 38 | 1.00% | |
| 😍 | 35 | 0.924% | |
| 👏 | 25 | 0.66% | |
| 👨💻 | 25 | 0.66% | |
| 35 further kinds | 267 | 7.05% |
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 319 of the 343 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 3,787 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 343 most recent posts we hold, published 6 August 2026 to 9 September 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 Stars
- Stars received
- 9
- across the posts below
- Posts paid on
- 8
- of 343 we hold a reading for · 2%
- Most on one post
- 2
- single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @yoshka12_chp. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 343 most recent posts we hold for this entry, published 6 August 2026 to 9 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Advertising
- Ad load
- 1.17%
- 4 of 343 posts carry an ad marker
- Regulatory tokens
- 4
- posts carrying an erid · 4 distinct tokens
- Median views · ads
- 5,740
- over 4 measured posts
- Median views · rest
- 6,030
- over 339 measured posts
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 |
|---|---|---|---|
| 2VtzqwQU73q | 1 | 20 August 2026 | 20 August 2026 |
| 2W5zFGPxfdj | 1 | 14 August 2026 | 14 August 2026 |
| 2W5zFGSuJ3T | 1 | 7 August 2026 | 7 August 2026 |
| 2W5zFHnLU2u | 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 343 most recent posts we hold, published 6 August 2026 to 9 September 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.
Recent posts
Posted without readable text
👎5❤🔥3❤1
Жители Йошкар-Олы, нужна ваша помощь в поисках человека! Отряд «ЛизаАлерт» просит откликнуться водителей и владельцев камер видеонаблюдения. Ищут Кукину (Жамойдову) Людмилу Анатольевну. Критически важны записи за 2 сентября 2026 года (13:30–15:00) с участка улицы Мира, проходящего мимо СНТ «Мичуринец» в сторону Куярского кольца. Если у вас есть информация, сообщите нам: 📞 8 (800) 700-54-52 (горячая линия) Источни…
❤11
❗️Внимание! Пропал человек! Источник: ЛизаАлерт Марий Эл Проголосовать за канал: голос! 🚀 Йошкар-Ола. Происшествия 📲Прислать новость: @yoshkachp_bot
❤6
⚡Внимание! Поиски продолжаются! Источник: ЛизаАлерт Марий Эл Проголосовать за канал: голос! 🚀 Йошкар-Ола. Происшествия 📲Прислать новость: @yoshkachp_bot
Читатели делятся кадрами с места ДТП в городе. Проголосовать за канал: голос! 🚀 Йошкар-Ола. Происшествия 📲Прислать новость: @yoshkachp_bot
❤3😢1
Двор и подъезды Воинов Интернационалистов 22а. Рядом школа и детский сад 🫣 Проголосовать за канал: голос! 🚀 Йошкар-Ола. Происшествия 📲Прислать новость: @yoshkachp_bot
❤10🔥1🤩1🤬1
Срочно требуются пользователи ПК З/П от 43000 рублей (из дома) Сейчас на удалённые вакансии спрос огромный, а 80% людей интересует только работа на дому (и это понятно). Поэтому канал «Удаленочка» предлагает вакансии для работы из дома: — свободный график — оплата 2-3 раза в месяц — официальное трудоустройство или подработка (выбираете Вы) Спешите на Удаленочку, там всем платят хорошие деньги за простую работу из …
🤡10
Вчера на перекрестке улиц Кремлевская и Я. Эшпая водитель Lada Granta при повороте налево на разрешающий сигнал светофора не уступил дорогу движущемуся со встречного направления прямо автомобилю ВАЗ-2112. В результате ДТП водитель автомашины ВАЗ-2112 и двое его пассажиров с травмами доставлены в больницу. Источник: Госавтоинспекция Марий Эл Проголосовать за канал: голос! 🚀 Йошкар-Ола. Происшествия 📲Прислать новос…
❤2
Прогноз погоды на сегодня ☀️ Проголосовать за канал: голос! 🚀 Йошкар-Ола. Происшествия 📲Прислать новость: @yoshkachp_bot
🔹Отбой беспилотной опасности на территории республики, сообщает РСЧС. Проголосовать за канал: голос! 🚀 Йошкар-Ола. Происшествия 📲Прислать новость: @yoshkachp_bot
🗿3🥱2
‼️Сегодня утром в Марий Эл была объявлена беспилотная опасность, сообщили РСЧС. Проголосовать за канал: голос! 🚀 Йошкар-Ола. Происшествия 📲Прислать новость: @yoshkachp_bot
🥱5
Showing the 12 most recent of 343 posts we hold for @yoshka12_chp. 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.
Mentions
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.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
@yoshka_chp_12 · 17,491#1
@yoshka_smi · 28,758#2
@chp_yo · 6,438#3
@progorod12 · 13,992#4
@yoshkoroche · 15,918#5
@yo_city · 6,737#6
@gibdd_rme · 9,271#7
@chpyo12 · 5,299#8
@yoshkin_guide · 4,725#9
@mariellive · 5,293#10
@topyo_media · 15,262#11
@ttwice12 · 1,425#12
@dubinki · 384#13
@lyceum28jo · 2,434#14
@okyrokgswagga · 401#15
@nosferatu_yo · 1,802#16
@mypervie12 · 1,365#17
@Crypt0Mems · 342#18
@moshpit_yo · 2,298#19
@rmnvshka · 1,597#20
@yoshkarolamoda · 690#21
@ztparty · 2,664#22
@tripyoparty · 598#23
@kpopcdyo · 618#24
@vrrabl · 416#25
@digitalmarsu · 4,475#26
@sbk12_official · 1,239#27
@dvvvor · 2,233#28
Read from Telegram’s recommendation API, most recently 9 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
@yoshka_smi · 28,758
Telegram ranks this channel #1 of 29 here — alongside 28 others — read 9 September 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list 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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“Йошкар-Ола. Происшествия” (@yoshka12_chp), 58,694 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/yoshka12_chp.
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.