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

Channel

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

@torpedomoscow_fc

Verified by Telegram

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cross-platform identity · Cite this entry

14,376subscribers

+32 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001315345327
TypeChannel
Username@torpedomoscow_fc
DescriptionОфициальный канал футбольного клуба «Торпедо Москва». Правила сообщества: https://clck.ru/3Q8vw6
Created11 March 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live15 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/torpedomoscow_fc

Growth

14,34114,39014,365.56 August 2026 — 14,344 subscribers6 August 2026 — 14,341 subscribers7 August 2026 — 14,346 subscribers8 August 2026 — 14,367 subscribers9 August 2026 — 14,390 subscribers10 August 2026 — 14,381 subscribers11 August 2026 — 14,383 subscribers12 August 2026 — 14,373 subscribers13 August 2026 — 14,366 subscribers15 August 2026 — 14,376 subscribers14,3766 August 202615 August 2026
10 measurements spanning 9 days, net +32. 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 14,334–14,397 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 00:5814,376+10
13 Aug 2026, 15:0714,366-7
12 Aug 2026, 14:2714,373-10
11 Aug 2026, 15:2814,383+2
10 Aug 2026, 16:4114,381-9
9 Aug 2026, 13:2214,390+23
8 Aug 2026, 15:1014,367+21
7 Aug 2026, 14:0614,346+5
6 Aug 2026, 10:3114,341-3
6 Aug 2026, 04:3614,344first reading

Engagement

50 posts held, back to 3 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 20 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
17.7%
avg views ÷ 14,376 subscribers
Avg views / post
2,550
50 posts measured
Reaction rate
3.70%
reactions ÷ views · ER floor
Posts in window
50
of 50 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 15 August 2026
Posts held50 (3 August 202615 August 2026)
Views total127,510
Reactions total4,722
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 10:09 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
11,200
Videos
3,370
Links
3,560

Lifetime counters from Telegram’s own channel header, read 15 August 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
5m 10s
Average length
28s

Measured directly from 11 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

4,366 reactions across 47 posts, in 23 distinct kinds. The most used accounts for 31.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53934150603768150101,38131.6%
🔥57713.2%
55412.7%
👍4299.83%
👎3437.86%
👏2144.90%
🤣1954.47%
🙏1623.71%
😨821.88%
😢741.69%
🤯701.60%
🎉641.47%
😭631.44%
🏆380.87%
😁370.847%
🤝300.687%
💔160.366%
😐120.275%
🥰90.206%
👌70.16%
3 further kinds90.206%

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 isTelegram’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 50 of the 50 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 4,722reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 50 most recent posts we hold, published 3 August 2026 to 15 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

15 Aug 2026, 09:50 UTC485 views25 reactionsread 15 August 2026
Photo

🔵⚙️⚪️ — 40 минут до начала встречи! Откуда будете болеть за «Торпедо»? ⚪️ Наш канал в МАХ

custom 5393415060376815010185🔥2

15 Aug 2026, 09:32 UTC830 views43 reactionsread 15 August 2026
Photo

⚡️ Стартовый состав на #ЧелябинскТорпедо! ⚪️ Наш канал в МАХ

custom 53934150603768150103012😭1

15 Aug 2026, 09:10 UTC972 views31 reactionsread 15 August 2026
Video

🔥 Всё внимание к матчу #ЧелябинскТорпедо — команда на стадионе! ⚪️ Наш канал в МАХ

custom 5393415060376815010256

15 Aug 2026, 08:13 UTC≈1,190 views28 reactionsread 15 August 2026
Photo

🤜🤛 Молодое противостояние #ЧелябинскТорпедо! Всего две встречи в рамках Первенства — вспоминаем их в инфографике и читаем превью. ⚪️ Наш канал в МАХ

custom 5393415060376815010226

15 Aug 2026, 07:15 UTC≈1,380 views103 reactionsread 15 August 2026
Photo

🥳 Евгению Храбростину — 75! Сегодня юбилей отмечает чемпион СССР (1976) и бронзовый призёр чемпионата СССР в составе «Торпедо». За чёрно-белых Евгений Борисович провёл 128 матчей и забил 31 мяч. Поздравляем с юбилеем, желаем крепкого здоровья, благополучия и новых приятных встреч с «Торпедо». Всегда рады видеть Вас на матчах нашего клуба! 🖤🤍 ⚪️ Наш канал в МАХ

