Telegram RegisterThe public register of Telegram
Telegram profile photo for МХК «Авто»

Channel

МХК «Авто»

@mhc_avto

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Polls · Citations · Telegram's recommendations · Cite this entry

7,338subscribers

+114 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001630607842
TypeChannel
Username@mhc_avto
Description☑️ Официальный телеграм-канал молодёжной хоккейной команды «Авто» 📍Екатеринбург 📱Наши соцсети: VK: https://vk.com/mhc_avto TikTok: @mhc_avto_ekb
Created11 March 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live15 November 2026
Measurements held28
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/mhc_avto

Topic

Sports — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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.

Growth

7,2097,5397,3747 August 2026 — 7,224 subscribers7 August 2026 — 7,224 subscribers7 August 2026 — 7,227 subscribers11 August 2026 — 7,221 subscribers13 August 2026 — 7,209 subscribers17 August 2026 — 7,211 subscribers20 August 2026 — 7,214 subscribers24 August 2026 — 7,230 subscribers27 August 2026 — 7,428 subscribers30 August 2026 — 7,429 subscribers1 September 2026 — 7,427 subscribers5 September 2026 — 7,433 subscribers10 September 2026 — 7,449 subscribers14 September 2026 — 7,439 subscribers19 September 2026 — 7,441 subscribers29 September 2026 — 7,470 subscribers6 October 2026 — 7,486 subscribers12 October 2026 — 7,501 subscribers15 October 2026 — 7,495 subscribers18 October 2026 — 7,503 subscribers21 October 2026 — 7,539 subscribers24 October 2026 — 7,532 subscribers27 October 2026 — 7,368 subscribers30 October 2026 — 7,364 subscribers2 November 2026 — 7,360 subscribers6 November 2026 — 7,365 subscribers9 November 2026 — 7,352 subscribers15 November 2026 — 7,338 subscribers7,3387 August 202615 November 2026
28 measurements spanning 100 days, net +114. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 7,160–7,589 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)SubscribersChange
15 Nov 2026, 13:067,338-14
9 Nov 2026, 19:287,352-13
6 Nov 2026, 02:157,365+5
2 Nov 2026, 14:527,360-4
30 Oct 2026, 17:357,364-4
27 Oct 2026, 19:407,368-164
24 Oct 2026, 14:007,532-7
21 Oct 2026, 19:577,539+36
18 Oct 2026, 11:387,503+8
15 Oct 2026, 14:207,495-6
12 Oct 2026, 19:517,501+15
6 Oct 2026, 10:017,486+16
29 Sept 2026, 07:177,470+29
19 Sept 2026, 02:397,441+2
14 Sept 2026, 13:157,439-10
10 Sept 2026, 21:587,449+16
5 Sept 2026, 21:577,433+6
1 Sept 2026, 14:267,427-2
30 Aug 2026, 00:047,429+1
27 Aug 2026, 05:127,428first reading

Engagement

158 posts held, back to 5 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 38 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
17.2%
avg views ÷ 7,338 subscribers
Avg views / post
1,260
108 posts measured
Reaction rate
5.03%
reactions ÷ views · ER floor
Posts in window
108
of 158 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 November 2026
Posts held158 (5 August 2026 – 16 November 2026)
Views total136,027
Reactions total6,844
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 14:37 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.

What this channel posts

Photos
≈10,100
Videos
≈2,920
Links
≈1,000

Lifetime counters from Telegram’s own channel header, read 16 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.

Video runtime
19m 52s
Average length
29s

Measured directly from 41 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.

Reaction mix

10,945 reactions across 157 posts, in 28 distinct kinds. The most used accounts for 54.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤5,97054.5%
🔥1,70315.6%
❤‍🔥5424.95%
🏆4013.66%
😭2342.14%
💔1971.80%
👏1821.66%
👍1691.54%
custom 54338247841672147431581.44%
🤣1471.34%
custom 54450859521941240001411.29%
👀1371.25%
custom 52494836625414688441351.23%
🎉1050.959%
custom 54339910509412029981010.923%
🤩990.905%
💘820.749%
😍790.722%
💯670.612%
😢650.594%
8 further kinds2312.11%

Custom emoji. 4 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 158 of the 158 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 10,945 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 158 most recent posts we hold, published 5 August 2026 to 16 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.

Recent posts

Telegram’s own ‘edited’ marker: 9 of 108 posts held from the last 30 days (8.33%) 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).

16 Nov 2026, 14:00 UTC442 views55 reactionsread 16 November 2026
Photo

Давайте глянем, что получилось 📸 🅰️ @mhc_avto

❤37🔥12custom 52494836625414688445👏1

16 Nov 2026, 13:35 UTC≈1,370 views100 reactionsread 16 November 2026
Video

Оцените творчество начинающего фотографа 😁 🅰️ @mhc_avto

❤54🔥28👏13🏆2custom 54338247841672147432custom 54450859521941240001

16 Nov 2026, 11:14 UTC≈1,000 views94 reactionsread 16 November 2026
Video

Кто потерял Лавра — он на тренировках по конькобежному спорту 😁 🅰️ @mhc_avto

❤64🔥21💯8👀1

