Telegram RegisterThe public register of Telegram
Telegram profile photo for ФК «Торпедо Миасс»

Channel

ФК «Торпедо Миасс»

@torpedomiass

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,416subscribers

+28 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001445757803
TypeChannel
Username@torpedomiass
Created18 January 2020measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live9 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/torpedomiass

Growth

1,3881,4231,405.57 August 2026 — 1,388 subscribers7 August 2026 — 1,388 subscribers10 August 2026 — 1,389 subscribers16 August 2026 — 1,396 subscribers23 August 2026 — 1,414 subscribers26 August 2026 — 1,418 subscribers29 August 2026 — 1,423 subscribers1 September 2026 — 1,422 subscribers4 September 2026 — 1,418 subscribers9 September 2026 — 1,416 subscribers1,4167 August 20269 September 2026
10 measurements spanning 33 days, net +28. 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 1,383–1,428 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 13:381,416-2
4 Sept 2026, 03:381,418-4
1 Sept 2026, 01:041,422-1
29 Aug 2026, 08:571,423+5
26 Aug 2026, 14:341,418+4
23 Aug 2026, 13:141,414+18
16 Aug 2026, 15:441,396+7
10 Aug 2026, 09:081,389+1
7 Aug 2026, 11:011,388no change
7 Aug 2026, 10:541,388first reading

Engagement

18 posts held, back to 16 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 18 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

368 reactions across 18 posts, in 11 distinct kinds. The most used accounts for 26.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52627037136124841029926.9%
7119.3%
❤‍🔥4612.5%
👏4512.2%
🔥338.97%
😡297.88%
😢267.07%
👍92.45%
😁61.63%
🤝30.815%
🏆10.272%

Custom emoji. One row above is a 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 count beside it is 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 18 of the 18 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 368 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 16 July 2026 to 1 August 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

1 Aug 2026, 13:20 UTC515 views40 reactionsread 7 August 2026
Photo

Сегодня вновь без победы. Вновь без забитых мячей. Итоговый счёт на табло - не тот, которого ждали мы, наши болельщики и все, кто в нас верит. Не опускаем руки! Мы вернёмся на тренировочное поле ещё злее и голоднее до побед. Эта чёрная полоса закончится только благодаря нашей работе, а не сама по себе. Спасибо всем, кто с нами, несмотря ни на что. Ваша поддержка сейчас важна как никогда. Мы слышим вас и будем битьс

custom 526270371361248410220😡13❤‍🔥3😁21🏆1

1 Aug 2026, 10:32 UTC526 views8 reactionsread 7 August 2026
Photo

📹 Прямая трансляция матча 3-го тура ЛЕОН-вторая лига "А", группа "Серебро" между командами "Иртыш" (Омск) и "Торпедо Миасс". Начало в 16:00 (14:00 по мск). Смотрим! 🖥 ТРАНСЛЯЦИЯ

❤‍🔥5🔥3

1 Aug 2026, 10:28 UTC521 views13 reactionsread 7 August 2026
Photo

Стартовый состав на матч против омского "Иртыша".

7❤‍🔥3🔥3

30 Jul 2026, 05:08 UTC642 views20 reactionsread 7 August 2026
Photo

⚽ Следующий матч играем на выезде! В рамках 3-го тура ЛЕОН-вторая лига "А", группа "Серебро" торпедовцы 1 августа в гостях сыграют против команды "Иртыш" (Омск).

14❤‍🔥5🔥1

26 Jul 2026, 15:30 UTC929 views20 reactionsread 7 August 2026
Photo

📈 Актуальная таблица ЛЕОН-вторая лига А, группа "Серебро". А также другие результат 2-го тура: ⚽ "Динамо Ставрополь" - "Иртыш" (Омск) - 1:1 (1:0) Голы: Коробочкин – автогол, 40 (1:0), Разборов, 55 (1:1) ⚽ "Динамо-2" (Москва) – "Тюмень" - 0:2 (0:0) Голы: Демьянов, 46 (0:1), Бабаев, 84 (0:2)

custom 52627037136124841029😡8❤‍🔥21

26 Jul 2026, 15:30 UTC784 views27 reactionsread 7 August 2026
Photo

Минимально проигрываем второму составу питерского "Зенита"...впереди много работы и мы будем сильнее! Только "Торпедо"! Только победа!

😢11custom 52627037136124841028😡5😁21

24 Jul 2026, 03:35 UTC922 views25 reactionsread 7 August 2026
Photo

⚽ В матче второго тура ЛЕОН-вторая лига "А", группа "Серебро" футбольный клуб "Торпедо Миасс" принимает команду "Зенит-2" (Санкт-Петербург). Игра состоится 25 июля, на стадионе "Труд". Начало в 16:00.

👏12custom 526270371361248410210❤‍🔥21

20 Jul 2026, 14:59 UTC≈1,070 views17 reactionsread 7 August 2026
Photo

Актуальная таблица ЛЕОН-вторая лига А, группа "Серебро". А также другие результат 1-ого тура: ⚽ "Зенит-2" (Санкт-Петербург) - "Динамо Ставрополь" - 3:0 (1:0) Голы: Левандовский, 15 (1:0), Ханов, 57 (2:0), Иванов, 65 (3:0) ⚽ "Иртыш" (Омск) - "Амкар-Пермь" - 0:3 (0:2) Голы:Галлямов, 5 (1:0), Усов, 32 (2:0), Усов, 76 (3:0)

🔥93😡3❤‍🔥1👍1

20 Jul 2026, 14:05 UTC932 views9 reactionsread 7 August 2026
Photo

📹 Кирилл Панченко и Владимир Федоров прокомментировали итоги матча 1-ого тура ЛЕОН-вторая лига "А", группа "Серебро" между командами "Торпедо Миасс" и "Динамо-2" (Москва). ▶️ ПРЕСС-КОНФЕРЕНЦИЯ

🔥43❤‍🔥2

18 Jul 2026, 13:33 UTC≈1,060 views27 reactionsread 7 August 2026
Photo

Начинаем сезон 26-27 в ЛЕОН-вторая лига "А", группа "Серебро" с домашнего поражения от двойки столичного "Динамо".

😢15custom 52627037136124841028❤‍🔥2😁2

18 Jul 2026, 10:45 UTC947 views7 reactionsread 7 August 2026
Photo

💪 Состав торпедовцев на сегодняшний матч! Вратарь Роман Ковалев. В защите Кузьмин, Балахонов, Лопатько, Бакшеев. В центре Ибрагимов и Слободчиков. Атакующая линия Якименко, Котельников, Максим Тарасов и Ярослав Тарасов. В запасе: Беззубов, Столбов, Замятин, Палкин, Ульяновский, Килин и Анферов.

custom 52627037136124841026👍1

18 Jul 2026, 10:05 UTC785 views7 reactionsread 7 August 2026
Photo

❗Начинаем сезон 26/27 в группе "Серебро" ЛЕОН-вторая лига "А"! 📹 Смотрите прямое включение с матча открытия, где миасское "Торпедо" принимает вторую команду московского "Динамо". Болеем за наших парней! ▶️ ТРАНСЛЯЦИЯ

🔥6👍1

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

Mentions

Named by 1 registered channel — 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.

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

“ФК «Торпедо Миасс»” (@torpedomiass), 1,416 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/torpedomiass.

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.