Telegram RegisterThe public register of Telegram

Channel

Пермское УФАС России

@perm_ufas

On this record: Growth · Engagement · Advertising · Posts · Citations · Cite this entry

311subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001669643634
TypeChannel
Username@perm_ufas
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/perm_ufas

Growth

3117 Aug 2026, 06:18 — 311 subscribers7 Aug 2026, 23:03 — 311 subscribers7 Aug 2026, 06:187 Aug 2026, 23:03
2 measurements taken within a single day. 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 310–312 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 23:03311no change
7 Aug 2026, 06:18311first reading

Engagement

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

ERR · 30 days
22.9%
avg views ÷ 311 subscribers
Avg views / post
71.3
11 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
11
of 20 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 July 2026
Posts held20 (22 June 202628 July 2026)
Views total784
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 06:18 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.

Advertising

Ad load
20.0%
4 of 20 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
115
over 4 measured posts
Median views · rest
73.0
over 16 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.

Measured over the 20 most recent posts we hold, published 22 June 2026 to 28 July 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 Jul 2026, 06:05 UTC72 viewsread 7 August 2026

⚡ Пермское УФАС возбудило дело из-за повышения цен на бензин на АЗС сети «Ликом». 🔍 Служба подозревает продавца сети в установлении экономически необоснованных цен на бензин. 📃 Ранее УФАС выдало этому продавцу предупреждение о недопустимости совершения действий, которые могут нарушать Закон о защите конкуренции. 🚫 Предупреждение не исполнено в установленный срок. ❗ В отношении продавца сети АЗС «Ликом» возбуждено

27 Jul 2026, 07:13 UTC63 viewsread 7 August 2026

🎒 Пермское УФАС напоминает продавцам о необходимости добросовестного рыночного поведения в период сезонного спроса перед началом учебного года. 📌 Для повышения доступности товаров для потребителей служба предлагает продавцам школьных товаров присоединиться к инициативе по ограничению цен и наценок в указанный период. ❗ Это позволит повысить доступность востребованных товаров и предотвратить возможный рост цен в пер

24 Jul 2026, 12:34 UTC72 viewsread 7 August 2026

Пермское УФАС проверит цены на газ в одной из крупных сетей Прикамья, пишет Properm.ru. ✍ В УФАС поступили жалобы на рост цен на сжиженный углеводородный газ (СУГ) на АЗС сети «Логаз SV». 🔍 Служба проанализирует состояние конкуренции на рынке розничной реализации СУГ в границах Пермского края с целью установления наличия или отсутствия доминирующих хозяйствующих субъектов. 🔍 Служба направит запросы в целях проверк

24 Jul 2026, 07:17 UTC62 viewsread 7 August 2026

⚡️ Пермское УФАС: «Детский мир» ограничил наценки на школьные товары перед началом учебного года. 👉 Перед 1 сентября 2026 года торговая сеть зафиксировала цены на отдельные канцелярские товары, а также одежду и обувь на уровне минимальных цен прошлого года. В ассортимент товаров по минимальным ценам в том числе вошли: 🎒 рюкзаки; 📚 тетради; ✏ карандаши; 🎨 принадлежности для рисования и творчества. ✅ Компания обеспе

23 Jul 2026, 11:40 UTC64 viewsread 7 August 2026
Advertisement

Пермское УФАС наложило на нарушителей Закона о рекламе более 1 млн рублей штрафов за 6 месяцев 2026 года. ✍ 102 жалобы на рекламу поступило в УФАС за 6 месяцев 2026 года. 📚 25 дел возбуждено по признакам нарушения Закона о рекламе. 📝 В 21 случае признаны нарушения и вынесены решения. 📃 8 предписаний о необходимости прекратить выявленное нарушение Закона о рекламе выдано нарушителям. ❗ 1 млн 5 тысяч рублей состав

22 Jul 2026, 09:25 UTC61 viewsread 7 August 2026

