Рабочий чат : https://t.me/+Hq6DjRmLnog3MWMy , давно стоило старый чат удалить
Signed Инженер-коммунист. Ярославль. им.тов.Демахина Д)

Channel
@marxist_yaroslavl
On this record: Topic · Growth · Engagement · Reactions · Posts · Polls · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
265subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001432546885 |
|---|---|
| Type | Channel |
| Username | @marxist_yaroslavl |
| Created | 23 December 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/marxist_yaroslavl |
Politics & activism — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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, 23:57 | 265 | +1 |
| 7 Sept 2026, 08:20 | 264 | -2 |
| 30 Aug 2026, 06:22 | 266 | +1 |
| 22 Aug 2026, 12:24 | 265 | -1 |
| 7 Aug 2026, 05:33 | 266 | no change |
| 7 Aug 2026, 05:24 | 266 | first reading |
19 posts held, back to 13 January 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 19 posts for this entry, the most recent from 3 March 2026. An engagement rate over an empty window would be a number about nothing.
111 reactions across 16 posts, in 15 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 37 | 33.3% | |
| 🔥 | 22 | 19.8% | |
| ❤ | 15 | 13.5% | |
| 👏 | 10 | 9.01% | |
| 🤔 | 7 | 6.31% | |
| 😁 | 6 | 5.41% | |
| 🤡 | 3 | 2.70% | |
| 🥰 | 3 | 2.70% | |
| 🕊 | 2 | 1.80% | |
| 👎 | 1 | 0.901% | |
| 💔 | 1 | 0.901% | |
| 😭 | 1 | 0.901% | |
| 🤓 | 1 | 0.901% | |
| 🤬 | 1 | 0.901% | |
| 🫡 | 1 | 0.901% |
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 16 of the 19 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 111 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 13 January 2026 to 3 March 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.
Рабочий чат : https://t.me/+Hq6DjRmLnog3MWMy , давно стоило старый чат удалить
Signed Инженер-коммунист. Ярославль. им.тов.Демахина Д)
7-9 марта планируем встречу нашего клуба в Ярославле. Предлагайте темы по управлению, инженерии, образованию и даты Актуальные нам темы: стоит ли работать там, где нет базового комфорта, безопасности ? - нытики, критиканы или предлагающие изменения и альтернативы? И #мем от товарищей https://t.me/inefficient_manager/2626 #встреча #тема #Ярославль Тест, резерв в MAX : https://max.ru/join/4tjz2PYMMNYcLBV-jsgKiFd9Bc6…
👍3❤2
Скоро предприниматели должны будут следить за браками и деторождением своих наемных работников по ТК? Руководители, Вы будете этим заниматься ? Сотрудники, согласны что начальство будет контролировать ваши браки и деторождение ? Цели поста, репоста: 1. Познакомить с каналом #БудьПрофи : https://t.me/bee_profi48 : "Надежда Новикова. Управляю персоналом, управляю агентством, пишу про людей и про работу." 2. Дать возмо…
👍4🤔1
Узнали больше друг о друге, об инженерах, управленцах, юристах, музыкантах, архитекторах, it-шниках на встрече нашего клуба в Ярославле 18.2. Спасибо участникам и клубу https://t.me/spiritsoundbase Теперь планируем 13.3 экскурсию на завод станков ЧПУ в Москве и встречу с единомышленниками в Москве - https://t.me/erptoc/562. Пока еще есть 6 мест на экскурсию. #встреча #СовмещаемНесовместимое "Управленец не обязан бы…
🔥4❤2👍2
18.02 в Ярославле презентация инженерно-управленческого рок-клуба им тов Демахина.(Неэффективный менеджер) и ДР Виктора Смирнова Цели клуба: объединение инженеров, управленцев, специалистов для взаимодействия, обсуждения проблем, поиска решений, взаимной поддержки, организации совместного досуга. Для участия пишите админу канала Виктору Смирнову @tovarich_Filatov , в комментариях, в сообщениях каналу. Место встреч…
👍7
Signed Инженер-коммунист. Товарищ Ярославский
Posted without readable text
❤1
Channel name was changed to «Инженер-коммунист. Товарищ Ярославский #ДефицитКадров»
#НашиПланы : 18.2 День рождения нашего товарища Виктора Смирнова @tovarich_Filatov . И сейчас обдумываем, что лучше организовать к его ДР в Ярославле, возможно в выступлением Виктора по нашим темам, по презентации инженерно-управленческого рок-клуба в Ярославле https://t.me/erptoc/475 ). Ждем и ваших идей и предложений)! Остальные наши планы: - 31.1-1.2 встречи с друзьями в центре Ярославле -6-8.2 мы в Москве https…
🔥7❤1
Signed Инженер-коммунист. Товарищ Ярославский
Приглашаем авторов, коментаторов к взаимодействию)! В нашем чате проголосовать в публичном опросе по взаимодействию https://t.me/c/2981311093/3682 #опрос #инженер_коммунист #подписчики #участники #СовмещаемНесовместимое ("Управленец не обязан быть коммунистом, но коммунист обязан быть управленцем!)"
👍2❤1🫡1
Инженер-коммунист. Товарищ Ярославский #ДефицитКадров pinned «Это наш основной канал https://t.me/erptoc , где мы говорим и про #Дефицит Кадров. Ждем Ваших подписок, комментариев и обращений там, товарищи»
Это наш основной канал https://t.me/erptoc , где мы говорим и про #Дефицит Кадров. Ждем Ваших подписок, комментариев и обращений там, товарищи
🔥3❤2👍1
Signed Инженер-коммунист. Товарищ Ярославский
Сегодня 18.01 едем на Технохутор под Ярославлем! ❄️ Поговорим о темах, которые мы поднимали: малоэтажное строительство - https://t.me/erptoc/404 , выгорание - https://t.me/erptoc/288 , развитие малого бизнеса и перспективы туризма, варианты взаимодействия и сотрудничества в малом и среднем бизнесе. Пишите ваши вопросы в комментариях. https://t.me/tehnohutor : 📅 Что ждёт вас в Технохуторе в 2026 г? Фестиваль Музыки …
👍5❤2
Signed Александр Вьюшин-Ярославский
Showing the 12 most recent of 19 posts we hold for @marxist_yaroslavl. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Я
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 19 most recent posts we hold, published 13 January 2026 to 3 March 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
@marxist_yaroslavl named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 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.
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.
“Инженер-коммунист. Товарищ Ярославский #ДефицитКадров” (@marxist_yaroslavl), 265 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/marxist_yaroslavl.
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.