Telegram RegisterThe public register of Telegram

Channel

Все о Торпедо

@TorpedoRu

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

1,590subscribers

+7 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-1002413047352
TypeChannel
Username@TorpedoRu
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/TorpedoRu

Topic

Sports — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. They sit inside a group of 3 channels that share the same post bodies with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@ilyev_serg/42854 Aug 2026, 17:38 UTC@TorpedoRu/5501 · this entry4 Aug 2026, 18:10 UTC1.0032 minutes
@ilyev_serg/42875 Aug 2026, 08:06 UTC@TorpedoRu/5503 · this entry5 Aug 2026, 08:11 UTC1.005 minutes
@ilyev_serg/42905 Aug 2026, 15:07 UTC@TorpedoRu/5506 · this entry5 Aug 2026, 15:13 UTC1.007 minutes
@ilyev_serg/42956 Aug 2026, 10:17 UTC@TorpedoRu/5508 · this entry6 Aug 2026, 10:21 UTC1.004 minutes
@ilyev_serg/42976 Aug 2026, 15:50 UTC@TorpedoRu/5511 · this entry6 Aug 2026, 16:06 UTC1.0016 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@ilyev_serg5 (5/5 hand-verifiable sample passed)1.007 minutes@ilyev_serg (50)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 17 comparable posts for this entry, running 4 August 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 3, the earliest publisher we hold is @ilyevserg. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 8 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

1,5831,5901,586.57 August 2026 — 1,583 subscribers7 August 2026 — 1,583 subscribers7 August 2026 — 1,584 subscribers11 August 2026 — 1,590 subscribers7 August 202611 August 2026
4 measurements spanning 4 days, net +7. 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,582–1,591 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 04:321,590+6
7 Aug 2026, 23:171,584+1
7 Aug 2026, 21:181,583no change
7 Aug 2026, 14:481,583first reading

Engagement

20 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
37.2%
avg views ÷ 1,590 subscribers
Avg views / post
591
20 posts measured
Reaction rate
9.06%
reactions ÷ views · ER floor
Posts in window
20
of 20 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 7 August 2026
Posts held20 (3 August 20267 August 2026)
Views total11,825
Reactions total1,071
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 21:18 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

Video runtime
18s
Average length
18s

Measured directly from 1 video 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

1,071 reactions across 20 posts, in 18 distinct kinds. The most used accounts for 42.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 534577328596976826245742.7%
👍21820.4%
🔥1069.90%
👎555.14%
524.86%
🤔474.39%
🤬434.01%
🤣353.27%
💯211.96%
😱90.84%
🍾80.747%
🫡80.747%
👏40.373%
🤨30.28%
👀20.187%
👌10.093%
😡10.093%
😭10.093%

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 20 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 1,071reactions 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 3 August 2026 to 7 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

7 Aug 2026, 12:50 UTC438 views47 reactionsread 7 August 2026
Forwarded from @rfntelegaPhoto

«Торпедо» перед последним матчем сезона в Волгограде. Верхний ряд (слева направо): Валерий Петраков📢, Арсен Аваков🇷🇺🇹🇯, Валерий Воробьёв🧤🇺🇦, Сергей Скаченко🇺🇦, Виктор Булатов🇷🇺, Артур Мкртчян🇦🇲, Сергей Бурченков🇷🇺, Валентин Иванов📢 Нижний ряд: Андрей Гашкин🇷🇺, Игорь Семшов🇷🇺, Дмитрий Градиленко🇷🇺, Андрей Малай🇷🇺, Вадим Евсеев🇷🇺. #торпедо #торпедомосква #рпл

custom 534577328596976826230👍8🔥63

7 Aug 2026, 12:11 UTC478 views56 reactionsread 7 August 2026
Forwarded from @fnlru

Президент ФНЛ Измайлов прокомментировал решение о переносе матча «Торпедо» — «Сочи» Президент Футбольной национальной лиги Наиль Измайлов прокомментировал решение о переносе матча 5-го тура второго по силе российского дивизиона между «Торпедо» и «Сочи». «Решение о переносе матча 5-го тура Лиги PARI «Торпедо Москва» — «Сочи» принято на основании регламентных норм и представленных клубом материалов. ФК «Сочи» своевр

🤣34custom 534577328596976826211🤔8🤬3

7 Aug 2026, 11:10 UTC521 views34 reactionsread 7 August 2026
Forwarded from @speckorr

В Торпедовских пабликах обсуждают перенос матча с Сочи. Простите, но у меня доза «этодругина» Дисклеймер: это только мое мнение. Мое не равно правильное. Просто высказываюсь, потому что не делать этого неправильно. Сразу скажу: мне не нравится технические поражения. Если бы решения принимал только я, то ни Уфе, ни Сочи я бы технари не выписывал. Но. Ситуация Сочи для меня отличается от прецедента прошлого сезона Л

custom 534577328596976826217🤔9👍6🤬2

7 Aug 2026, 09:17 UTC599 views55 reactionsread 7 August 2026
Photo