Более 6,3 млн рублей штрафов наложило Пермское УФАС на монополистов края в первой половине 2026 года за нарушения при подключении потребителей к сетям. ✍ В УФАС за 6 месяцев 2026 года поступило больше 120 жалоб 📍 о нарушениях правил подключения домовладений к сетям газоснабжения в рамках программы бесплатной газификации; 📍 о нарушениях при подключении к электрическим сетям, сетям водоснабжения и водоотведения, а так

22 Jul 2026, 06:52 UTC58 viewsread 7 August 2026

✍ В Пермское УФАС за 6 месяцев 2026 года поступило более 430 обращений по фактам возможного злоупотребления компаниями-монополистами доминирующим положением на рынках электроэнергетики, тепло-, газо-, водоснабжения и водоотведения, обращения с коммунальными отходами. Причины жалоб: 📍навязывание невыгодных условий договора с ресурсоснабжающей организацией, 📍отказ в заключении договора, 📍несогласие с ценами (тарифами)

20 Jul 2026, 09:18 UTC73 viewsread 7 August 2026
Photo

Александр Плаксин: "Задача Пермского УФАС - развитие конкуренции", показывает Вести-Пермь. Руководитель Пермского УФАС Александр Плаксин в эфире радио "Вести ФМ" подвел итоги работы ведомства за 6 месяцев 2026 года: 📍 какие нарушения чаще всего выявляли на товарных рынках, в сфере госзакупок, рекламы, деятельности монополий и органов власти, 📍 какие вызовы сегодня стоят перед антимонопольной службой Прикамья, 📍 каки

20 Jul 2026, 09:04 UTC73 viewsread 7 August 2026

❗ Пермское УФАС включило в реестр недобросовестных поставщика некачественных медизделий. Подрядчик поставил в Федеральный центр сердечно-сосудистой хирургии им. С.Г. Суханова некачественные медизделия и не исполнил требование заказчика - заменить товар на качественный. ☝ Нарушение условий контракта со стороны поставщика создало угрозу оказанию высокотехнологичной специализированной медпомощи гражданам. Заказчик от

15 Jul 2026, 11:24 UTC93 viewsread 7 August 2026

Пермское УФАС включило в реестр недобросовестных поставщиков 72 участника закупок за 6 месяцев 2026 года. В УФАС поступило 246 обращений заказчиков о включении информации о подрядчиках в реестр недобросовестных поставщиков. ❗ В реестр включена информация ✅ о 10 недобросовестных участниках закупок, уклонившихся от заключения контрактов, ✅ о 60 подрядчиках, с которыми контракты расторгнуты по решению заказчиков, ✅ о

15 Jul 2026, 11:05 UTC93 viewsread 7 August 2026

Пермское УФАС выявило 127 нарушений при проведении госзакупок за 6 месяцев 2026 года. 📍 В УФАС поступило 249 жалоб участников закупок. ✅ Признаны обоснованными 64 жалобы. 📍 По результатам рассмотрения жалоб выявлено 96 нарушений Закона о контрактной системе. ✅ Выдано 88 предписаний об устранении нарушений. 📍 Проведено 56 проверок. Проверено 73 закупки. ✅ По результатам проверок выявлено 31 нарушение Закона о контр

14 Jul 2026, 07:33 UTC108 viewsread 7 August 2026
Photo

Руководитель Пермского УФАС Александр Плаксин подведет итоги работы ведомства за 6 месяцев 2026 года в прямом эфире радио Вести ФМ. Глава антимонопольной службы региона расскажет о состоянии конкуренции в Пермском крае на текущий момент, а также ответит на актуальные вопросы: 📍 о динамике цен на продовольственные товары, 📍 о ситуации на региональном рынке розничной реализации автомобильного топлива, 📍 о практике по

Showing the 12 most recent of 20 posts we hold for @perm_ufas. 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 — 1,007,219 of 1,169,250entries 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.

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.

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

“Пермское УФАС России” (@perm_ufas), 311 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/perm_ufas.

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.