Доброй ночи, рубиновые ❤️💚 Уходим на выходные в отличном настроении ⚽️
custom 5318890063461900442101❤🔥17❤15🔥3

Channel
@fcrk1958
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Telegram's recommendations · Referenced elsewhere · Cite this entry
53,189subscribers
-2,323 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 | 6 November 2026 |
| Measurements held | 61 |
| Confirmed unchanged | 1 time, most recently 6 November 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 20:07 | 53,189 | +167 |
| 5 Nov 2026, 19:10 | 53,022 | -12 |
| 4 Nov 2026, 15:57 | 53,034 | -27 |
| 3 Nov 2026, 18:29 | 53,061 | -16 |
| 2 Nov 2026, 17:27 | 53,077 | -87 |
| 1 Nov 2026, 19:21 | 53,164 | -25 |
| 31 Oct 2026, 15:46 | 53,189 | -18 |
| 30 Oct 2026, 17:58 | 53,207 | -22 |
| 29 Oct 2026, 18:21 | 53,229 | -27 |
| 28 Oct 2026, 17:54 | 53,256 | -18 |
| 27 Oct 2026, 18:18 | 53,274 | -33 |
| 26 Oct 2026, 15:51 | 53,307 | -31 |
| 25 Oct 2026, 19:05 | 53,338 | -14 |
| 24 Oct 2026, 16:16 | 53,352 | -11 |
| 23 Oct 2026, 17:48 | 53,363 | -29 |
| 22 Oct 2026, 15:51 | 53,392 | -51 |
| 21 Oct 2026, 09:56 | 53,443 | -34 |
| 20 Oct 2026, 09:16 | 53,477 | -41 |
| 19 Oct 2026, 08:16 | 53,518 | -28 |
| 18 Oct 2026, 07:19 | 53,546 | first reading |
583 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 187 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 6 November 2026 |
|---|---|
| Posts held | 583 (4 August 2026 – 6 November 2026) |
| Views total | 1,006,071 |
| Reactions total | 32,184 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Nov 2026, 00:21 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 7 November 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 210 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.
89,472 reactions across 572 posts, in 82 distinct kinds. The most used accounts for 31.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5318890063461900442 | 27,821 | 31.1% | |
| ❤ | 16,968 | 19.0% | |
| 🤣 | 8,030 | 8.97% | |
| custom 5334738737597263451 | 5,029 | 5.62% | |
| 🔥 | 3,735 | 4.17% | |
| 😭 | 2,286 | 2.55% | |
| 💔 | 1,710 | 1.91% | |
| 👍 | 1,689 | 1.89% | |
| custom 5402194428796379700 | 1,683 | 1.88% | |
| custom 5402459737516190082 | 1,568 | 1.75% | |
| custom 5424929155277945471 | 1,354 | 1.51% | |
| custom 5402279718256944234 | 1,216 | 1.36% | |
| custom 5400227419674161683 | 1,056 | 1.18% | |
| 🤨 | 1,053 | 1.18% | |
| custom 5402554561804149844 | 897 | 1.00% | |
| custom 5402156950911752156 | 770 | 0.861% | |
| ❤🔥 | 769 | 0.859% | |
| 😁 | 756 | 0.845% | |
| 😨 | 686 | 0.767% | |
| custom 5402570466068045810 | 660 | 0.738% | |
| 62 further kinds | 9,736 | 10.9% |
Custom emoji. 10 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 583 of the 583 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 92,438 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 583 most recent posts we hold, published 4 August 2026 to 6 November 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.
Telegram’s own ‘edited’ marker: 31 of 197 posts held from the last 30 days (15.7%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Доброй ночи, рубиновые ❤️💚 Уходим на выходные в отличном настроении ⚽️
custom 5318890063461900442101❤🔥17❤15🔥3
Олег Кузьмин ответил на вопросы журналистов после матча с «Локомотивом» ⚽️ – об игре команды и реализации моментов – о том, как удалось одержать две победы подряд – о неудачных моментах в сегодняшней игре 💙СМОТРЕТЬ В VK ВИДЕО 📺СМОТРЕТЬ НА YOUTUBE
❤34custom 542492004135736102114custom 53188900634619004428🔥3
Впервые с 2017 года обыграли «Локо» в Москве 👏🏻 9 лет назад Олег Кузьмин выводил команду с капитанской повязкой, а сегодня – в роли тренера ⚽️ Браво, Олег Александрович! ⚽️
❤145🔥36custom 531889006346190044228custom 542492004135736102111💯4👏3
«Мы ехали сюда брать очки! Я в вас верил и горжусь вами!» ⚽️ Важные слова тренера команде в победной раздевалке ⚽️
❤89🔥20custom 542492004135736102110custom 53188900634619004428👍1
Пока ждём победную раздевалку – изучаем статистику игры с «Локомотивом» 🔥😉
❤🔥60custom 531889006346190044219❤10custom 54249200413573610212
Что творят эти парни?! Браво, команда! 😍 Накидаем реакций под постом, и мы выкладываем победную раздевалку🔥 🇷🇺 – ДЕЛАЕМ!
custom 5318890063461900442244❤41🤝8🔥6❤🔥1
Эдди, сколько очков сегодня забрали?🤔 Ставим 3️⃣ под постом 👇
custom 5391167306422327939198❤21😁11custom 53188900634619004429
Егор Тесленко – лучший игрок матча против «Локомотива» ⭐️⚽️ Браво, Егор 👏👏👏
❤122custom 531889006346190044239custom 540028000725374356632👍2
➕3️⃣ 😉
🤣143❤26😁13custom 54002800072537435666😨3🤨2❤🔥1👍1
В честь победы дарим скидку на домашний матч с «Зенитом» 🔥 Переходи на официальный сайт и забирай билет по промокоду ПОБЕДА ❤️💚 ❗️Торопитесь: промокод действует ровно одни сутки на все сектора! 🎫 КУПИТЬ БИЛЕТЫ 🎫
❤68👍15🔥10custom 54002800072537435667🤣4custom 53188900634619004423
Автор победного гола Егор Тесленко на связи ⚽️ Спасибо всем болельщикам на стадионе и у экранов за поддержку ❤️💚 ⚽️ – Браво, Тес! Браво, команда!
custom 5318890063461900442187❤43👍19custom 540028000725374356610🔥5❤🔥2
ЗАСЛУЖЕННАЯ ПОБЕДА! ОБЫГРЫВАЕМ «ЛОКОМОТИВ» В МОСКВЕ 🔥😍 🇷🇺 – МЫ «РУБИН», НАС НЕ ОСТАНОВИТЬ!
custom 5318890063461900442359❤78❤🔥31🤣11👍8🔥2🤪2
Showing the 12 most recent of 583 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 3 posts 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.
We recorded 1 post on @fcrk1958 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. 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 51 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“ФК «Рубин»” (@fcrk1958), 53,189 subscribers as measured 6 November 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.