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 · Posts edited after publishing · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

21,400subscribers

+198 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
Description«Об ЭП и УЦ» - @ep_uc самый популярный телеграм-канал о сфере электронной подписи 🗣Чат канала https://t.me/joinchat/-y4FR5AKn7hiMzFi 🔄Обратная связь,инфопартнерство - @Ep_Uc_bot Реклама в канале: @Ep_Uc_bot https://telega.in/c/ep_uc
Created20 September 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held61
Confirmed unchanged1 time, most recently 10 November 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 the other topics.

Growth

21,18321,41221,297.521,4006 August 202610 November 2026
61 measurements spanning 96 days, net +198. 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,149–21,446 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 61
Measured (UTC)SubscribersChange
10 Nov 2026, 08:5521,400-2
8 Nov 2026, 22:2021,402+1
7 Nov 2026, 14:5621,401+2
5 Nov 2026, 13:0621,399-1
4 Nov 2026, 13:3521,400+3
3 Nov 2026, 15:5621,397+3
2 Nov 2026, 14:5121,394-4
1 Nov 2026, 12:1821,398-8
31 Oct 2026, 09:4821,406+1
30 Oct 2026, 11:4721,405+18
29 Oct 2026, 09:4821,387+6
28 Oct 2026, 08:0621,381-5
27 Oct 2026, 07:2821,386-6
26 Oct 2026, 04:1821,392-2
25 Oct 2026, 06:4621,394-3
24 Oct 2026, 05:3821,397+1
23 Oct 2026, 06:4721,396+3
20 Oct 2026, 23:0921,393+2
19 Oct 2026, 23:3021,391-6
19 Oct 2026, 00:4721,397first reading

Engagement

135 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 84 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
13.3%
avg views ÷ 21,400 subscribers
Avg views / post
2,850
34 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
34
of 135 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. It is computed over the 1 of 34 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 November 2026
Posts held135 (30 July 2026 – 11 November 2026)
Views total96,750
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 16:42 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
≈2,480
Videos
≈54
Links
≈3,150

Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

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
70
across the posts below
Posts paid on
4
of 135 we hold a reading for · 3%
Most on one post
50
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 135 most recent posts we hold for this entry, published 30 July 2026 to 11 November 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
0.741%
1 of 135 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
2,710
over 134 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 135 most recent posts we hold, published 30 July 2026 to 11 November 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