🏆 Черно-белые Исправили этот недочет. 👑 «Торпедо» (Россия) 1. «Ювентус» (Италия) 2. «Сантос» (Бразилия) 3. «Ньюкасл Юнайтед» (Англия) 4. «Ботафого» (Бразилия) 5. «Атлетико Минейро» (Бразилия) 6. «Бешикташ» (Турция) 7. ПАОК (Греция) 8. «Удинезе» (Италия) 9. «Либертад» (Парагвай) 10. «Партизани» Тирана (Албания) 11. «Монтевидео Уондерерс» (Уругвай) 12. «Ноттс Каунти» (Англия) 13. «Серкль Шарлеруа» / «Шарлеруа» (Бельг

custom 534577328596976826227👍148🔥3🫡2🍾1

7 Aug 2026, 06:17 UTC573 views51 reactionsread 7 August 2026
Forwarded from @Anario_13Photo

⚡️Чупаев уходит из Торпедо: по моей информации, форвард разорвет контракт с клубом Лиги PARI по обоюдному согласию. Сергей в июне писал, что 21-летний экс-игрок Динамо покинет Восточную. В прошлом сезоне Торпедо отправлял Сашу в аренду в Спартак из Костромы. 🔥С тебя комментарий, лайк и подписка!

👍23custom 534577328596976826215🫡63🤨3🤔1

6 Aug 2026, 17:33 UTC595 views66 reactionsread 7 August 2026
Forwarded from @badradioTM

Ну что, ФНЛ и Наиль Измайлов лично учат значение слова - дискредитация. Этим решением обнулëн технарь «Уфы» (а за что им техническое поражение выписали, м? Ни за что, получается) и в очередной раз опрокинут авторитет Лиги, если он был. Причем ещё и на фоне «понятийного авторитета» конкретного клуба. Случись ситуация в обратном направлении, игру в интересах «Торпедо» перенесли бы? Ответ совершенно очевиден.

👍31💯21custom 534577328596976826213😡1

6 Aug 2026, 17:22 UTC477 views47 reactionsread 7 August 2026
Forwarded from @ilyevserg

⚡️ По последним данным, матч "Торпедо" - "Сочи" перенесен на субботу на 18:00.

👎23🤬14custom 534577328596976826291

6 Aug 2026, 16:06 UTC480 views37 reactionsread 7 August 2026
Forwarded from @ilyevserg

Матч "Торпедо" - "Сочи" в назначенное время вряд ли состоится По моим данным, "Сочи" полетит в Москву завтра двумя группами. Одна - из Сухума, вторая - из Краснодара (нашли небольшую порцию билетов). Основная масса футболистов, если опять же все будет по графику, прибудет в столицу в 18:30. А матч в Химках с "Торпедо" назначен на 20:00, причем он телевизионный. Как выходить из этой ситуации - решения пока нет. Все

🤬22custom 53457732859697682629👎42

6 Aug 2026, 15:39 UTC563 views45 reactionsread 7 August 2026
Forwarded from @fnlru

«Сочи» попросил о переносе матча против «Торпедо» из-за проблем с вылетом в Москву Генеральный директор «Сочи» Сергей Новиков сообщил, что клуб попросил перенести матч 5-го тура Лиги PARI против «Торпедо» на 8 августа из-за проблем с вылетом команды. Матч «Торпедо» — «Сочи» должен пройти в пятницу, 7 августа, на стадионе «Арена Химки» (начало — в 20:00 мск). В четверг стало известно, что «Сочи» не смог вылететь в

👎21custom 534577328596976826210😱93👀2

6 Aug 2026, 10:55 UTC673 views37 reactionsread 7 August 2026
Forwarded from @nezfootPhoto

✈️ «Сочи» может не успеть на матч с «Торпедо» У сочинцев возникли проблемы с вылетом в Москву на матч пятого тура Лиги PARI. Главный тренер команды Игорь Осинькин сообщил, что клуб рассматривает все возможные способы добраться до столицы, но конкретного решения пока нет. Матч с «Торпедо» должен пройти завтра, 7 августа, на «Арене Химки». Начало в 20:00 по московскому времени. — Есть угроза, что не успеете к матчу?

👍13custom 534577328596976826212🤔11😭1

6 Aug 2026, 10:21 UTC544 views42 reactionsread 7 August 2026
Forwarded from @ilyevsergPhoto

🛩 "Сочи" не может вылететь в Москву Сочинцы, у которых завтра вечером игра в Химках с "Торпедо", не могут вылететь в столицу. Рейс в 13 часов, которым должны были добираться "барсы", отменили. Небо закрыли из-за атак БПЛА. А на более поздние рейсы билетов нет. Как нет их из Краснодара и МинВод. В клубе прорабатывают варианты, что делать.

👍15custom 534577328596976826212🤔10🔥32

6 Aug 2026, 06:11 UTC671 views119 reactionsread 7 August 2026
Forwarded from @fcmashukPhoto

«Торпедо» — рядом! ❤️🤍 В трудные моменты особенно ценится поддержка тех, кто не остается в стороне. Узнав о сложной ситуации, с которой столкнулся футбольный клуб «Машук-КМВ», игроки московского «Торпедо» единогласно приняли решение оказать нашей команде финансовую помощь. Мы искренне благодарим футболистов «Торпедо» за этот благородный поступок, поддержку и настоящее футбольное единство. Такие действия еще раз до

custom 534577328596976826278👍2115👏4🔥1

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

Citation-graph rank

Citation-graph rank — 918,136 of 1,151,006entries 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 2 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.

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

“Все о Торпедо” (@TorpedoRu), 1,590 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/TorpedoRu.

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.