А теперь настал черёд команды ЛФИ показать свою силу. Уже завтра, в 15:00, на Коробке они встретятся с командой ФИВТ. Приглашаем всех присоединиться к текстовой трансляции события! → t.me/mv_diht_lpr_2026
❤7

Channel
@mv_lpr_rt_2025
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
574subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002630383063 |
|---|---|
| Type | Channel |
| Username | @mv_lpr_rt_2025 |
| Created | Between 1 March 2025 and 1 June 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 2 times, most recently 15 August 2026 |
| On Telegram | t.me/mv_lpr_rt_2025 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 23:07 | 574 | no change |
| 7 Aug 2026, 06:01 | 574 | first reading |
19 posts held, back to 1 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 19 posts for this entry, the most recent from 29 May 2026. An engagement rate over an empty window would be a number about nothing.
815 reactions across 19 posts, in 19 distinct kinds. The most used accounts for 41.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5330560151030088591 | 341 | 41.8% | |
| custom 5346222977635602359 | 235 | 28.8% | |
| ❤ | 57 | 6.99% | |
| custom 5445081154715666709 | 56 | 6.87% | |
| custom 5335030030869224461 | 39 | 4.79% | |
| ❤🔥 | 13 | 1.60% | |
| 💔 | 12 | 1.47% | |
| custom 5352850618979460811 | 11 | 1.35% | |
| 🏆 | 11 | 1.35% | |
| ⚡ | 9 | 1.10% | |
| 🔥 | 9 | 1.10% | |
| 🐳 | 7 | 0.859% | |
| 😨 | 4 | 0.491% | |
| 😍 | 3 | 0.368% | |
| 🤬 | 3 | 0.368% | |
| 😱 | 2 | 0.245% | |
| 👀 | 1 | 0.123% | |
| 💅 | 1 | 0.123% | |
| 🤯 | 1 | 0.123% |
Custom emoji. 5 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 19 of the 19 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 815reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 1 June 2025 to 29 May 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.
А теперь настал черёд команды ЛФИ показать свою силу. Уже завтра, в 15:00, на Коробке они встретятся с командой ФИВТ. Приглашаем всех присоединиться к текстовой трансляции события! → t.me/mv_diht_lpr_2026
❤7
Сезон Матчей Века 2026 начинается! Присоединяйтесь к трансляции первого МВ в этом году: ФАЛТ принимает команду ФРТК на своём поле в Жуковском! https://t.me/mv_falt_rt_2026
❤8
В заключительном студенческом Матче Века сезона 24-25 команда ЛФИ одержала победу над РТ со счётом 77:59!
custom 533056015103008859199custom 534622297763560235943custom 544508115471566670920❤10🔥4❤🔥3
Матч завершён!
custom 533056015103008859178custom 534622297763560235933❤🔥6custom 53350300308692244615
Гол! ЛФИ 77:59 РТ Картель!
custom 534622297763560235943❤6❤🔥1custom 53305601510300885911
Гол! ЛФИ 77:58 РТ Бирюков!
custom 533056015103008859146custom 53462229776356023594😨2
🟥 Красная карточка Арсению Мерзлякову! 🟥 Красная карточка Ростиславу Гусакову! Небольшая стычка на поле, Вербов не жалеет.
custom 544508115471566670930custom 53462229776356023596🤯1custom 53305601510300885911
Гол! ЛФИ 76:58 РТ Серебряков!
custom 533056015103008859129❤5custom 53462229776356023593🤬1😨1
Гол! ЛФИ 75:58 РТ Закирьянов!
custom 534622297763560235923custom 53305601510300885917🔥2❤1
Гол! ЛФИ 75:57 РТ Зеркально!
custom 533056015103008859124custom 53462229776356023596🔥2🤬2
30 минут до конца матча!
custom 533503003086922446113custom 53462229776356023595❤1❤🔥1
Гол! ЛФИ 74:57 РТ
custom 534622297763560235930custom 533503003086922446111❤🔥1🐳1custom 54450811547156667091
Showing the 12 most recent of 19 posts we hold for @mv_lpr_rt_2025. 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 — 782,750 of 1,480,975entries 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.
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 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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“Матч Века ЛФИ – РТ 2025” (@mv_lpr_rt_2025), 574 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/mv_lpr_rt_2025.
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.