Telegram RegisterThe public register of Telegram

Channel

УЦ ФК

@uc_fk

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

5,528subscribers

-2 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001448075535
TypeChannel
Username@uc_fk
DescriptionОфициальный канал Удостоверяющего центра Федерального казначейства
Created30 July 2020measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live11 August 2026
Measurements held3
Confirmed unchanged2 times, most recently 11 August 2026
On Telegramt.me/uc_fk

Growth

5,5285,5305,5296 August 2026 — 5,530 subscribers6 August 2026 — 5,530 subscribers8 August 2026 — 5,528 subscribers6 August 20268 August 2026
3 measurements spanning 3 days, net -2. 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 5,528–5,530 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 23:015,528-2
6 Aug 2026, 03:355,530no change
6 Aug 2026, 02:075,530first reading

Engagement

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

ERR · 30 days
23.3%
avg views ÷ 5,528 subscribers
Avg views / post
1,290
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 12 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 31 July 2026
Posts held12 (12 January 202631 July 2026)
Views total1,290
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 04:09 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

Photos
270
Videos
7
Links
319

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

31 Jul 2026, 19:47 UTC≈1,290 viewsread 12 August 2026
Forwarded from @ep_uc

✍️6 лет Порядку УЦ ФК 6 лет назад, 31 июля 2020 года, вступил в силу Порядок реализации Федеральным казначейством функций аккредитованного УЦ, утвержденный приказом Федерального казначейства от 16.03.2020 № 11н. Приказ 11н стал первым НПА госУЦ, разработанным на основании Требований к порядку УЦ от Минцифры, позднее был заменён 21н, но стал основой для других госУЦ по разработке своих Порядков УЦ. 6 лет назад имен

19 Jun 2026, 17:35 UTC≈2,740 viewsread 12 August 2026
Forwarded from @ep_ucPhoto

🔐 Экспертный совет по вопросам внедрения и использования электронной подписи и сертификатов безопасности В разделе Координационно-совещательные органы официального сайта Минцифры России создана страница Экспертного совета по вопросам внедрения и использования электронной подписи и сертификатов безопасности. Совет воссоздан приказом Минцифры от 09.12.2025 № 1157 и призван стать ключевой площадкой для диалога между р

4 Jun 2026, 05:45 UTC≈3,230 viewsread 12 August 2026
Forwarded from @ep_ucPhoto

📊 Топ-10 аккредитованных удостоверяющих центров: Госключ рвётся к лидерству За 5 месяцев 2026 года выдано 8,18 млн. сертификатов - на 20% больше, чем год назад. Топ-10 АУЦ стабильно контролируют >91% всей выдачи сертификатов в стране (статистика за аналогичный период прошлого года по ссылке). 🚀 ИнфоТеКС ИТ взлетел со 886 тыс. до 1,83 млн. - рост квалифицированных сертификатов Госключа более чем вдвое. Отрыв от лиде

16 Apr 2026, 05:35 UTC≈4,190 viewsread 12 August 2026
Forwarded from @ep_ucPhoto

Про токены и аппаратную поддержку новых ГОСТ шифрования Данная информация должна озвучиваться на проходящих конференциях и транслироваться дальше в широкие массы, но чего нет, того нет, поэтому спасибо вендорам и подписчикам, которые делятся информацией. Если с Рутокен ЭЦП 2.0 давно было понятно, поддержки нового ГОСТ там нет и вместо 2.0 рекомендован 3.0, то по JaCarta-2 ГОСТ информация появилась недавно: JaCarta-

6 Apr 2026, 05:06 UTC≈4,550 viewsread 12 August 2026
Forwarded from @ep_ucPhoto

📣 Юбилей Федеральному закону 63-ФЗ "Об электронной подписи" - 15 лет! Закон был подписан 6 апреля 2011 года и вступил в силу 8 апреля, заменил утративший силу ФЗ-1 от 10.01.2002 "Об электронной цифровой подписи", но не сразу. В изначальной редакции с целью обеспечения технических условий реализации требований 63-ФЗ действие 1-ФЗ подлежало прекращению с 1 июля 2012 г., но Федеральный закон от 10 июля 2012 г. № 108-Ф

29 Mar 2026, 14:44 UTC≈4,970 viewsread 12 August 2026
Photo

Начальник Управления режима секретности и безопасности информации Федерального казначейства Бражко В.С. 25.03.2026 принял участие в работе тематической секции "Информационные системы государства, кибербезопасность и криптография" XXVIII научно-практической конференции РусКрипто и выступил с докладом "Обеспечение информационной безопасности в Федеральном казначействе", в ходе которого рассказал о перспективных направл

20 Mar 2026, 16:40 UTC≈4,890 viewsread 12 August 2026
Forwarded from @ep_uc

🚀В Госдуму внесён законопроект № 1182063-8 "О внесении изменений в Федеральный закон "Об электронной подписи": 🔹22 страницы изменений 🔹6 приказов к изменению (3 Минцифры, по одному у ФСБ, Минфина и ФНС) 🔹0 руб. бюджетных расходов ✍️"Об ЭП и УЦ"

3 Mar 2026, 03:50 UTC≈7,270 viewsread 12 August 2026
Forwarded from @ep_ucPhoto

Обновление Портала заявителя Удостоверяющего центра Федерального казначейства

27 Feb 2026, 10:01 UTC≈14,900 viewsread 12 August 2026

📣2 марта в 19:00 по МСК будет осуществляться обновление версии Портала заявителя. В рамках обновления будет осуществлен переход на новый дизайн Портала заявителя и обновлен процесс подачи запроса на сертификат (изменены шаги подачи запроса). Для уменьшения возможных ошибок рекомендуем завершить подачу всех ранее созданных запросов на получение сертификата до обновления версии системы. В новой версии портала будет

3 Feb 2026, 05:25 UTC≈9,270 viewsread 12 August 2026
Forwarded from @ep_ucPhoto

⚠️ КриптоПро CSP 4.0: УЦ Федерального казначейства отклоняет запросы на сертификаты С 2 февраля 2026 года все запросы на получение сертификатов, сгенерированные с использованием КриптоПро CSP версии 4.0, УЦ ФК отклоняются. 🔸 КриптоПро CSP версии 4.0 не имеет действующего сертификата соответствия (истек 15.01.2026). 🔸 Для работы с КЭП обязательны сертифицированные сборки версии 5.0: ✅ КриптоПро CSP 5.0.11455 ✅ Крипт

20 Jan 2026, 15:45 UTC≈14,400 viewsread 12 August 2026
Photo

📣О тиражировании СКЗИ КриптоПро CSP 5.0 R3

12 Jan 2026, 10:10 UTC≈14,600 viewsread 12 August 2026
File

Списки отозванных сертификатов УЦ ФК

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

Citation-graph rank

Citation-graph rank — 429,454 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

Mentions

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.

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.

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

“УЦ ФК” (@uc_fk), 5,528 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/uc_fk.

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.