Channel
@mingkhyakutia
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
1,056subscribers
-15 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001704720727 |
|---|---|
| Type | Channel |
| Username | @mingkhyakutia |
| Created | 28 February 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/mingkhyakutia |
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 19 September 2026 and assigned it the closest of 31 fixed categories, at 82% 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, 07:37 | 1,056 | +1 |
| 11 Sept 2026, 14:02 | 1,055 | -5 |
| 6 Sept 2026, 14:20 | 1,060 | -1 |
| 2 Sept 2026, 07:53 | 1,061 | -6 |
| 30 Aug 2026, 07:16 | 1,067 | +2 |
| 20 Aug 2026, 18:02 | 1,065 | -1 |
| 17 Aug 2026, 10:54 | 1,066 | -4 |
| 13 Aug 2026, 17:35 | 1,070 | +2 |
| 10 Aug 2026, 17:11 | 1,068 | -2 |
| 7 Aug 2026, 07:31 | 1,070 | -1 |
| 6 Aug 2026, 12:36 | 1,071 | no change |
| 6 Aug 2026, 09:38 | 1,071 | first reading |
8 posts held, back to 7 May 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 8 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
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 2 of the 8 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 7 May 2026 to 1 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.
ГУП «ЖКХ РС(Я)» исполнило обязательства по облигациям серии БО-на 2.53 млрд рублей, избежав дефолта 31.07.2026 ГУП «ЖКХ РС(Я)» погасило 2 395 376 облигаций серии БО-01 и исполнило обязательства по выплате 28-го купона. Обязательства перед инвесторами исполнены в полном объеме до истечения установленного законом льготного периода (grace period) на исправление технического дефолта.
По поручению Главы Якутии Айсена Николаева, данному в ходе «Прямой линии» 27 апреля, задолженность по заработной плате перед работниками ГУП «ЖКХ РС(Я)» будет полностью погашена до 14 мая 2026 года. 🔹 Как сообщил на брифинге министр жилищно-коммунального хозяйства и энергетики РС(Я) Вячеслав Емельянов, Правительство республики приняло Распоряжение об увеличении лимита субсидирования отрасли на 1,5 млрд рублей. Средс…
Уважаемые ветераны и жители Республики Саха (Якутия)! От имени Министерства ЖКХ и энергетики РС(Я) и от себя лично сердечно поздравляю Вас с Днём Великой Победы! Сегодня мы отмечаем 81-ю годовщину Победы в Великой Отечественной войне — события, которое навсегда останется в сердцах нашего народа и вписано в историю каждой семьи. В этот священный день мы с глубоким уважением и благодарностью вспоминаем тех, кто сраж…
Сегодня в Зале Республики Глава Якутии вручил диплом выпускнику первого потока кадровой программы «Якутия — земля героев» Титу Ивановичу Захарову — инженеру-технологу водоочистных сооружений Покровска АО «Водоканал», участнику специальной военной операции. Накануне, 6 мая, он успешно защитил выпускную работу. Как справедливо сказал сегодня на церемонии Айсен Сергеевич, наши бойцы доказали верность Родине в бою, а се…
В Республике Саха (Якутия) продолжается предварительный отбор по включению в Реестр квалифицированных подрядных организаций 📥 Министерство жилищно-коммунального хозяйства и энергетики Республики Саха (Якутия) начинает прием заявок от подрядных организаций для участия в предварительном отборе на II квартал 2026 года. 📋 Все организации, прошедшие предварительный отбор, будут включены в Реестр квалифицированных подряд…
Коллектив Министерства жилищно-коммунального хозяйства и энергетики Республики Саха (Якутия) принял участие во Всероссийской акции «Свеча памяти» 📅 Накануне 81-й годовщины Победы, сотрудники ведомства вышли на площадь Победы в Якутске, чтобы вместе с жителями города почтить память героев Великой Отечественной войны. 🙏 Собравшиеся почтили память павших общей минутой молчания. Сразу после неё участники зажгли тысячи …
❤1
Сегодня, 7 мая, коллектив Министерства ЖКХ и энергетики РС(Я) присоединился к общегородскому субботнику. ♻️ В преддверии Дня Победы сотрудники министерства дружно вышли на уборку закреплённой территории. ✅ Убрали мусор, очистили территорию от прошлогодней травы и листьев. Прилегающая территория заметно преобразилась, участники субботника внесли свой вклад в чистоту родного города.
Провёл совещание с главами районов и руководителями ресурсоснабжающих организаций. Главный вопрос — готовность ресурсоснабжающих организаций к прохождению паводкоопасного и пожароопасного сезонов 2026 года. Подготовка к прохождению паводкоопасного и пожароопасного сезонов проходит в штатном режиме, в соответствии с решениями, принятыми республиканской Комиссией по ЧС, и распоряжением Правительства. В рамках данной…
Showing the 8 most recent of 8 posts we hold for @mingkhyakutia. 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.
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 1 registered channel — 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.
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.
“Министерство ЖКХ и энергетики Якутии” (@mingkhyakutia), 1,056 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/mingkhyakutia.
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.