Telegram RegisterThe public register of Telegram
Telegram profile photo for Об ЭП и УЦ

Channel

Об ЭП и УЦ

@ep_uc

On this record: Topic · Growth · Engagement · What this channel posts · Stars · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry

21,210subscribers

+8 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001555507916
TypeChannel
Username@ep_uc
Created20 September 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live4 October 2026
Measurements held35
Confirmed unchanged1 time, most recently 4 October 2026
On Telegramt.me/ep_uc

Topic

Technology — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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.

Growth

21,18321,24821,215.56 August 2026 — 21,202 subscribers6 August 2026 — 21,202 subscribers8 August 2026 — 21,216 subscribers8 August 2026 — 21,210 subscribers9 August 2026 — 21,209 subscribers10 August 2026 — 21,207 subscribers13 August 2026 — 21,212 subscribers14 August 2026 — 21,214 subscribers15 August 2026 — 21,207 subscribers17 August 2026 — 21,202 subscribers18 August 2026 — 21,196 subscribers19 August 2026 — 21,194 subscribers20 August 2026 — 21,192 subscribers21 August 2026 — 21,193 subscribers22 August 2026 — 21,190 subscribers24 August 2026 — 21,183 subscribers25 August 2026 — 21,184 subscribers26 August 2026 — 21,191 subscribers27 August 2026 — 21,213 subscribers28 August 2026 — 21,218 subscribers29 August 2026 — 21,214 subscribers30 August 2026 — 21,207 subscribers31 August 2026 — 21,204 subscribers1 September 2026 — 21,210 subscribers2 September 2026 — 21,203 subscribers3 September 2026 — 21,211 subscribers5 September 2026 — 21,210 subscribers9 September 2026 — 21,208 subscribers11 September 2026 — 21,204 subscribers13 September 2026 — 21,211 subscribers15 September 2026 — 21,217 subscribers17 September 2026 — 21,235 subscribers19 September 2026 — 21,248 subscribers27 September 2026 — 21,240 subscribers4 October 2026 — 21,210 subscribers21,2106 August 20264 October 2026
35 measurements spanning 60 days, net +8. 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 21,173–21,258 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
4 Oct 2026, 18:0221,210-30
27 Sept 2026, 01:0021,240-8
19 Sept 2026, 18:0021,248+13
17 Sept 2026, 06:1921,235+18
15 Sept 2026, 04:5721,217+6
13 Sept 2026, 15:2021,211+7
11 Sept 2026, 17:0121,204-4
9 Sept 2026, 04:1521,208-2
5 Sept 2026, 19:3721,210-1
3 Sept 2026, 16:1721,211+8
2 Sept 2026, 07:0721,203-7
1 Sept 2026, 07:1421,210+6
31 Aug 2026, 04:4421,204-3
30 Aug 2026, 05:1621,207-7
29 Aug 2026, 03:3421,214-4
28 Aug 2026, 06:4421,218+5
27 Aug 2026, 03:3421,213+22
26 Aug 2026, 04:2721,191+7
25 Aug 2026, 06:0621,184+1
24 Aug 2026, 09:2921,183first reading

Engagement

84 posts held, back to 30 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 64 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
8.55%
avg views ÷ 21,210 subscribers
Avg views / post
1,810
8 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
8
of 84 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 28 September 2026
Posts held84 (30 July 2026 – 28 September 2026)
Views total14,510
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Sept 2026, 14:07 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
1m 22s
Average length
27s

Measured directly from 3 videos 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.

Telegram Stars

Stars received
19
across the posts below
Posts paid on
2
of 84 we hold a reading for · 2%
Most on one post
13
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ep_uc. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 84 most recent posts we hold for this entry, published 30 July 2026 to 28 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Advertising

Ad load
1.19%
1 of 84 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
3,430
over 1 measured post
Median views · rest
3,050
over 83 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2SDnjdrDJFD111 August 202611 August 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 84 most recent posts we hold, published 30 July 2026 to 28 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

28 Sept 2026, 07:55 UTC≈1,150 viewsread 28 September 2026
Video

📣Айдентити Конф 2026 7 октября в Москве состоится Айдентити Конф - пленарная сессия посвящена автономным ИИ-агентам. Для представителей вендоров/интеграторов/дистрибьютеров — платное, для подписчиков канала действует Спецпромокод на скидку 10% - КЛЮЧ2026, его нужно ввести на сайте при регистрации. ✍️Телеграм-канал "Об ЭП и УЦ" третий раз выступает информационным партнёром конференции

