Channel
@zakon_guru_tg
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,944subscribers
-8 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001595292925 |
|---|---|
| Type | Channel |
| Username | @zakon_guru_tg |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/zakon_guru_tg |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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 |
|---|---|---|
| 19 Sept 2026, 06:37 | 1,944 | +1 |
| 14 Sept 2026, 23:37 | 1,943 | -3 |
| 5 Sept 2026, 22:57 | 1,946 | -6 |
| 30 Aug 2026, 00:43 | 1,952 | -1 |
| 26 Aug 2026, 16:12 | 1,953 | +1 |
| 19 Aug 2026, 11:57 | 1,952 | +1 |
| 16 Aug 2026, 20:47 | 1,951 | -3 |
| 13 Aug 2026, 04:25 | 1,954 | +1 |
| 9 Aug 2026, 20:33 | 1,953 | +1 |
| 7 Aug 2026, 01:57 | 1,952 | no change |
| 7 Aug 2026, 00:31 | 1,952 | first reading |
17 posts held, back to 16 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 2 pages 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 17 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
50 reactions across 13 posts, in 4 distinct kinds. The most used accounts for 54.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 27 | 54.0% | |
| 🔥 | 17 | 34.0% | |
| 😁 | 4 | 8.00% | |
| ❤ | 2 | 4.00% |
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 17 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 50 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 16 July 2026 to 6 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.
Существенные изменения в ППРФ 1875 вносятся Постановлением Правительства Российской Федерации от 03.08.2026 № 969 "О внесении изменений в некоторые акты Правительства Российской Федерации" В ближайшее время обновим "цветную редакцию" ППРФ 1875 и сервис поиска по его позициям. Информация будет доведена в ближайшее время.
👍1
Три главных страха поставщика или просто у нас пятниШное настроение 🥳. Всем быстрейшего окончания рабочей недели и хороших выходных!
😁4
НМЦ до НГ на ГСМ считается самостоятельно. Ответственность за завышение цены заказчики также несут самостоятельно.
https://vkvideo.ru/video-190749134_456239217
Изменения в 44-ФЗ, вносимые 2 законопроектами, приняты в третьем чтении ГД РФ. Это означает, что вопрос нескольких дней, когда они будут приняты окончательно. Посмотреть и подготовится к нововведениям можно в методическом пособии, указанном выше. Краткое содержание того, что меняется: Законопроект № 1286425-8 🟡 Со дня опубликования Ст. 93 (ч.15) — разрешено заключать несколько контрактов на однородные/идентичные т…
👍5🔥3
«Цветная редакция» 44-ФЗ со всеми изменениями, которым ещё предстоит вступить в силу. Скачать можно здесь: https://zakon.guru/Materialy. Нововведения и не только разберём на предстоящих семинарах в сентябре в Москве. Увидимся!
👍3
Калькуляторы расчета неустойки с заказчика и поставщика по 44-ФЗ обновлены в связи с изменением ЦБ РФ ключевой ставки с 27.07.2026 до 14% Ссылки на обновленные калькуляторы: https://zakon.guru/calc44fz-zakazchik https://zakon.guru/calc44fz-postavchik Приятного использования 🥰
👍2
Получили ответ Минфина России по данному вопросу: ответ на данный вопрос компетенция Минпромторга России - теперь ждем ответ от них.
👍2❤1
Обновили функционал поиска аналогичной требования заказчика по 44-ФЗ продукции. Аналоги ищутся преимущественно на сайтах производителей и дистрибьютеров, а не на маркетплейсах. Дополнительно выгружены контакты производителей, которых нет в реестре российской продукции. Надеемся, что для поставщиков по 44-ФЗ функционал окажется максимально полезным. Протестировать можно уже сейчас в пробной версии https://zakon.guru/a…
👍4
Мы посоветоваться. Кому-то нужен сервис по проверки санкций в отношении юр.лиц по наименованию, ИНН, ОГРН? Сидим вот и думаем. Заказчики, которые работают по 223-ФЗ и ПП 301 и так, видимо, знают, что санкции есть и нельзя размещать свои закупки в открытом доступе, но может быть что-то не учли? Ждем комментарии.
Обновлен график очных мероприятий Центра «Закон.гуру» в Москве и в Санкт-Петербурге. В программах гособоронзаказ, 44-ФЗ, 223-ФЗ, закупки строительства, нацрежим, работа с реестрами и многое другое. Ссылка: https://zakon.guru/seminar/
Центр "Закон.гуру" выступит организатором Всероссийского форума "ГОСЗАКУПКИ 360°". Мероприятие пройдет очно в Москве 24 ноября текущего года. Наши подписчики в приоритетном порядке могут подать заявку и принять участие в Форуме в качестве докладчика. Заявки принимаются по адресу [email protected] (тема письма - ГОСЗАКУПКИ 360°). В письме укажите ФИО и должность полностью, а также предлагаемую тему для выступления.
🔥2❤1
Showing the 12 most recent of 17 posts we hold for @zakon_guru_tg. 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.
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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Госзакупки 44-ФЗ, 223-ФЗ и B2B | ЗАКОН.ГУРУ” (@zakon_guru_tg), 1,944 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/zakon_guru_tg.
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.