Кто круче разбирается в логотипах РПЛ? 🤔🇷🇺 Начо вместе с Юкичем зарубились против Мальдонадо и Арройо ⚽️ Попробуй сыграть по ссылке и делись результатами в комментариях👇
custom 531889006346190044248❤22❤🔥6😁3

Channel
@fcrk1958
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Referenced elsewhere · Cite this entry
54,034subscribers
-1,478 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001156318536 |
|---|---|
| Type | Channel |
| Username | @fcrk1958 |
| Description | № 7091743193 Официальный Telegram-канал ФК «Рубин» Поддержи наш канал своим голосом: https://t.me/boost/fcrk1958 Официальное мини-приложение: https://t.me/fcrubin_bot Канал пресс-службы «Рубина»: https://t.me/fcrkpress |
| Created | 17 July 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/fcrk1958 |
Sports — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 12:41 | 54,034 | -66 |
| 16 Sept 2026, 03:39 | 54,100 | -92 |
| 14 Sept 2026, 07:35 | 54,192 | -37 |
| 12 Sept 2026, 14:37 | 54,229 | -43 |
| 10 Sept 2026, 15:19 | 54,272 | -138 |
| 7 Sept 2026, 12:57 | 54,410 | -58 |
| 4 Sept 2026, 15:20 | 54,468 | -94 |
| 3 Sept 2026, 02:35 | 54,562 | -159 |
| 1 Sept 2026, 22:36 | 54,721 | -441 |
| 31 Aug 2026, 19:24 | 55,162 | -23 |
| 30 Aug 2026, 21:39 | 55,185 | +172 |
| 29 Aug 2026, 23:28 | 55,013 | -1 |
| 28 Aug 2026, 23:45 | 55,014 | +16 |
| 28 Aug 2026, 02:34 | 54,998 | -245 |
| 27 Aug 2026, 01:58 | 55,243 | -380 |
| 26 Aug 2026, 01:36 | 55,623 | -113 |
| 25 Aug 2026, 05:05 | 55,736 | -47 |
| 24 Aug 2026, 05:55 | 55,783 | -224 |
| 22 Aug 2026, 13:53 | 56,007 | +107 |
| 21 Aug 2026, 07:25 | 55,900 | first reading |
325 posts held, back to 4 August 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 96 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 22 September 2026 |
|---|---|
| Posts held | 325 (4 August 2026 – 22 September 2026) |
| Views total | 1,016,180 |
| Reactions total | 32,214 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Sept 2026, 16:05 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.
Lifetime counters from Telegram’s own channel header, read 22 September 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.
Measured directly from 102 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.
48,225 reactions across 314 posts, in 61 distinct kinds. The most used accounts for 30.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5318890063461900442 | 14,473 | 30.0% | |
| ❤ | 8,956 | 18.6% | |
| custom 5334738737597263451 | 3,238 | 6.71% | |
| 🤣 | 3,119 | 6.47% | |
| 🔥 | 2,041 | 4.23% | |
| custom 5402194428796379700 | 1,613 | 3.34% | |
| custom 5402459737516190082 | 1,365 | 2.83% | |
| custom 5424929155277945471 | 1,354 | 2.81% | |
| 😭 | 1,333 | 2.76% | |
| 👍 | 1,002 | 2.08% | |
| custom 5400227419674161683 | 724 | 1.50% | |
| custom 5402554561804149844 | 680 | 1.41% | |
| custom 5402570466068045810 | 660 | 1.37% | |
| 🤨 | 635 | 1.32% | |
| 💔 | 617 | 1.28% | |
| 👏 | 400 | 0.829% | |
| custom 5400101620082056194 | 357 | 0.74% | |
| custom 5230954452072033873 | 330 | 0.684% | |
| custom 5402156950911752156 | 328 | 0.68% | |
| 😁 | 324 | 0.672% | |
| 41 further kinds | 4,676 | 9.70% |
Custom emoji. 11 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 are Telegram’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 325 of the 325 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 51,191 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 325 most recent posts we hold, published 4 August 2026 to 22 September 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.
Кто круче разбирается в логотипах РПЛ? 🤔🇷🇺 Начо вместе с Юкичем зарубились против Мальдонадо и Арройо ⚽️ Попробуй сыграть по ссылке и делись результатами в комментариях👇
custom 531889006346190044248❤22❤🔥6😁3
«Рубин» проведёт товарищеский матч против «Балтики» 🇷🇺🤍 Игра пройдет 3 октября на базе в Казани 🏠 Ставь ⚽️ если ждёшь!
custom 5318890063461900442183❤14😁14❤🔥6👍4😭2🤝1😨1
Урозов 🆚 Мальдонадо 🤔 Устроили челлендж для защитников «Рубина» 🇷🇺 За кого болели? ❤️ – Урозов 🔥– Мальдонадо
❤106🔥49👍15👏1🕊1
Кристиану Ансальди – 40 ❤️💚 Сегодня свой день рождения отмечает легендарный защитник «Рубина» – Кристиан Ансальди 😍 ⚽️ – С днём рождения, Крис!
custom 5318890063461900442237🔥46❤28🫡4⚡3👍1
Узнали у игроков «Рубина» их планы на выходные 🌴⚽️ Ставь ❤️ если уже соскучился по команде 👇
❤60custom 531889006346190044220🔥10🫡1😁1
АННА НЕМЧЕНКО НА «АК БАРС АРЕНЕ» ⚽️💙 11 октября перед матчем с московским «Динамо» выступит актриса театра и кино, блогер, певица, автор хита «Танцпол везде» 🎤 Начало программы в 18:00. До встречи на стадионе ❤️💚 🎫 БИЛЕТЫ НА МАТЧ 🎫
custom 531889006346190044274🤣31🔥15❤9🤨3😨2🥰1
Сергею Рыжикову – 46! 🧤 Сегодня свой день рождения отмечает легендарный вратарь «Рубина» Сергей Рыжиков ❤️💚 🧤 – ты стоишь стеной, Рыжиков Сергей!
custom 5230954452072033873330❤65custom 533473873759726345125custom 531889006346190044216👍11
Иванов 🆚 Бабаев 🤔 Устроили челлендж для новичков «Рубина» 🇷🇺 За кого болели? ❤️ – Иванов 🔥– Бабаев
🔥121❤47custom 531889006346190044218custom 54002274196741616835😭2custom 53192437325438903022🥰1
Андерсон Арройо не попал в окончательный состав сборной Колумбии ⚽️🇨🇴 Ранее футболист «Рубина» вошел в расширенный список, но не был включен финальный состав 🇷🇺
custom 5400227419674161683170😭119🫡25custom 531889006346190044224💔10😁3❤2
«Рубин» в топ-6 Альфа-Банк РПЛ по итогам 9️⃣ тура 🇷🇺📊 Уходим на международную паузу до 11 октября 📅 Как вам результаты, рубиновые? Делитесь мнением в комментариях ✍️👇
custom 5318890063461900442188😨39❤22🔥13😁6🤣4😭1custom 53347387375972634511
«Будет сложнейший матч. Нам нужна энергия от всех, кто выходит на поле, и от тех, кто находится на скамейке» ⚽️ За кадром гостевой ничьи с «Родиной»: речь Франка Артиги на установке и перед выходом на поле, реакция игроков и тренеров на ключевые моменты игры, а также атмосфера в раздевалке после матча 🇷🇺 Сюжет с игры – уже на Rubin TV ⏯️⏯️ 💙 СМОТРЕТЬ В VK ВИДЕО 📺 СМОТРЕТЬ НА YOUTUBE
❤36custom 531889006346190044228custom 540022741967416168310🥰2🔥1🤣1
Игроки «Рубина» отправились в свои национальные сборные ⚡️🌍 🇷🇺 – Удачи и без травм, парни!
custom 5318890063461900442154custom 540022741967416168341❤15🔥7
Showing the 12 most recent of 325 posts we hold for @fcrk1958. 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.
@fcrk1958 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 49 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
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.
Read from Telegram’s recommendation API, most recently 23 August 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.
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.
This channel appears in 47 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.
Wikipedia
5 Wikipedia articles name this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“ФК «Рубин»” (@fcrk1958), 54,034 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/fcrk1958.
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.