Telegram RegisterThe public register of Telegram

Channel

МАЯК | РБЦ

@mayak_rbc

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

1,304subscribers

-7 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001019009367
TypeChannel
Username@mayak_rbc
Created9 February 2016measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/mayak_rbc

Growth

1,3041,3111,307.56 August 2026 — 1,311 subscribers6 August 2026 — 1,311 subscribers10 August 2026 — 1,306 subscribers12 August 2026 — 1,304 subscribers6 August 202612 August 2026
4 measurements spanning 6 days, net -7. 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 1,303–1,312 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 21:151,304-2
10 Aug 2026, 07:041,306-5
6 Aug 2026, 11:501,311no change
6 Aug 2026, 11:451,311first reading

Engagement

7 posts held, back to 9 July 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
46.5%
avg views ÷ 1,304 subscribers
Avg views / post
607
6 posts measured
Reaction rate
8.52%
reactions ÷ views · ER floor
Posts in window
6
of 7 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 4 August 2026
Posts held7 (9 July 20264 August 2026)
Views total3,639
Reactions total310
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 11:50 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

343 reactions across 7 posts, in 7 distinct kinds. The most used accounts for 49.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 524932945174070697316849.0%
custom 52535224651030364756418.7%
🕊4914.3%
custom 5235810861787917997205.83%
💯174.96%
🤣133.79%
😇123.50%

Custom emoji. 3 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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 7 of the 7 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 343reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 7 most recent posts we hold, published 9 July 2026 to 4 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.

Recent posts

4 Aug 2026, 18:00 UTC310 views46 reactionsread 6 August 2026
Video

150 лет Синодальному переводу Библии 📖 🕊 В честь этой даты церковь в Троицке запустила необычный проект — каждый желающий может собственноручно переписать несколько стихов из Евангелия от Иоанна. После завершения рукопись будет передана в дар Троицкому музею ко Дню города. 🙌 Наша молодежь с радостью участвует в этом проекте. Для нас это не просто переписывание текста, а возможность познакомить людей с Библией, расс

custom 524932945174070697323🕊13😇10

31 Jul 2026, 19:03 UTC476 views39 reactionsread 6 August 2026
Video

Мы знаем, каково это оказаться в большом городе и в большой церкви совсем одному — это страшно.. ✝️Но ты не одинок: церковь — не просто здание. Это собрание людей, желающих проявить любовь, которую когда-то они увидели во Христе. Нам важно, чтобы каждый приходящий в нашу общину смог почувствовать заботу и принятие 🤍 Приходя на служение, смело находи ребят в зеленых футболках, они с радостью покажут тебе здание, п

custom 524932945174070697317💯13🕊7😇2

28 Jul 2026, 08:05 UTC701 views62 reactionsread 6 August 2026
Photo

Маяковцы на брянском конгрессе! На этих выходных молодежь нашей церкви съездила на брянскую землю - там проходил собор церквей. Примерно так выглядел наш таймлайн 🐚 🤩Пятница — в 11 утра приехали в Брянск, разложили палатки, осмотрели базу отдыха, пошли на вечернее богослужение, покушали вкуснейшее томленое мясо (16 часов) в смокере, попели песни. 🤩Суббота — утренняя пробежка, завтрак, богослужение, поездка на озеро

custom 524932945174070697331custom 525352246510303647518🕊13

24 Jul 2026, 11:02 UTC688 views69 reactionsread 6 August 2026
Video

Если ты недавно в церкви или еще не в малой группе — обязательно присоединяйся💡 Это место общения, поддержки и духовного роста. Возможно, именно там ты найдешь друзей на долгие годы🤍

custom 524932945174070697329custom 525352246510303647518🤣11🕊5💯4custom 52358108617879179972

22 Jul 2026, 16:17 UTC678 views43 reactionsread 6 August 2026
Photo

Небольшая зарисовка с воскресенья ⚽️ Собрались с молодежью, посмотрели чемпионат мира 2026 по футболу на большом экране. Уже планируем Формулу 1. Кому место забронить?

custom 524932945174070697322custom 523581086178791799711custom 52535224651030364759🤣1

15 Jul 2026, 08:38 UTC786 views51 reactionsread 6 August 2026
Photo

Открытый воздух + открытые сердца — Маяк на Опен Эйр 🩵 🚉 На предыдущем уикенде наша молодёжь отправилась на ночном поезде из Москвы и утром уже была в лесу под Санкт-Петербургом на палаточной конференции Опен Эйр. 🏕 4 дня вместе на берегу озера, проповеди о важности церкви в жизни христиан, семинары на актуальные темы, прославление, время в общении, активности, Божья благодать. Вдали от сети в лесу мы точно стали б

custom 524932945174070697330🕊11custom 525352246510303647510

9 Jul 2026, 12:03 UTC844 views33 reactionsread 6 August 2026
Video

Какие мысли у молодежи после воскресного маяка?

custom 524932945174070697316custom 52535224651030364759custom 52358108617879179977🤣1

Showing the 7 most recent of 7 posts we hold for @mayak_rbc. 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 — 254,306 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 3 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.

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

“МАЯК | РБЦ” (@mayak_rbc), 1,304 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/mayak_rbc.

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.