Channel
@gerkus_fm
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cross-platform identity · Cite this entry
4,047subscribers
-4 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001235254595 |
|---|---|
| Type | Channel |
| Username | @gerkus_fm |
| Created | 2 February 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/gerkus_fm |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 09:35 | 4,047 | -3 |
| 6 Aug 2026, 19:38 | 4,050 | -1 |
| 6 Aug 2026, 10:45 | 4,051 | no change |
| 6 Aug 2026, 09:40 | 4,051 | first reading |
11 posts held, back to 30 March 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 4 pagesof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 11 posts for this entry, the most recent from 4 June 2025. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
504 reactions across 11 posts, in 7 distinct kinds. The most used accounts for 59.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 300 | 59.5% | |
| 🔥 | 102 | 20.2% | |
| 🏆 | 69 | 13.7% | |
| 🌚 | 20 | 3.97% | |
| ⚡ | 8 | 1.59% | |
| 🤨 | 3 | 0.595% | |
| 🤩 | 2 | 0.397% |
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 11 of the 11 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 504reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 30 March 2025 to 4 June 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Интересно было бы вам, друзья, узнать подробнее об Эгриси и моем участии в медийном футболе?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
👍18🌚2
Photo, posted without a caption
🏆20👍7🌚3
Во избежание недоразумений В Акроне работает прекрасный специалист Константин Клюшев. Он прекрасный профессионал и мой хороший товарищ. Желаю ему больших успехов в этой сложной работе и ни в коем случае не претендую на это место.
👍51🏆10🌚3
Вы сегодня
Shares as published. No per-option vote count is published by Telegram, so none is shown.
🌚1🏆1
Немного дополню Александра. Важной (но не очень приятной и часто грустной) частью работы в построении чемпионской команды было расставание. Расстались с большой группой игроков, поменяв тактическую схему и придав ей эффективность. Так, например, расстались с Майконом, отличным парнем и хорошим игроком, но освободили место для Антона Миранчука. Ну и оперативные замены, выпадавших из-за травм игроков на не менее каче…
🔥51👍18🌚1
🔥 5 мая 2018 года в Москве было солнечно и жарко Я очень хорошо помню это, потому что в тот день испытал от футбольного матча эмоции, которые будет очень сложно повторить (матч Россия – Испания, случившийся двумя месяцами позже, был близок, но стал номером 2). 🚀 В тот день Локомотив стал Чемпионом России по футболу Когда я пришел работать в Клуб (октябрь 2016 года), клуб занимал 8-е место, становился чемпионом посл…
👍79🔥35🏆11🤨2
Коллега Александр напомнил о памятной дате и написал любопытный пост о Локо 2018, сравнивая его с легендарным фильмом Moneyball. Предлагаю вашему вниманию.
👍21🏆3⚡1🌚1🔥1
!!! Александр Михайлович!!! Great8!!! Порадовал всю страну!!!
👍83🏆24🔥15⚡7🌚1
Любопытно. Криптонит Спартака
🌚2🤩2
Последние шесть матчей «Спартака» с «Ахматом» в РПЛ: Сезон 22/23 «Ахмат» - «Спартак» - 1:1 «Спартак» - «Ахмат» - 0:0. Сезон 23/24 «Спартак» - «Ахмат» - 0:0 «Ахмат» - «Спартак» - 2:1. Сезон 24/25 «Спартак» - «Ахмат» - 0:0 «Ахмат» - «Спартак» - 0:0. Грозный «Ахмат». @НежурналистИванов
👍23🌚3🤨1
Спартак теряет ключевые очки в Грозном. Означает ли это, что для них гонка за трофей закончилась?
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
🌚3
Showing the 11 most recent of 11 posts we hold for @gerkus_fm. 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.
The 3 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
Интересно было бы вам, друзья, узнать подробнее об Эгриси и моем участии в медийном футболе?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Вы сегодня
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Спартак теряет ключевые очки в Грозном. Означает ли это, что для них гонка за трофей закончилась?
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 11 most recent posts we hold, published 30 March 2025 to 4 June 2025. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Геркус Z ФМ” (@gerkus_fm), 4,047 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/gerkus_fm.
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.