28 Sept 2026, 05:30 UTC≈1,360 viewsread 28 September 2026
Photo

🏛 При краже пароля от «Госуслуг» необходимо блокировать банковские карты. Такое мнение у директора колледжа Всероссийского государственного университета юстиции, который уточняет, что следует ограничить доступ к счетам и обновить защитные комбинации на самом портале и связанных ресурсах. В противном случае злоумышленники смогут добраться до конфиденциальной информации пользователя. Юрист предупредил, что из-за бездей…

27 Sept 2026, 05:15 UTC≈1,730 viewsread 28 September 2026
Photo

📣Система адвокатуры и сертификаты Минцифры Ничего не понятно, но очень интересно. Собственно само письмо приведено выше, в нем сухая констатация, что с 1 октября шифрование каналов доступа будет с использованием сертификата Минцифры, а также информация о необходимости использования КриптоПро CSP 5.0 и браузера от Яндекса (кроме МВД и пользователей мобильных устройств). Описание напоминает переход на TLS-ГОСТ, как б…

26 Sept 2026, 19:11 UTC≈1,700 viewsread 28 September 2026
Photo

📈Самая полная статистика НУЦ В преддверии 15 тыс. действующих сертификатов НУЦ (при общем объеме выдачи в 33,5 тыс., 10 тыс. действующих были в середине июля) подготовлена самая полная статистика выдачи сертификатов НУЦ за 5 лет. ✍️Об ЭП и УЦ

26 Sept 2026, 05:45 UTC≈1,900 viewsread 28 September 2026
Photo

✍️Дело о "неподписанном" договоре одно из самых продолжительных по рассмотрению - здесь и признание "недействительной ЭЦП" и использование ключа ЭП после отзыва сертификата, суды идут с 2023 года доходя до Верховного. Судебная тяжба продолжается, новое заседание назначено на 6 ноября.

25 Sept 2026, 15:38 UTC≈2,070 viewsread 28 September 2026
Photo

✍️Тот момент, когда в запросе ясности было больше, чем в ответе.

25 Sept 2026, 05:30 UTC≈2,300 viewsread 28 September 2026
Photo

🏛 Судебная практика - "ключ под контролем хакера" или "а был ли взлом?" Можете представить, что хакеры, получив удаленный доступ до компьютера и обнаружив подключенный носитель с ключом ЭП, подадут за организацию декларацию уточнённую декларацию по НДС, которая будет убирать ранее указанный налоговый вычет? Я не могу, а наши суды могут - дело А40-290966/23, традиционные три инстанции. ООО оспаривало действия нало…

24 Sept 2026, 18:01 UTC≈2,300 viewsread 28 September 2026
Photo

Ростелеком - новый номинант премии "Профанация года". Нельзя писать так безграмотно (1, 2): 1. В стране 43 АУЦ. 2. Норма закона в отношении госУЦ вступила в силу 01.01.2022.

3 Sept 2026, 05:50 UTC≈1,720 viewsread 3 September 2026
Photo

⚡️Госуслуги - выбранный сертификат не подходит Руководитель организации использовал свой сертификат для аутентификации через ЕСИА, быстро и удобно, без подтверждения СМС. Но в один момент - ошибка, сертификат не подходит: войдите другим способом или выберите другой сертификат. Сертификат не истёк, ключ тоже (про встречающийся рассинхон времени действия ключей ЭП и сертификата рассказывать не нужно). Информативность …

2 Sept 2026, 16:46 UTC≈1,990 viewsread 3 September 2026

📣 Аккредитация УЦ 2026 В соответствии с решением Правительственной комиссии, уполномоченной на принятие решения об аккредитации удостоверяющих центров (протокол от 27.08.2026 № 4пр), продлена аккредитация УЦ Тандер (Магнит) и Энергоцентр. Количество аккредитованных УЦ - не изменилось, 44 шт. ✍️"Об ЭП и УЦ"

2 Sept 2026, 05:28 UTC≈2,200 views0 reactions6 Starsread 3 September 2026
Photo

✍️Про сертификаты платформы Цифрового рубля Их два - TLS-сертификат для защиты канала и неквалифицированной электронной подписи. Если со структурой TLS-сертификатов вопросов нет, их структура: C= RU O = g.ru.cbrdc.prt.*** CN= ФИО L = CBDCTLS SNILS = СНИЛС То к сертификатам, создаваемым подчиненными подсистеме Удостоверяющего центра платформы Цифрового рубля Банка России, вопрос возник сразу - кто придумал такую ст…

