Channel
@fcreverse
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
123subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002220421089 |
|---|---|
| Type | Channel |
| Username | @fcreverse |
| Description | Медиафутбольная команда из Санкт-Петербурга Участники Зимнего турнира ОЛЕ Пари Участники Медиафутбольного Урожая Талантов от М5 Финалисты отбора Winline Уличного Футбола в Санкт-Петербурге |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/fcreverse |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 03:17 | 123 | no change |
| 8 Aug 2026, 06:02 | 123 | first reading |
20 posts held, back to 13 June 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 1 pageof 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 20 posts for this entry, the most recent from 13 August 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 4 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.
236 reactions across 17 posts, in 16 distinct kinds. The most used accounts for 25.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 61 | 25.8% | |
| 🔥 | 33 | 14.0% | |
| custom 5328043536417843380 | 29 | 12.3% | |
| 😢 | 18 | 7.63% | |
| 🥰 | 17 | 7.20% | |
| custom 5319070993254201336 | 13 | 5.51% | |
| 👍 | 13 | 5.51% | |
| ❤🔥 | 12 | 5.08% | |
| 🏆 | 11 | 4.66% | |
| 👎 | 7 | 2.97% | |
| custom 5246794802560774143 | 5 | 2.12% | |
| 😎 | 5 | 2.12% | |
| 💘 | 4 | 1.69% | |
| ⚡ | 3 | 1.27% | |
| 🤣 | 3 | 1.27% | |
| 💩 | 2 | 0.847% |
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 17 of the 20 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 236reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 13 June 2025 to 13 August 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.
💯 Болеем за наших Как вы помните, мы участвовали в отборочном этапе «Winline Уличный Футбол», уступив в финале команде Тимощука Но кураторы выделили из нашей команды Ваню Клеветова, который уже 16 числа будет феерить в составе «Андердогов» Желаем Ване удачи и надеемся, что у него получится пробиться с драфта в финальный этап сезона 🔥 🤩@fcreverse
custom 53280435364178433806🔥4custom 53190709932542013364
🤩MATCHDAY🤩 сегодня сыграем в полуфинале COPA 2025 🏆 Верим в нашу команду! Ну и конечно же, приходим поддержать нас, а играть будем тут ⬇️⬇️ Поселок Репино, ул. Нагорная 18:30 🤩@fcreverse
custom 53280435364178433805❤3🔥3🤣1
🤩НАМ 1 ГОД! 🤩 Ровно год назад началась история нашей команды — с первого мяча, первого матча, первых эмоций. За это время мы выросли, стали сильнее, сыграннее и сплочённее. Было всё: победы, поражения, яркие моменты, которые навсегда останутся с нами. ⚽🔥 Огромное спасибо каждому, кто был и остаётся частью этой команды — игрокам, болельщикам и друзьям. Вы — наше сердце. ❤️ Это только начало. Впереди — новые цели, …
custom 53280435364178433808🏆5custom 53190709932542013365❤2
Дорогой Влад! От всей команды REVERSE поздравляем тебя с этим важным событием – бракосочетанием! Желаем вам с Никой долгой и счастливой совместной жизни, взаимопонимания, крепкой любви и семейного благополучия. Горько! 🤩@fcreverse
❤15❤🔥9👍8🔥3
🥲
😢7❤6👎4💩2custom 53280435364178433801
🤩 проигрываем 5:3 увидимся в плей-офф) @fcreverse
🥰5😢5👎3
стартуем с минуты на минуту 🤩🤩🤩
❤6👍5💘4
✉️Главный матч группового этапа Copa 2025 В третьем туре в соперниках VKFT🤩, особой личной истории с данной командой у нас нет, но победа в медиадерби сегодня очень важна Стартуем уже через 2 часа на поле в Репино 🤩@fcreverse
❤4⚡3🏆3
Параллельно сегодня наша стена - Никита Ивлев дебютировал в молодежной лиге по пляжному футболу, отгрузив Локомотиву классную банку 🤩 🤩@fcreverse
❤6😎5🥰4
💎WW, Слоны Забираем волевую победу красным мячом во втором туре, 5:4 Через неделю матч за первое место в группе! ⌛ 🤩@fcreverse
❤5🔥4🥰3
✏️Тур Copa 2025 уже сегодня! У кого есть желание посетить прекрасный курортный район в такую хорошую погоду, а так же поддержать нас, тогда ⬇️ ждём вас по адресу: Fc Reverse vs 78Club 16.07.2025 17:00 Поселок Репино, ул. Нагорная 🤩@fcreverse
❤4🔥4custom 53280435364178433804
Зато нас Дима Ликс сфоткал 🥸 🤩 @fcreverse
🔥8custom 52467948025607741435custom 53280435364178433805
Showing the 12 most recent of 20 posts we hold for @fcreverse. 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 — 244,863 of 1,481,243entries 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.
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.
Named by 6 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.
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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“FC Reverse” (@fcreverse), 123 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/fcreverse.
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.