А что если… 🚆Подписаться на Бронепоезд
🤯233🤣81❤31custom 52422229687880002154custom 52424318373425732174custom 52539513304724625432custom 52424153833228619101custom 52425990575992744551

Channel
@loko76
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Posts edited after publishing · Polls · Citations · Telegram's recommendations · Cite this entry
37,485subscribers
+1,949 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001906120014 |
|---|---|
| Type | Channel |
| Username | @loko76 |
| Description | Крепкий юмор, эмоции и немного «гениальной» аналитики. Партнер @fonbet_official Лучший телеграм-канал КХЛ о клубе сезона 2025/26. Связь: @NLeba ВК: https://vk.com/bronepoezd50 По вопросам чата: @denis_igumn0v @kiselnikovgame |
| Created | 1 September 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/loko76 |
Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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 |
|---|---|---|
| 25 Sept 2026, 06:59 | 37,485 | -72 |
| 18 Sept 2026, 20:57 | 37,557 | +2,490 |
| 16 Sept 2026, 08:58 | 35,067 | +82 |
| 14 Sept 2026, 13:57 | 34,985 | -21 |
| 12 Sept 2026, 22:40 | 35,006 | -46 |
| 11 Sept 2026, 00:20 | 35,052 | -32 |
| 8 Sept 2026, 01:58 | 35,084 | -62 |
| 5 Sept 2026, 01:20 | 35,146 | -11 |
| 3 Sept 2026, 09:34 | 35,157 | +82 |
| 2 Sept 2026, 05:13 | 35,075 | +33 |
| 1 Sept 2026, 04:14 | 35,042 | -99 |
| 31 Aug 2026, 04:57 | 35,141 | -87 |
| 30 Aug 2026, 06:35 | 35,228 | -18 |
| 29 Aug 2026, 06:04 | 35,246 | -78 |
| 28 Aug 2026, 03:13 | 35,324 | -37 |
| 27 Aug 2026, 01:14 | 35,361 | -27 |
| 25 Aug 2026, 22:55 | 35,388 | -14 |
| 24 Aug 2026, 21:59 | 35,402 | -49 |
| 23 Aug 2026, 04:39 | 35,451 | -8 |
| 21 Aug 2026, 14:28 | 35,459 | first reading |
279 posts held, back to 2 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 89 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 26 September 2026 |
|---|---|
| Posts held | 279 (2 August 2026 – 26 September 2026) |
| Views total | 964,940 |
| Reactions total | 86,743 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 02:59 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 27 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 58 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.
140,299 reactions across 274 posts, in 74 distinct kinds. The most used accounts for 38.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤣 | 53,342 | 38.0% | |
| ❤ | 30,233 | 21.5% | |
| custom 5332651933247243199 | 8,102 | 5.77% | |
| custom 5231213241031500682 | 4,012 | 2.86% | |
| 💯 | 3,525 | 2.51% | |
| custom 5332276024824594879 | 3,396 | 2.42% | |
| custom 5253951330472462543 | 3,272 | 2.33% | |
| custom 5242431837342573217 | 3,225 | 2.30% | |
| custom 5242222968788000215 | 2,860 | 2.04% | |
| 🔥 | 2,212 | 1.58% | |
| custom 5242432709220935979 | 1,719 | 1.23% | |
| custom 5334757347690576054 | 1,663 | 1.19% | |
| custom 5265120251191796401 | 1,657 | 1.18% | |
| custom 5305694231711482780 | 1,526 | 1.09% | |
| custom 5456213924695277618 | 1,488 | 1.06% | |
| custom 5307499049983701812 | 1,402 | 0.999% | |
| 👍 | 1,229 | 0.876% | |
| custom 5307634624921370163 | 1,113 | 0.793% | |
| custom 5242599057599274455 | 1,037 | 0.739% | |
| custom 5335072817333436135 | 980 | 0.699% | |
| 54 further kinds | 12,306 | 8.77% |
Custom emoji. 15 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 279 of the 279 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 142,214 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 279 most recent posts we hold, published 2 August 2026 to 26 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @loko76. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 279 most recent posts we hold for this entry, published 2 August 2026 to 26 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2VtzqvPEevg | 1 | 25 September 2026 | 25 September 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 279 most recent posts we hold, published 2 August 2026 to 26 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
А что если… 🚆Подписаться на Бронепоезд
🤯233🤣81❤31custom 52422229687880002154custom 52424318373425732174custom 52539513304724625432custom 52424153833228619101custom 52425990575992744551
⌚ FONBET OVERTIME придумали в Ярославле, а значит, все знатоки болеют за «Локомотив»! На сайте вас уже ждёт квиз из 5 вопросов. За каждый правильный ответ вы получите баллы, а самые внимательные смогут заработать до 4 000 баллов! 🎁 Обменять баллы можно на подарки: ▪️ супербокс с приставкой; ▪️ карточки Героев #FONBETOVERTIME; ▪️ сувенирную шайбу. Список доступных призов обновляется каждый месяц — заглядывай!
❤55custom 524226593993579800214🔥8custom 52424318373425732174custom 52422229687880002153custom 52425990575992744551
Коротко о поездке в Хабаровск: 🚆Подписаться на Бронепоезд
🤣379💯52custom 525395133047246254328custom 52422229687880002156❤4🔥4🤯3😡2
Лучший игрок матча с «Амуром»?
The shares total 126%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
🤣97custom 526472957237661904551❤23custom 52424318373425732173custom 52424316612489144972custom 52425990575992744552🔥1custom 52422229687880002151
В Ярославле так сильно любят кошек, что решили проигрывать только тем командам, у которых на логотипе изображены киски 😻 🚆Подписаться на Бронепоезд
🤣316💯59custom 524227423351764497552❤20custom 526277456768798590710custom 52423561943785566417custom 52422229687880002154custom 52424318373425732171
⚡️Выяснились подробности перехода Ярослава Лихачёва в «Амур». Как сообщает источник, хабаровчане будут выплачивать «Локомотиву» по 2 миллиона рублей за каждую победу «Амура», когда Ярослав находился на льду. В Ярославле еще до начала игры было решено обменять 2 очка на 2 миллиона. 🚆Подписаться на Бронепоезд
🤣272❤39custom 524222296878800021529custom 524239689348865225712😡5custom 52424318373425732172😭1custom 52425990575992744551
Классическая вторая игра на Дальнем Востоке: 🚆Подписаться на Бронепоезд
🤣257custom 525395133047246254355💯43😭20❤4😡4custom 53347573476905760543custom 52422229687880002152
Главный тренер «Локомотива» на дальневосточном выезде: 🚆Подписаться на Бронепоезд
🤣312custom 524222296878800021572custom 524015219325589521457❤8💯3custom 52425990575992744552🔥1custom 52424318373425732171
«Голы в большинстве — для слабаков!» © Николаев 🚆Подписаться на Бронепоезд
❤335🔥76👏42🤣19custom 524243183734257321711💯6custom 52425990575992744556custom 52424316612489144974
Ребята, которые сделали для меня фигурки Исаева, Бензопилино и котика Иванова, придумали классную благотворительную историю ❤️ Залетайте к ним в группу, чтобы узнать все подробности 👉 https://vk.ru/wall-236358000_25
❤146👍24custom 524222296878800021517custom 52424318373425732175👏3custom 52425990575992744552
Поддержим тех кто пока не с нами, но они с нами, но пока не с нами! 500 Каюмовых ☕ + 500 Березкиных 🛢️ = скорейшее выздоровление и победа над «Амуром» 🚆Подписаться на Бронепоезд
custom 5242559049978910942803custom 5242265205496392564747❤60custom 524259905759927445510🤣6custom 52424316612489144976custom 52422229687880002154custom 52424318373425732172
😏 Новость-молния! @news76 дарит деньги на бензин! Среди наших подписчиков мы разыграем пять топливных карт номиналом 5 000 рублей. Условия такие: — подписаться на 76.RU в МАКС; — отправить этот пост другу; — нажать на кнопку «Участвую». Розыгрыш продлится три недели — итоги 5 октября. Победителей будет пять! Всем удачи и бензина ❤️🔥 Реклама. О рекламодателе
🔥21🤣14❤8🤯4😡3custom 52424318373425732172custom 52422229687880002151custom 52425990575992744551
Showing the 12 most recent of 279 posts we hold for @loko76. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
@loko76 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.
The 5 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
Лучший игрок матча с «Амуром»?
The shares total 126%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Лучший игрок матча с «Адмиралом»?
The shares total 135%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Лучший игрок матча с «Барысом»?
The shares total 219%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Лучший игрок матча с «Авангардом»?
The shares total 216%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
С каким девизом пойдем за 3-м Кубком?
The shares total 146%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 279 most recent posts we hold, published 2 August 2026 to 26 September 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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 10 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.
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 2 September 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 23 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“50 оттенков бронепоезда | ХК «Локомотив» Ярославль” (@loko76), 37,485 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/loko76.
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.