Telegram RegisterThe public register of Telegram

Channel

ДРКС-экспресс

@drcs_express

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

2,321subscribers

-3 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001300491200
TypeChannel
Username@drcs_express
Created17 September 2020measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/drcs_express

Growth

2,3212,3242,322.57 August 2026 — 2,324 subscribers7 August 2026 — 2,324 subscribers10 August 2026 — 2,323 subscribers13 August 2026 — 2,321 subscribers7 August 202613 August 2026
4 measurements spanning 6 days, net -3. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 2,321–2,324 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 11:242,321-2
10 Aug 2026, 04:312,323-1
7 Aug 2026, 04:532,324no change
7 Aug 2026, 04:462,324first reading

Engagement

18 posts held, back to 9 April 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
12.6%
avg views ÷ 2,321 subscribers
Avg views / post
292
2 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
2
of 18 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 July 2026
Posts held18 (9 April 202616 July 2026)
Views total583
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 16:40 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
15s
Average length
15s

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.

Reaction mix

22 reactions across 9 posts, in 5 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1150.0%
👍731.8%
👎29.09%
👌14.55%
🤬14.55%

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 9 of the 18 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 22reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 9 April 2026 to 16 July 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.

Recent posts

16 Jul 2026, 08:26 UTC293 viewsread 7 August 2026
Forwarded from @kristazakupki_44File

File, posted without a caption

16 Jul 2026, 08:26 UTC290 viewsread 7 August 2026
Forwarded from @kristazakupki_44Photo

На стартовой странице в разделе "Новости" размещена информация в максимально схематичном виде "Ведение реестра контрактов по ЗМО с 01.07.2026г.", а также прикреплена ниже ⤵️

19 Jun 2026, 07:10 UTC746 viewsread 7 August 2026
Forwarded from @drcs_kk

❗️Уважаемые коллеги! Обращаем ваше внимание на то , что сайты доменной зоны *.krasnodar.ru (в том числе сайт департамента и РИССЗ КК) теперь используют сертификат, выданный удостоверяющим центром Министерства цифрового развития, связи и массовых коммуникаций Российской Федерации. В случае, если ваш браузер сообщает о небезопасном подключении, необходимо произвести установку корневых сертификатов Министерства цифров

18 Jun 2026, 13:10 UTC600 viewsread 7 August 2026
Forwarded from @drcs_kk

В рамках методологического сопровождения деятельности заказчиков департаментом направлена информационная рассылка об изменениях законодательства о контрактной системе с 01.07.2026. С 01.07.2026 вступают в силу положения Закона № 44-ФЗ, предусматривающие обязанность включения в реестр контрактов, информации о контрактах, заключенных в том числе в соответствии с п. 4, 5, 23, 42, 44 и 46 ч. 1 ст. 93 Закона № 44-ФЗ, а

9 Jun 2026, 11:15 UTC522 views1 reactionsread 7 August 2026
Forwarded from @kristazakupki_44Photo

❗️При возникновении подобных ошибок при выгрузке документов, содержащих вложения, прикрепленные 08.06.2026, а также при попытке скачиваний таких вложений, необходимо аннулировать данный документ и приложить его заново

1

9 Jun 2026, 07:35 UTC454 views1 reactionsread 7 August 2026
Forwarded from @kristazakupki_44

🟢 Работа системы восстановлена, файлы прикладываются, выгрузка в ЕИС активна

👍1

9 Jun 2026, 06:47 UTC545 viewsread 7 August 2026

РИССЗ КК будет недоступна ориентировочно 2 часа (возможно, меньше). ЦИТ проводит восстановительные работы

4 Jun 2026, 11:28 UTC595 views2 reactionsread 7 August 2026
Forwarded from @kristazakupki_44

❗️ В ближайшее время будет произведена перезагрузка системы

👎2

4 Jun 2026, 08:00 UTC635 viewsread 7 August 2026
Forwarded from @kristazakupki_44Photo

🛑Наблюдается медленная работа системы, ведутся работы по устранению проблемы

1 Jun 2026, 06:57 UTC≈1,480 views2 reactionsread 7 August 2026

📊 Подготовлен Сводный аналитический отчёт по госзакупкам Краснодарского края за 2025 год! Ежегодно департамент проводит масштабный мониторинг государственных закупок края — это фундамент для оценки эффективности расходования бюджетных средств и развития контрактной системы. Теперь результаты работы за 2025 год доступны всем в ЕИС. Из отчёта вы узнаете: 🔹 Как развивалась контрактная система края в условиях экономиче

1👍1

7 May 2026, 07:07 UTC826 views2 reactionsread 7 August 2026
Forwarded from @kristazakupki_44Photo

При обратной интеграции (размещенного напрямую в ЕИС) заключенного контракта (проекта контракта) возникает ошибка, дублируются объекты закупок. Исправление планируется ориентировочно в 12:00 мск. До исправления загрузка проектов контракта отключена. При формировании проектов контракта в РИС данной ошибки не наблюдается.

1👌1

5 May 2026, 12:02 UTC789 viewsread 7 August 2026
Forwarded from @kristazakupki_44Photo

❌ Массово возникают ошибки, причины выясняются

Showing the 12 most recent of 18 posts we hold for @drcs_express. 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.

Forward network

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.

Cite this entry

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 August 2026 — this entry's latest reading, not the date you are reading this.

“ДРКС-экспресс” (@drcs_express), 2,321 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/drcs_express.

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.