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 678–680 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
7 Aug 2026, 18:10
679
no change
7 Aug 2026, 09:48
679
first reading
Engagement
15 posts held, back to 11 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 1 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
45.1%
avg views ÷ 679 subscribers
Avg views / post
306
13 posts measured
Reaction rate
2.76%
reactions ÷ views · ER floor
Posts in window
13
of 15 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
Window
Rolling 30 days · latest post in window 6 August 2026
Posts held
15 (11 July 2026 – 6 August 2026)
Views total
3,983
Reactions total
110
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 09:48 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.
Reaction mix
137 reactions across 15 posts, in 8 distinct kinds. The most used accounts for 46.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
64
46.7%
👍
19
13.9%
🙏
17
12.4%
🥰
13
9.49%
🔥
11
8.03%
❤🔥
10
7.30%
😁
2
1.46%
💋
1
0.73%
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 15 of the 15 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 137reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 11 July 2026 to 6 August 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.
Advertising
Ad load
6.67%
1 of 15 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
134
over 1 measured post
Median views · rest
360
over 14 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
erid
Posts
First seen
Last seen
2VtzqvFbGBt
1
6 August 2026
6 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 15 most recent posts we hold, published 11 July 2026 to 6 August 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.
Друзья!
Возможно, рядом с вами есть человек, которому сегодня особенно нужны знания о любви, семье и гармоничных отношениях.
Команда клубного движения «БЛАГОСТЬ» рекомендует
новый ПРАКТИКУМ, где
Олег Геннадьевич Торсунов выступает в роли главного ведущего лектора
❤️🩷❤️
«ИСКУССТВО ЛЮБИТЬ»
Это 5-месячный путь к взаимопониманию, поддержке и укреплению отношений — через знания, практику, встречи в группе и сопровожд…
Волонтерский центр Благость Москва 2 Сокольники☀️
🚶♀️➡️🚶♂️➡️Каждую среду ВЦ Благость Москва 2 Сокольники проводит ЗОЖ встречи - Аскезы по средам🏃🏻♂️➡️🏃🏼♀️➡️
❗️Приглашаем всех желающих в парк Сокольники на динамическую чистку пяти слоев в компании единомышленников ❤️
🏃🏻♂️➡️🚶♀️➡️Бег или быстрая ходьба по желанию и возможностям🚶♂️➡️🏃🏼♀️➡️
🗓 5 августа, среда
⏱️ Время: 8.00
📌 Место встречи: центральный …
🔥1-2 августа -
Очная группа в Москве на Большую Клубную Встречу с Олегом Геннадьевичем
Торсуновым!
📅 1-2 августа(сб,вс)
🕚 11:00–14:00 (МСК)
м.Авиамоторная
📍Адрес: после записи
• Настройка
• Совместная практика
• Ответы
С собой:
коврик/плед, вода
Запись/вопросы:
+79104457287
Сергей
Telergam VK MAX WhatApp
Дорогие друзья!
Сегодня Регина Кутлова для женщин направления "Семья в благости" провела очень душевную и познавательную встречу! Каждая из нас ушла со своим открытием и теплой благодарностью🙏в сердце❤️!
Регина!!! Благодарю от каждой из нас за заботу, внимание и напоминание всего этого очень-очень важного🥰!!!
Волонтерский центр Благость Москва 2 Сокольники☀️
🚶♀️➡️🚶♂️➡️ Каждую среду ВЦ Благость Москва 2 Сокольники проводит ЗОЖ встречи - Аскезы по средам 🏃🏻♂️➡️🏃🏼♀️➡️
❗️Приглашаем всех желающих в парк Сокольники на динамическую чистку пяти слоев в компании единомышленников ❤️
🏃🏻♂️➡️🚶♀️➡️Бег или быстрая ходьба по желанию и возможностям🚶♂️➡️ 🏃🏼♀️➡️
🗓 22 июля, среда
⏱️ Время: 8.00
📌 Место встречи: центральны…
ДОРОГИЕ ДРУЗЬЯ И ЕДИНОМЫШЛЕННИКИ!
🤩 МАКСИМ БЕЗРОДНОВ в Москве!!!
- 26 июля с 18.00 до 20.30 состоится встреча с Максимом!
──────────────
☀️ Максим (t.me/maximbezro...) — наставник и куратор «Школы счастья», специалист оздоровительного центра «Амрита», дипломированный коуч, лектор на Веда Радио, а так же консультант по трудным жизненным обстоятельствам. Глубоко разбирается в жизни и уже много лет помогает людям ста…
🌺 Дорогие, девушки 🌺!
25го июля в 10:30 планируем встречу
с Региной Кутловой, на которой она проведет тренинг на тему:
"Как выйти замуж за мужчину своей мечты!!!"
Регина Кутлова
- бизнес-тренер
- коуч ICF
- автор курсов "Тайм-менеджмент", "Эффективное управление"
Сотренер - Алина Титова
Место встречи: м.Рязанский проспект
Встреча безоплатная.
Запись на встречу обязательна. Сообщить о своем участии можно Екатери…
Приветствуем, друзья!
🎉 20 ИЮЛЯ☀️
~ПОНЕДЕЛЬНИК~
🔥ОЧНАЯ ГРУППА🔥
для совместной практики
- Онлайн подключение к интенсиву с Олегом Торсуновым
🧭Адрес: м. Нагорная,
Электролитный проезд, 3Г
🕰Время: с 19:00 до 21:30.
По всем вопросам пишите:
+79104457287 Сергей
@TikhomirovSS
Telergam VK MAX WhatApp
🙏6🔥1
Showing the 12 most recent of 15 posts we hold for @blagostmsk. 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 — 241,423 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.
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.
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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@blagostmsk named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@maximbezro named in 1 post, 8 August 2026 – 8 August 2026
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.
“❗️ АНОНСЫ ❗️ВЦ БЛАГОСТЬ Москва” (@blagostmsk), 679 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/blagostmsk.
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.