Channel
@mostik56
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
194subscribers
-17 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003928353502 |
|---|---|
| Type | Channel |
| Username | @mostik56 |
| Created | Between 1 April 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/mostik56 |
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 24 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 05:37 | 194 | -10 |
| 7 Sept 2026, 19:58 | 204 | -4 |
| 30 Aug 2026, 11:54 | 208 | -1 |
| 24 Aug 2026, 04:34 | 209 | +1 |
| 16 Aug 2026, 07:18 | 208 | -3 |
| 8 Aug 2026, 11:01 | 211 | no change |
| 7 Aug 2026, 14:18 | 211 | first reading |
16 posts held, back to 31 July 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 page of 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 16 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
42 reactions across 14 posts, in 11 distinct kinds. The most used accounts for 38.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 16 | 38.1% | |
| 👏 | 6 | 14.3% | |
| 👍 | 4 | 9.52% | |
| 😁 | 3 | 7.14% | |
| 🤣 | 3 | 7.14% | |
| 🫡 | 3 | 7.14% | |
| ✍ | 2 | 4.76% | |
| 🔥 | 2 | 4.76% | |
| 👎 | 1 | 2.38% | |
| 🤔 | 1 | 2.38% | |
| 🥰 | 1 | 2.38% |
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 14 of the 16 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 42 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 31 July 2026 to 7 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.
Меня ЗАКРЫВАЮТ сегодня в 23:00 🥸 Для меня эта новость — как гром среди ясного неба... В общем, до 6 часов утра 10 августа я буду закрыт. Так что по домам как разъедетесь в Южный и окрестности, имейте в виду: обратно — по другой дороге. Причина, конечно же, в демонтаже несущих конструкций. В это время ездить по мне небезопасно. Для пешеходов, к слову, ограничений не будет: вы можете ходить по мне в обе стороны. А гр…
❤1👎1🤔1
Не я, но тоже любопытно... Это мой сосед — жд-мост — в 1909 году ☝🏻 Я про него давеча рассказывал)
Движение по Донгузской меняется ‼️ Скоро будет так: вы съезжаете с меня в сторону Южного, и у вас будет отдельный левый поворот в Кузнечный, чтобы для движения прямо были доступны две полосы. Говорят, это должно улучшить трафик. Мэр, к слову, отмечает, что понимает неудобства от ремонта меня и этой улицы, выражает вам благодарность за понимание ✊
Вот так снимали мою дряблую кожу 😬 Сейчас уже получше, конечно)
👏2
Ну вот куда белый такой попёрся, грязнулей же вернётся домой 🤣 #барсик_мостовой
🤣3❤1🥰1
Ну так вот... Когда спешите — очевидно, шанс ДТП сильно выше 🤨 А это создаёт пробки. Вот так было вчера на мне. Сами понимаете. Думайте.
✍2🫡2
Молодёжь, обратите внимание: Донгузская, как и я, на нехилом таком участке теперь тоже сузилась вполовину ‼️ Дело в ремонте дороги, конечно 🥸 Так что едем тихо, не спеша, не шурша... В следующей публикации покажу, что бывает, когда вы едете наоборот — в спешке...
❤2
Думаете, я один такой мост, который обновится на Донгузской? Как бы не так 😏 Говорят, что уже вовсю ищут подрядчика на ремонт путепровода над Беляевской. Тоже немолодой — 1976 год, шутка ли... Давно пора. От будущего подрядчика потребуют провести проектно-изыскательские и строительно-монтажные работы: замена крайних балок, замена барьерного ограждения, замена асфальта и гидроизоляции, замена железобетонных конструк…
👏1
🧐 Иногда читаю комментарии каких-то умников, мол: "Сегодня мимо проезжал, опять рабочие ничего не делают, фелонят только..." А на этом видео что тогда? 😤 С начала мая фиксировал, как работают мужики, посмотрите... Честь и хвала им! За их труд!!!
❤2🔥1
Горжусь своим сыном 💪 Ему, вон, уже полимерку эпоксидную стелят. Не отстаёт! Тоже хорошеет! Видео прислала подписчица Настя.
👍3
Утро доброе, молодёжь 🥸 Ещё с 31 июля вы меня спрашивали, как там ситуация с открытием... Ну вот теперь-то по мне можно проехать, хе-хе-хе! Правда, другой момент был утром: из-за ДТП на подъездах ко мне образовались пробочки... До сих пор тут трафик слегка напряжённый. Будьте осторожны на дороге, шибко не спешите!
👍1🔥1
Ну мужики! С праздником вас! 🤝 Спасибо за защиту Родины, гордимся каждым, кто служил в ВДВ 🫡
❤3🫡1
Showing the 12 most recent of 16 posts we hold for @mostik56. 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.
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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“ОренРуль” (@mostik56), 194 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/mostik56.
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.