Channel
@FiveMinutesForFighting
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
134subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003259417504 |
|---|---|
| Type | Channel |
| Username | @FiveMinutesForFighting |
| Description | Источник ценных сведений о боях на льду. Спросить за всё: @SergioSamoilov |
| Created | Between 1 October 2025 and 31 January 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/FiveMinutesForFighting |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 00:15 | 134 | no change |
| 7 Aug 2026, 17:42 | 134 | first reading |
20 posts held, back to 25 March 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 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 1 April 2026. 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 18 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.
37 reactions across 13 posts, in 10 distinct kinds. The most used accounts for 37.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 14 | 37.8% | |
| 👀 | 6 | 16.2% | |
| 🔥 | 5 | 13.5% | |
| ❤ | 3 | 8.11% | |
| 👍 | 2 | 5.41% | |
| 💩 | 2 | 5.41% | |
| 🫡 | 2 | 5.41% | |
| 🗿 | 1 | 2.70% | |
| 😐 | 1 | 2.70% | |
| 🤯 | 1 | 2.70% |
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 13 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 37reactions 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 25 March 2026 to 1 April 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.
🥊 ИГОРЬ ШЕСТЕРКИН ПОДРАЛСЯ!!! ЭТО НЕ ШУТКА! Что вообще происходит? Сначала Сергей Бобровский, затем Андрей Василевский, кто следующий из наших? Илья Сорокин? @hockeyonkp
👀4❤2
Судью завалили в потасовке – всем по 3 матча дисквалификации срочно!
Ну и куда без 🇨🇿 Адама Рашки, раз уж Спарта начала драться. Правда, дракой эту стычку с капитаном Пльзени 🇨🇿 Якубом Ержабеком назвать сложно - экс-Витязь-и-Спартак даже не сопротивлялся. Тем не менее, bitka по протоколу и по 5 минут каждому. 📹: Hokej.cz
🇨🇿 Иво Седлачек vs 🇨🇿 Аарон Ирвинг Через ЧМ по фигурке плавно кинули мостик в Чехию 🇨🇿 Здесь малыш Седлачек (179/71!!!) взял и завалил опытнейшего канадского защитника Ирвинга (185/90). Тот потом пытался грязно реваншироваться, но мы-то понимаем, что это уже не в зачет. Только в карму 👎 📹: Hokej.cz
❤1
А начало этой беспощадной любви положил танец 🛢 Коннора Мерфи против ⚔️ Коула Смита. Как раз параллельно в эти дни проходит ЧМ по фигурному катанию. Могли бы в парном разряде выступить 💃 📹: Sportsnet
😁1
🛢 Дарнелл Нерс по итогам эпизода подарил нам очередной, хоть и крайне омерзительный, стикер 😘😘😘
💩2🗿1😐1
Конец первого периода между ⚔️ Вегасом и 🛢 Эдмонтоном подарил нам вот это. Буквально реслинг под воротами. 📹: Gino Hard
😁2
🇺🇦 🇱🇻 Перенесёмся в балтийскую хоккейную лигу (есть и такая). Тут играли команды из Риги и Киева - по доброй китайской традиции, Киев играет вдали от дома в городе с чарующим названием Pinki, от которого все североамериканские легионеры рижского "Динамо" во все сезоны, как это принято нынче говорить, угорали. Это хоккей, это плей-офф - и это rivalry тоже получилось heated. В этом международном матче сошлись и игроки…
😁4🔥1
🐳 Зив Буйюм и 👑 Брэндт Кларк так хотели подраться, что одного судьи не хватило, чтобы это остановить. А зачем вообще надо было останавливать? 🤔 В итоге драки не было, а по 5 минут за драку обоим и по большой неспортивке до кучи - было. Здесь явно нужны судьи из КХЛ. 📹: B/R Open Ice
⛰️ Джон Мэнсон vs ✈️ Морган Бэррон Легенда-Мэнсон в своем стиле (быстро и коряво) привалил Бэррона. Ну штош, зато нам тайминг сэкономили ⏰ 📹: TSN
🦈 Зак Остапчук vs 🎵 Логан Майю После невнятного начала Остапчук взял себя в руки и уложил как минимум 10 правых боковых по голове Майю. Чистейшая победа единогласным решением ✅ 📹: Gino Hard
🔥2
Драка Дюхэйма, драка Дюхэйма... Как насчет драки Уилсона? 😆 🦅 Том Уилсон vs 🦣 Лоусон Краузе Ну, это было как всегда - плюс-минус эпохально. Удары, сальто, шоу. 📹: Gino Hard
🔥2👍1
Showing the 12 most recent of 20 posts we hold for @FiveMinutesForFighting. 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.
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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“Пять минут за драку ✊” (@FiveMinutesForFighting), 134 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/FiveMinutesForFighting.
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.