Channel
@rudenskofficial
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
642subscribers
+26 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001621424360 |
|---|---|
| Type | Channel |
| Username | @rudenskofficial |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/rudenskofficial |
Other / unclassifiable — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 78% 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 |
|---|---|---|
| 13 Sept 2026, 05:56 | 642 | +7 |
| 5 Sept 2026, 11:37 | 635 | +9 |
| 29 Aug 2026, 13:03 | 626 | +7 |
| 23 Aug 2026, 11:26 | 619 | +1 |
| 15 Aug 2026, 16:08 | 618 | +2 |
| 8 Aug 2026, 03:02 | 616 | no change |
| 7 Aug 2026, 17:38 | 616 | first reading |
7 posts held, back to 5 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 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 7 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 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.
52 reactions across 6 posts, in 5 distinct kinds. The most used accounts for 46.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 24 | 46.2% | |
| 🔥 | 9 | 17.3% | |
| 👏 | 8 | 15.4% | |
| ❤ | 6 | 11.5% | |
| 🤝 | 5 | 9.62% |
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 6 of the 7 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 52 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 5 August 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.
📹 ВИДЕОФАКТ ➡️ Таким был двухдневный практический тренинг для заместителей руководителей по закупкам ведущих промышленных предприятий Беларуси на базе ОАО "Руденск" 📌 Сегодня участники тренинга встретятся с Министром промышленности Андреем Кузнецовым, где обсудят применение полученного опыта на предприятиях отрасли.
🔥7👏1
➡️ Завершающим этапом обучения стала экскурсия по цеху производства рефлекторов и автомобильных фар с демонстрацией работы действующей Производственной ячейки по сборке блок-фар для «Газели NN». 🤝 Директор ОАО "Руденск" Андрей Солонович выражает благодарность представителям АО «НПК» и технологической службе предприятия за подготовку и проведение практического тренинга для заместителей руководителей по закупкам веду…
👍7🤝5👏2
Участники обучения решали реальную производственную задачу ОАО "Руденск" совместно со специалистами технологической службы предприятия, которым предстоит завершить внедрение, оценить реальный производственный эффект и продолжить улучшения. Итогом стала защита проекта перед директором ОАО "Руденск" Андреем Солоновичем. ➡️ Основной вывод: инструменты Производственной системы работают и дают практический эффект, подход…
👏5👍2❤1
✅ В течение двух дней участники практического тренинга осваивали инструменты Производственной системы «Группы ГАЗ» на базе ОАО "Руденск" 1️⃣ С первого дня команды были погружены в реальный производственный процесс: наблюдали за операторами, анализировали текущие процессы, фиксировали неэффективные движения и потери, предлагали улучшения. 2️⃣ Во второй день перешли к внедрению предложений по оптимизации производств…
👍4🔥2
🟡Президент Беларуси поздравил личный состав и ветеранов транспортных войск с профессиональным праздником - Днем железнодорожных войск. "Славные традиции белорусских военных железнодорожников тесно связаны с историей первых специализированных воинских подразделений, созданных в Барановичах 150 лет назад. При этом каждый этап становления и развития железнодорожных войск был отмечен высокой боевой выучкой, самоотверже…
⚡️⚡️ Второй день обучения начался с организации производственной ячейки в соответствии с целевой планировкой 📌 Участникам предстоит продумать как расставить столы, установить их по схеме, закрепить склизы, расставить ложементы по рабочим местам и подготовить тару для деталей.
👍5
Подсмотрели за процессом обучения 👀 ✔️После теории — к практике. ➡️ Участники анализируют текущее состояние выделенной производственной ячейки: внимательно наблюдают за работой операторов на каждом рабочем месте, выявляют потери и проблемы при выполнении операций, предлагают решения по оптимизации рабочих процессов. 💬 Как результат — идеи кооперационных решений, направления работы с внутренними поставщиками, основ…
👍6❤5
Showing the 7 most recent of 7 posts we hold for @rudenskofficial. 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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“ОАО "Руденск"” (@rudenskofficial), 642 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/rudenskofficial.
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.