Telegram’s own ‘edited’ marker: 2 of 34 posts held from the last 30 days (5.88%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

11 Nov 2026, 05:28 UTC≈1,720 viewsread 11 November 2026

✍️А ведь когда-то серьезно обсуждалось, чтобы доверенными лицами аккредитованных УЦ были только МФЦ и нотариусы. Представляете, чтобы бы могли наделать первые? Да и вторые не оставали. https://www.securitylab.ru/news/579807.php

11 Nov 2026, 05:20 UTC≈1,600 viewsread 11 November 2026
Photo

📊 Топ-10 аккредитованных удостоверяющих центров за десять месяцев 2026 года Общий рост выданных сертификатов на 2,8 млн. по сравнению с аналогичным периодом прошлого года. Одно изменение в топ-10 по сравнению с прошлым месяцем, теперь Т-Банк на 10 позиции. Изменения ещё произойдут, они будут связаны с прекращением аккредитации УЦ Модум и повторением весенней ситуации с Атлас Карт, что в очередной раз создаст право…

10 Nov 2026, 04:48 UTC≈2,070 viewsread 11 November 2026
Photo

✍️Принят первый НПА, связанный с Национальным УЦ Подписано распоряжение Правительства, устанавливающее случаи при которых сертификат безопасности НУЦ прекращает своё действие. К трем случаям, установленных частью 7 статьи 14.1 63-ФЗ (истечение срока действия, на основании заявления или в рамках соглашения между НУЦ и заявителем), добавлены ещё четыре: 🔹вступление в силу решения суда, которым установлено, что сертиф…

9 Nov 2026, 19:34 UTC≈2,160 viewsread 11 November 2026
Photo

✍️Ответ Судебного департамента при на письмо АРБ "О судебных документах без электронной подписи" Судебный департамент ответил раньше Минцифры на запрос АРБ... и зря. Качество ответа в очередной раз показывает непонимание госорганами нашей сферы, даже самых базовых вещей. Если коротко - во всём виновата Почта России: При использовании сервиса ЭЗП в адрес АО «Почта России» направляется для вручения получателю докумен…

8 Nov 2026, 16:55 UTC≈2,410 viewsread 11 November 2026

✍️Исторический пост - как проверка Счётной палаты выявила проблемы в деятельности УЦ В 2017 году Счётная палата вскрыла схему, при которой пенсионные накопления граждан переводились в НПФ с использованием электронных подписей, квалифицированные сертификаты которых были выданы в нарушение 63-ФЗ. Проверка процедур подачи заявлений о переходе в электронной форме за 2012–2016 годы выявила: 🔹заявления от имени умерших л…

7 Nov 2026, 05:19 UTC≈2,620 viewsread 11 November 2026
Photo

😳Модум решил не продлевать истекающую 23 ноября аккредитацию УЦ в плановом порядке, поэтому ждём повторение истории Атлас Карт?

6 Nov 2026, 16:36 UTC≈2,680 viewsread 11 November 2026
Forwarded from @antiinfosec

Браузер обязан дружить с Госключом. Но Госключ пока не дружит с приказом Минцифры. Из-за атак на дата-центры в паблике как-то упустили новый проекте требований к «доверенному ПО». Однако там есть интересный пункт: браузер должен уметь работать с «клиентской частью» государственной системы электронной подписи. Той самой, что описана в постановлении № 2152 и на которой работает «Госключ». Звучит логично. Государство с…

6 Nov 2026, 05:05 UTC≈2,590 viewsread 11 November 2026
Photo

✍️Подведены итоги обсуждения требований Минцифры к доверенному ПО Учтены только редакторские правки. На мои предложения: 1. Согласно разработанному проекту почтовые приложения должны обеспечить использование сертифицированных средств электронной подписи с применением квалифицированных сертификатов в целях обеспечения целостности передаваемой информации в сообщениях электронной почты. Однако включение адреса электрон…

5 Nov 2026, 18:00 UTC≈2,660 viewsread 11 November 2026

🔐 CA/B Forum взялся за решение проблемы слабых ключей ECDSA Я ждал, когда же CA/B Forum выскажется по проблеме слабых ключей УЦ eMudhra, высказались, в протоколе рабочей группы. Решили, что в Базовых требованиях есть пробел - для RSA проверки качества ключей прописаны (раздел 6.1.6), а для ECDSA явных минимальных проверок нет. Председатель форума Димитрис Захаропулос сам поднял инцидент с промежуточными сертификат…

5 Nov 2026, 05:32 UTC≈3,150 viewsread 11 November 2026
Photo

❌Утечка данных УЦ или компиляция? В начале мая стала обсуждаться информация о появлении в утечках базы под названием "Пользователи cryptopro.ru 2026". Одного взгляда на реквизитный состав достаточно, чтобы понять - название не соответствует источнику утечки, о чем было отдельное сообщение от КриптоПро. Логика такого названия утечки объясняется просто - увидели хакеры название криптопровайдера и сделали свой неправи…

5 Nov 2026, 05:03 UTC≈3,100 viewsread 11 November 2026
Photo

Некоторым операторам ЭДО неплохо было бы убрать данный баннер об "обновлении электронной подписи".

Showing the 12 most recent of 135 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.

Posts edited after publishing

@ep_uc edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
10 November 2026
Most recent edit
10 November 2026

Posts recorded as deleted after publishing

We recorded 7 posts on @ep_uc as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
10 August 2026
Most recent seen missing
11 November 2026
Median time before seen missing
47 hours
Seen missing in the last 30 days
1

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 16 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,561
#1
Всё про ЭДО
@roseuorg · 13,550
#2
Минцифры России
@mintsifry · 232,434
#3
Листок бюрократической защиты информации
@bureaucraticsecurity · 19,134
#4
Privacy Advocates
@prv_adv · 21,842
#5
Амбассадор ЭДО
@ambassador_edo · 3,850
#6
DigitalRussia
@drussia · 13,907
#7
УЦ ФК
@uc_fk · 5,495
#8
Новости СМЭВ+
@smev_news · 8,342
#9
Астрал | Цифровые решения для бизнеса
@gkastral · 3,220
#10
OFD24 | ККТ, Маркировка, ЕГАИС, Меркурий, Честный ЗНАК, ДМДК, СБП, ЦТО, ОФД, 1С
@ofd24 · 20,786
#11
ИнфоТеКС
@infotecs_official · 6,442
#12
SecurityLab.ru
@SecLabNews · 86,532
#13
BESSEC
@bessec · 4,796
#14
Мероприятия по ИБ
@InfoBezEvents · 5,693
#15
ZLONOV security
@zlonov_security · 3,985
#16
Госключ по API
@goskey_api · 2,897
#17
ИТ-комитет Госдумы
@itduma · 3,624
#18
RPPA PRO: Privacy • AI • Cybersecurity • IP
@GDPRru · 6,143
#19
Новости информационной безопасности
@fstecru · 5,663
#20
BIS Journal — Информационная безопасность
@BISInside · 2,271
#21
Компания «Актив»
@aktivcompany · 2,364
#22
Новости Минцифры
@mincifry · 7,047
#23
AKTIV.CONSULTING
@aktivcons · 2,636
#24
УЦ «Основание»
@ucosnovanie · 899
#25
CISOCLUB - кибербезопасность и ИТ
@cisoclub · 7,191
#26
Сбер2B ЭДО
@sberkorus · 2,789
#27
Новости КриптоПро
@cryptopro_news · 3,682
#28
AM Live
@anti_malware · 13,159
#29
Банк России
@centralbank_russia · 243,972
#30
TAdviser
@tadviser · 13,465
#31
Б-152: защита персональных данных
@b152privacy · 9,024
#32
Код ИБ: ИИ & КиберБезопасность
@codeibnews · 7,007
#33
НеКасперский
@NeKaspersky · 16,203
#34
Цифровое право
@digital_law_trends · 13,403
#35
BI.ZONE
@bizone_channel · 11,624
#36
Нецифровая экономика
@antidigital · 24,491
#37
Positive Technologies
@Positive_Technologies · 29,449
#38
Телеком-ревью
@Telecomreview · 6,783
#39
ЭДО и После
@EDFclub · 987
#40
Integral Security
@integral_security · 1,710
#41
CORTEL
@Cortel_cloud · 4,072
#42
Госключ по СМЭВ
@goskey_smev · 2,102
#43
Импортозамещение в ИТ
@RU_Hardware_Soft · 8,793
#44
Новости битрикс
@AstralBitrixNews · 153 (as read 24 September 2026)
#45
Russian OSINT
@Russian_OSINT · 48,514
#46
ЗаТелеком 🌐
@zatelecom · 64,510
#47
ФНС России
@nalog_gov_ru · 89,464
#48
Госуслуги
@gosuslugi · 988,723
#49
РСпектр: связь, ИТ, кибербезопасность
@rspectr · 3,301
#50
Аутентификация, биометрия, электронная подпись
@AuthBioDS · 399
#51
Пост Лукацкого
@alukatsky · 38,465
#52
Раньше всех. Ну почти.
@bbbreaking · 1,975,436
#53
БДУ ФСТЭК России
@bdufstecru · 10,641
#54
Аналитический центр RPPA
@Persdata · 7,741
#55
Банкста
@banksta · 439,838
#56
ГосСОПКА Центр
@sopkacentr · 6,134
#57
ИБ в "Законе"
@MetaSecurityInformation · 4,079
#58
Утечки информации
@dataleak · 117,675
#59
Денис Лукаш | Privacy Expert
@privacyexpert · 13,403
#60
Управление Уязвимостями и прочее
@avleonovrus · 12,628
#61
RuSecJobs Channel
@RuSecJobs · 11,614
#62
Кто не идёт вперёд, тот идёт назад
@nkhramtsovsky · 442
#63
ГОСТ VPN | aveselov.ru
@aveselov_ru · 2,140
#64
Информация без опасностей (безопасность)
@infobezopasnost · 1,518
#65
ЕСКС технические работы
@esks_tech · 1,977
#66
Резбез
@Rez_in_Bez · 2,643
#67
SecAtor
@true_secator · 42,213
#68
Echelon Eyes
@EchelonEyes · 6,541
#69
Контур
@skbkontur_official · 25,129
#70
ISACARuSec
@IsacaRuSec · 2,268
#71
Кибервойна
@cyberguerre · 8,923
#72
Social Engineering
@Social_engineering · 124,696
#73
ИБ Терминология
@Infsec_terms · 652 (as read 24 September 2026)
#74
Топ кибербезопасности Батранкова
@safebdv · 9,995
#75
Ivan Begtin
@begtin · 9,104
#76
Код на проводе
@Kodnaprovode · 6,089
#77
Инфобезопасность
@infobezopasnostru · 3,307
#78
Токсичная цифра
@toxic_digital · 5,534
#79
Kept | Cyber
@kept_cyber · 1,165
#80
Избранное про ИБ
@sergeyborisov23 · 1,119
#81
Я у мамы SecMemOps
@secmemops · 5,435
#82
AlexRedSec
@alexredsec · 4,030
#83
Аладдин Р.Д.
@aladdinrd · 525
#84
Эшер II. A+
@usher2 · 16,550
#85
ПЕРСОНЕМЫ
@personemes · 1,245
#86
СУДЕБНАЯ ПРАКТИКА IP и IT
@sudpraktik_IPIT_demo · 22,978
#87
k8s (in)security
@k8security · 13,332
#88
Астрал.Безопасность
@is_astral · 2,924
#89
Sachok
@CyberSachok · 11,349
#90
Канал
@ordercomru · 6,098
#91
infosec
@it_secur · 63,440
#92
LegalTech
@Lgltech · 15,339
#93
CNews.ru
@CNewsDaily · 15,763
#94
Mash
@mash · 3,140,033
#95
Information Security Memes
@infosecmemes · 9,619
#96
ССК: вопросы для подготовки
@sskquestions · 1,230
#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,786
Telegram ranks this channel #5 of 87 here — alongside 86 others — read 26 September 2026
Листок бюрократической защиты информации
@bureaucraticsecurity · 19,134
Telegram ranks this channel #7 of 98 here — alongside 97 others — read 4 October 2026
Privacy Advocates
@prv_adv · 21,842
Telegram ranks this channel #23 of 98 here — alongside 97 others — read 22 September 2026
ГИС ЕИС ЗАКУПКИ
@gis_eiszakupki · 89,074
Telegram ranks this channel #41 of 93 here — alongside 92 others — read 26 August 2026
Контур
@skbkontur_official · 25,129
Telegram ranks this channel #42 of 97 here — alongside 96 others — read 14 September 2026
Честный ЗНАК breaking news
@crptbreaking · 29,643
Telegram ranks this channel #65 of 69 here — alongside 68 others — read 26 September 2026
ГИС ТОРГИ ПРОДАЖИ
@gis_torgi_prodaji · 24,284
Telegram ranks this channel #65 of 83 here — alongside 82 others — read 15 September 2026
ФНС России
@nalog_gov_ru · 89,464
Telegram ranks this channel #66 of 96 here — alongside 95 others — read 17 August 2026
Бухучет, налоги, 1С
@buhru · 35,198
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 10 November 2026 — this entry's latest reading, not the date you are reading this.

“Об ЭП и УЦ” (@ep_uc), 21,400 subscribers as measured 10 November 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.