1 Sept 2026, 16:36 UTC≈2,360 viewsread 3 September 2026
Photo

Они сошлись. Волна и камень, Стихи и проза, НУЦ и рубль Т-Банк для подключения цифрового рубля требует установки сертификатов безопасности Национального УЦ

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

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.

Mentions

Named by 13 registered channels — 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.

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

ЭДО для бизнеса
@EDOB2B · 7,547
#1
Всё про ЭДО
@roseuorg · 13,622
#2
Минцифры России
@mintsifry · 234,419
#3
Листок бюрократической защиты информации
@bureaucraticsecurity · 19,093
#4
Privacy Advocates
@prv_adv · 21,899
#5
Амбассадор ЭДО
@ambassador_edo · 3,874
#6
DigitalRussia
@drussia · 13,878
#7
УЦ ФК
@uc_fk · 5,508
#8
Новости СМЭВ+
@smev_news · 8,377
#9
Астрал | Цифровые решения для бизнеса
@gkastral · 2,841
#10
OFD24 | ККТ, Маркировка, ЕГАИС, Меркурий, Честный ЗНАК, ДМДК, СБП, ЦТО, ОФД, 1С
@ofd24 · 20,798
#11
ИнфоТеКС
@infotecs_official · 6,431
#12
SecurityLab.ru
@SecLabNews · 84,790
#13
BESSEC
@bessec · 4,785
#14
Мероприятия по ИБ
@InfoBezEvents · 5,655
#15
ZLONOV security
@zlonov_security · 3,996
#16
Госключ по API
@goskey_api · 2,905
#17
ИТ-комитет Госдумы
@itduma · 3,647
#18
RPPA PRO: Privacy • AI • Cybersecurity • IP
@GDPRru · 6,094
#19
Новости информационной безопасности
@fstecru · 5,669
#20
BIS Journal — Информационная безопасность
@BISInside · 2,277
#21
Компания «Актив»
@aktivcompany · 2,363
#22
Новости Минцифры
@mincifry · 7,076
#23
AKTIV.CONSULTING
@aktivcons · 2,632
#24
УЦ «Основание»
@ucosnovanie · 895
#25
CISOCLUB - кибербезопасность и ИТ
@cisoclub · 7,069
#26
Сбер2B ЭДО
@sberkorus · 2,806
#27
Новости КриптоПро
@cryptopro_news · 3,664
#28
AM Live
@anti_malware · 13,156
#29
Банк России
@centralbank_russia · 244,269
#30
TAdviser
@tadviser · 13,390
#31
Б-152: защита персональных данных
@b152privacy · 8,935
#32
Код ИБ: ИИ & КиберБезопасность
@codeibnews · 6,886
#33
НеКасперский
@NeKaspersky · 16,103
#34
Цифровое право
@digital_law_trends · 13,463
#35
BI.ZONE
@bizone_channel · 11,291
#36
Нецифровая экономика
@antidigital · 24,364
#37
Positive Technologies
@Positive_Technologies · 29,080
#38
Телеком-ревью
@Telecomreview · 6,730
#39
ЭДО и После
@EDFclub · 977
#40
Integral Security
@integral_security · 1,713
#41
CORTEL
@Cortel_cloud · 4,074
#42
Госключ по СМЭВ
@goskey_smev · 2,103
#43
Импортозамещение в ИТ
@RU_Hardware_Soft · 8,668
#44
Новости битрикс
@AstralBitrixNews · 153 (as read 24 September 2026)
#45
Russian OSINT
@Russian_OSINT · 47,997
#46
ЗаТелеком 🌐
@zatelecom · 64,306
#47
ФНС России
@nalog_gov_ru · 89,698
#48
Госуслуги
@gosuslugi · 993,636
#49
РСпектр: связь, ИТ, кибербезопасность
@rspectr · 3,340
#50
Аутентификация, биометрия, электронная подпись
@AuthBioDS · 402
#51
Пост Лукацкого
@alukatsky · 37,955
#52
Раньше всех. Ну почти.
@bbbreaking · 1,974,828
#53
БДУ ФСТЭК России
@bdufstecru · 10,600
#54
Аналитический центр RPPA
@Persdata · 7,797
#55
Банкста
@banksta · 438,494
#56
ГосСОПКА Центр
@sopkacentr · 16,345
#57
ИБ в "Законе"
@MetaSecurityInformation · 4,061
#58
Утечки информации
@dataleak · 118,872
#59
Денис Лукаш | Privacy Expert
@privacyexpert · 13,441
#60
Управление Уязвимостями и прочее
@avleonovrus · 12,148
#61
RuSecJobs Channel
@RuSecJobs · 11,416
#62
Кто не идёт вперёд, тот идёт назад
@nkhramtsovsky · 438
#63
ГОСТ VPN | aveselov.ru
@aveselov_ru · 2,055
#64
Информация без опасностей (безопасность)
@infobezopasnost · 1,514
#65
ЕСКС технические работы
@esks_tech · 1,972
#66
Резбез
@Rez_in_Bez · 2,648
#67
SecAtor
@true_secator · 41,782
#68
Echelon Eyes
@EchelonEyes · 6,534
#69
Контур
@skbkontur_official · 25,290
#70
ISACARuSec
@IsacaRuSec · 2,260
#71
Кибервойна
@cyberguerre · 8,806
#72
Social Engineering
@Social_engineering · 124,999
#73
ИБ Терминология
@Infsec_terms · 652 (as read 24 September 2026)
#74
Топ кибербезопасности Батранкова
@safebdv · 9,974
#75
Ivan Begtin
@begtin · 9,096
#76
Код на проводе
@Kodnaprovode · 6,055
#77
Инфобезопасность
@infobezopasnostru · 3,297
#78
Токсичная цифра
@toxic_digital · 4,407
#79
Kept | Cyber
@kept_cyber · 1,148
#80
Избранное про ИБ
@sergeyborisov23 · 1,096
#81
Я у мамы SecMemOps
@secmemops · 5,365
#82
AlexRedSec
@alexredsec · 4,009
#83
Аладдин Р.Д.
@aladdinrd · 518
#84
Эшер II. A+
@usher2 · 16,363
#85
ПЕРСОНЕМЫ
@personemes · 1,235
#86
СУДЕБНАЯ ПРАКТИКА IP и IT
@sudpraktik_IPIT_demo · 22,924
#87
k8s (in)security
@k8security · 13,185
#88
Астрал.Безопасность
@is_astral · 2,921
#89
Sachok
@CyberSachok · 11,280
#90
Канал
@ordercomru · 6,058
#91
infosec
@it_secur · 62,254
#92
LegalTech
@Lgltech · 15,417
#93
CNews.ru
@CNewsDaily · 15,692
#94
Mash
@mash · 3,108,224
#95
Information Security Memes
@infosecmemes · 9,651
#96
ССК: вопросы для подготовки
@sskquestions · 1,229
#97