👍37custom 539341506037681501032🏆12🎉108👏3🙏1

15 Aug 2026, 06:04 UTC≈1,550 views47 reactionsread 15 August 2026
Photo

⚡️ День матча! #ЧелябинскТорпедо 🏆 Лига PARI, 6 тур 🗓 Суббота, 15 августа ⏰ 13:30 мск | 15:30 местное 📍 Челябинск 🏟️ «Центральный» ✅ Судейская бригада 🖥 VK Видео 🖥 Кинопоиск 🖥 Матч ТВ 🎫 Билеты ⚪️ Наш канал в МАХ

👍24custom 539341506037681501015🔥42👌1🙏1

14 Aug 2026, 18:10 UTC≈2,090 views103 reactionsread 15 August 2026
Video

Александр Юшин — в списке кандидатов на лучший гол июля в Лиге PARI! 🔥 — Голосуем за Сашу по ссылке и ждём в строю! ⚪️ Наш канал в МАХ

🔥71👍207🎉5

14 Aug 2026, 16:26 UTC≈2,230 views84 reactionsread 15 August 2026
Photo

📰 Ровно 35 лет назад, 14 августа 1991 года, вышел первый номер «Спорт-Экспресса»! Желаем ещё много лет быть создателями главных спортивных историй 🤩 ⚪️ Наш канал в МАХ

42👍35👏5👎2

14 Aug 2026, 15:00 UTC≈2,530 views222 reactionsread 15 August 2026
Photo

⚡️ Мамаду Камара успешно прооперирован в Москве! Наш малийский полузащитник перенёс операцию по пластике разрыва акромиально-ключичного сочленения плечевого сустава в Юсуповской больнице Москвы. Восстановление игрока займёт 2.5 месяца 🙏 Мамаду, желаем успешной реабилитации и скорейшего возвращения на поле! ⚪️ ⚪️ Наш канал в МАХ

🙏129custom 53934150603768150106514😨6👌2👎2😭2💔1

14 Aug 2026, 13:56 UTC≈2,290 views77 reactionsread 15 August 2026
Photo

Чёрно-белые на месте! Отдыхаем и набираемся сил на #ЧелябинскТорпедо ✊ ⚪️ Наш канал в МАХ

custom 5393415060376815010559🔥8👍3🏆1👏1

14 Aug 2026, 09:16 UTC≈2,190 views88 reactionsread 14 August 2026
Video

🛫 Мы отправляемся в Челябинск — 6 тур Лиги PARI уже завтра! 🔥 — хорошего полёта, торпедовцы! ⚪️ Наш канал в МАХ

🔥37custom 539341506037681501033👍10🙏62

13 Aug 2026, 16:46 UTC≈2,480 views72 reactionsread 14 August 2026
Video

Одна фраза и совершенно разные эмоции! «Почему ты не отдал мне пас?» — версия Ильи и Алексея 😂 ⚪️ Наш канал в МАХ

🤣2419😁9custom 53934150603768150109👎6🤯5

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

@torpedomoscow_fc 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 August 2026
Most recent edit
9 August 2026

Citation-graph rank

Citation-graph rank — 11,222 of 1,481,217entries 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.

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 28 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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.

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.

ФК «Динамо» Москва
@fcdynamo · 122,496
Telegram ranks this channel #33 of 99 here — alongside 98 others — read 14 August 2026
ФК «Спартак-Москва»
@fcsmtg · 270,357
Telegram ranks this channel #44 of 93 here — alongside 92 others — read 10 August 2026
ФК «Краснодар»
@fckrasnodar · 111,809
Telegram ranks this channel #78 of 97 here — alongside 96 others — read 14 August 2026
ПФК ЦСКА
@pfccskamoscow · 178,193
Telegram ranks this channel #94 of 98 here — alongside 97 others — read 12 August 2026

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

Cross-platform identity — Wikidata

A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.

Q324338 on Wikidata, read 16 August 2026
LabelFC Torpedo Moscow
Descriptionassociation football club in Russia
YouTubeUCFxv6t60VC-9i8e-6ynCPZQ
Official sitehttp://www.fc-tm.ru

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

“ФК «Торпедо Москва»” (@torpedomoscow_fc), 14,376 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/torpedomoscow_fc.

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.