Channel
@lysenok56
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
3,301subscribers
-4 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001181149558 |
|---|---|
| Type | Channel |
| Username | @lysenok56 |
| Created | 16 May 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 13 August 2026 |
| On Telegram | t.me/lysenok56 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 00:30 | 3,301 | -3 |
| 7 Aug 2026, 05:51 | 3,304 | -1 |
| 6 Aug 2026, 06:22 | 3,305 | first reading |
13 posts held, back to 25 February 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof 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 13 posts for this entry, the most recent from 26 February 2024. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
719 reactions across 13 posts, in 18 distinct kinds. The most used accounts for 36.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤬 | 262 | 36.4% | |
| 👍 | 127 | 17.7% | |
| 🔥 | 61 | 8.48% | |
| 🤣 | 45 | 6.26% | |
| 👏 | 40 | 5.56% | |
| 🆒 | 32 | 4.45% | |
| 👌 | 32 | 4.45% | |
| 😱 | 26 | 3.62% | |
| ❤ | 23 | 3.20% | |
| 🙈 | 21 | 2.92% | |
| 👀 | 15 | 2.09% | |
| 😁 | 13 | 1.81% | |
| 🤯 | 6 | 0.834% | |
| 😢 | 5 | 0.695% | |
| ❤🔥 | 4 | 0.556% | |
| 🤔 | 4 | 0.556% | |
| 🎉 | 2 | 0.278% | |
| 👎 | 1 | 0.139% |
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 13 of the 13 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 719reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 25 February 2024 to 26 February 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
На Салмина болт кладут все, кому не лень... Ну кроме бывшего демократа Куниловского... Предприниматели не исключение... Помните Салмин говорил, что ведёт активную работу с предпринимателями по теме гололёда?!! Смотрите... Вот результаты... #пишутвчате... Проспект Парковый дом 13 с торца дома коммерсанты, магазины и страшный гололёд, колеи. Вопрос кто должен привести в порядок эту территорию?!
🤬58👍32❤11🔥4❤🔥3🤯1
🤔🤔🤔 Ситуацию в городе мои подписчики назвали "Ледовым побоищем"... Только вот не совсем понятно, кто в этой битве Александр Невский, а кто воины-чуди... Если судить по аналогии потерь, то в в роли шведов и литовцев Салмин воспринимает жителей города... А вот себя, согласно татух, считает Александром Невским... Вопрос лишь в одном... С какой стороны глянуть?!! Перефразирую великого Булгакова... Сегодня ты Александр Н…
🔥26👍10🤬8😁3❤1👌1🆒1
За минувшую неделю в травмпунктах Оренбурга было зафиксировано 1211 обращений граждан с травмами различного характера. В числе наиболее частых причин обращения - переломы конечностей, ушибы и сотрясения мозга
🤬61🙈5👏4👌2👍2🆒2❤🔥1
На улице Кольцевой так и не сносят аварийную пятиэтажку... Хотя ранее подрядчиками было обещано "начать завтра"... В тот момент, когда опровергали мое предположение о расторжении контракта...
👌19🙈8🆒2
Салмин - это тот, кто боится не только за свои слова, но и за действия получить в морду... Как и в случае с видеосовещанием с Паслером на "Телевышке" за него отдуваться будет совершенно не профильный заместитель Алексей Кудинов... Напомню, что зона ответственности за уборку снега и борьбу с гололедом, в соответствии с предложенной им же Структурой администрации города, полностью лежит на нем и главах округов...
👍25❤5🆒3👀2👎1
Рядом с домом ангелов ограждают очередной исторический особняк... Сносить будут?!!
🤬41😢5👍3🎉2🤯1
На самом деле, никаких двух увольнений Давыденко не было... Случилось невозможное... Сначала он написал заявление, потом по слухам, мормоны сказали, что еще пободаемся и он забрал заявление и ушёл на больничный... Была надежда, что в дело вмешается Бережицкий... Но... Если верить коллегам, то у него самого проблемы посерьёзнее, чем глава округа в Оренбурге... Лишний раз светиться из-за #хозяйственнаяимпотенция смысла…
🆒16👀9👌7❤3👍2😁2
👆👆👆 Первая жертва бесхозяйственности в городе... И не последняя... А кому-то еще и в ближайшие две недели предстоит уйти по утрате доверия...
🔥31👍7🤔4🆒2❤1
1️⃣2️⃣3️⃣ Глава Южного округа Оренбурга Владимир Давыденко уволился По какой причине оставил свой пост Владимир Давыденко не раскрывается. Бывший глава Северного округа Оренбурга Владимир Давыденко с октября прошлого года возглавил Южный округ, но продержался на этом месте недолго – без малого четыре месяца. Подробнее
👏36👀4👍3👌2😱2🆒2
🆘👆😱Фото хроника, состояния тротуаров в центральной части Оренбурга‼️
🤬40👍2😱2
😂😂😂 Интересный докУмент попался мне на днях... В общем... Для нестандартного позиционирования чиновников Игорь Сухарев, наш блогера-министр решил завести анонимный телеграм-канал... О чем сообщил по секрету всему свету через закрытую систему документооборота Правительства региона, скрепив это, как Кот Бегемот на современном уровне, электронно-цифровой подписью "УПЛОЧЕНО"... В общем, Игорь Николаевич решил собрать все…
🤣38🙈8👍6❤2😱1
15 линия в Оренбурге почищена
👍35😁7🆒3👌1
Showing the 12 most recent of 13 posts we hold for @lysenok56. 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 — 216,643 of 1,169,250entries 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.
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.
Named by 16 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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Lysenok” (@lysenok56), 3,301 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/lysenok56.
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.