15 Nov 2026, 11:32 UTC≈1,360 views78 reactionsread 16 November 2026
Photo

Не все победы даются легко 😮‍💨 🅰️ @mhc_avto

❤58👏13💔7

15 Nov 2026, 09:35 UTC≈1,350 views85 reactionsread 16 November 2026
Photo

Герман, поздравляем с новой отметкой в карьере 😎 🅰️ @mhc_avto

❤65👏20

15 Nov 2026, 08:45 UTC≈1,300 views81 reactionsread 16 November 2026
Photo

Выбор команды 🤝 Выбор болельщиков Спаситель Сава Жиров — лучший игрок матча 😁 🅰️ @mhc_avto

❤64🔥16custom 54339910509412029981

15 Nov 2026, 08:31 UTC≈1,250 views67 reactionsread 16 November 2026
Photo

Передача фуражки прошла успешно 🫡 🅰️ @mhc_avto

❤49🏆10👏8

15 Nov 2026, 07:32 UTC≈1,270 views55 reactionsread 16 November 2026
Photo

Уже восстановили нервную систему? Тогда листайте кадры с матча 🤣 🅰️ @mhc_avto

❤41🔥12🏆2

15 Nov 2026, 07:00 UTC≈1,130 views81 reactionsread 16 November 2026
Photo

Мотя, давай фотку сделаем? 🅰️ @mhc_avto

❤50🔥20🏆8👍3

14 Nov 2026, 15:28 UTC≈1,260 views41 reactionsread 16 November 2026
Photo

Нападающий Антон Лыков — о победе над «АКМ-Юниор»: — Получились хорошие два периода: владели инициативой и шайбой, не давали сопернику играть в нашей зоне. В конце третьего немного расслабились, потеряли концентрацию, пропустили три гола. Хорошо, что получилось выйти вперёд и выиграть игру. — После двух периодов команда вела со счётом 3:0, но в третьем позволила сопернику сравнять счёт. Что произошло с командой в з…

❤26🔥10💯5

14 Nov 2026, 15:26 UTC678 views29 reactionsread 14 November 2026
Photo

Нападающий «Авто» Иван Губин поделился комментариями после матча с «АКМ-Юниор»: — Хорошие 50 минут, потом подрасслабились, пропустили три гола. В итоге хорошо, что мы смогли забить ещё одну шайбу и выиграть. — Сегодня ты отметился двумя результативными передачами. Как оценишь свою игру и взаимодействие с партнёрами? — В целом доволен. Два паса были рабочими, а там уже Савелий Жиров хорошо забил. — Насколько тяжело…

❤22custom 54180191928488095834🔥3

14 Nov 2026, 14:53 UTC815 views0 reactionsread 14 November 2026
Poll

⭐️ ЛУЧШИЙ ИГРОК МАТЧА: версия болельщиков

  1. #12 Иван Губин6%
  2. #20 Сергей Соколкин35%
  3. #46 Матвей Чумаков12%
  4. #58 Савелий Жиров42%
  5. #87 Антон Лыков5%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Showing the 12 most recent of 158 posts we hold for @mhc_avto. 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.

Posts edited after publishing

@mhc_avto 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.

First edit seen
9 November 2026
Most recent edit
9 November 2026

Polls

The 2 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.

14 Nov 2026, 14:53 UTCAnonymous Poll292 voters

⭐️ ЛУЧШИЙ ИГРОК МАТЧА: версия болельщиков

  1. #12 Иван Губин6%
  2. #20 Сергей Соколкин35%
  3. #46 Матвей Чумаков12%
  4. #58 Савелий Жиров42%
  5. #87 Антон Лыков5%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

7 Nov 2026, 11:06 UTCFinal Results509 voters

⭐️ЛУЧШИЙ ИГРОК МАТЧА: выбор болельщиков

  1. #20 Сергей Соколкин50%
  2. #57 Филипп Морозов10%
  3. #60 Данила Семейкин4%
  4. #97 Никита Афанасьев36%

Shares as published. No per-option vote count is published by Telegram, so none is 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 158 most recent posts we hold, published 5 August 2026 to 16 November 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.

Forward network

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.

Mentions

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.

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.

Appears in Telegram’s recommendations for other channels

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.

ХК «Автомобилист»
@hc_avtomobilist · 57,970
Telegram ranks this channel #2 of 97 here — alongside 96 others — read 23 August 2026
Молодежная хоккейная лига I МХЛ
@mhlrus · 49,517
Telegram ranks this channel #34 of 99 here — alongside 98 others — read 25 August 2026
Hockeymans78
@Hockeymans78 · 23,890
Telegram ranks this channel #55 of 90 here — alongside 89 others — read 15 September 2026
ФК «Урал»
@fc_uralEkb · 28,589
Telegram ranks this channel #62 of 95 here — alongside 94 others — read 8 September 2026
Селекционный отдел
@hockeyscout · 19,020
Telegram ranks this channel #64 of 77 here — alongside 76 others — read 4 October 2026

This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Cite this entry

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 15 November 2026 — this entry's latest reading, not the date you are reading this.

“МХК «Авто»” (@mhc_avto), 7,338 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/mhc_avto.

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.