Read from Telegram’s recommendation API, most recently 24 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

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.

OFD24 | ККТ, Маркировка, ЕГАИС, Меркурий, Честный ЗНАК, ДМДК, СБП, ЦТО, ОФД, 1С
@ofd24 · 20,798
Telegram ranks this channel #5 of 87 here — alongside 86 others — read 26 September 2026
Листок бюрократической защиты информации
@bureaucraticsecurity · 19,093
Telegram ranks this channel #7 of 98 here — alongside 97 others — read 4 October 2026
Privacy Advocates
@prv_adv · 21,899
Telegram ranks this channel #23 of 98 here — alongside 97 others — read 22 September 2026
ГИС ЕИС ЗАКУПКИ
@gis_eiszakupki · 89,536
Telegram ranks this channel #41 of 93 here — alongside 92 others — read 26 August 2026
Контур
@skbkontur_official · 25,290
Telegram ranks this channel #42 of 97 here — alongside 96 others — read 14 September 2026
Честный ЗНАК breaking news
@crptbreaking · 29,611
Telegram ranks this channel #65 of 69 here — alongside 68 others — read 26 September 2026
ГИС ТОРГИ ПРОДАЖИ
@gis_torgi_prodaji · 24,504
Telegram ranks this channel #65 of 83 here — alongside 82 others — read 15 September 2026
ФНС России
@nalog_gov_ru · 89,698
Telegram ranks this channel #66 of 96 here — alongside 95 others — read 17 August 2026
Бухучет, налоги, 1С
@buhru · 35,352
Telegram ranks this channel #84 of 95 here — alongside 94 others — read 2 September 2026

This channel appears in 9 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Об ЭП и УЦ” (@ep_uc), 21,210 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/ep_uc.

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.