✅Наши чистые расходы (разница между купленными и проданными) в сравнении с другими клубами АПЛ по итогам ЛТО.
👎27👍7❤4❤🔥1

Channel
@redsmu
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Polls · Citations · Telegram's recommendations · Cite this entry
18,840subscribers
+217 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001825265825 |
|---|---|
| Type | Channel |
| Username | @redsmu |
| Created | 21 November 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 30 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/redsmu |
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 10 August 2026 and assigned it the closest of 31 fixed categories, at 99% 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.
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.
Posts published here appear word for word on 1 other registered channel. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @DevilsInDetails/186615 Aug 2026, 09:35 UTC | @redsmu/45999 · this entry5 Aug 2026, 09:36 UTC | 1.00 | 72 seconds |
| @DevilsInDetails/186926 Aug 2026, 21:04 UTC | @redsmu/46019 · this entry7 Aug 2026, 07:40 UTC | 1.00 | 11 hours |
| @DevilsInDetails/187047 Aug 2026, 18:39 UTC | @redsmu/46035 · this entry7 Aug 2026, 21:50 UTC | 1.00 | 3.2 hours |
| @DevilsInDetails/186806 Aug 2026, 09:00 UTC | @redsmu/46015 · this entry6 Aug 2026, 10:05 UTC | 0.97 | 65 minutes |
| @DevilsInDetails/186725 Aug 2026, 17:04 UTC | @redsmu/46012 · this entry5 Aug 2026, 20:04 UTC | 0.89 | 3.0 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @DevilsInDetails | 5 (5/5 hand-verifiable sample passed) | 0.97 | 3.0 hours | @DevilsInDetails (5–0) |
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. 3 of the 5 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 16 comparable posts for this entry, running 5 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.
Across the whole group of 2, the earliest publisher we hold is @DevilsInDetails. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, 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.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 09:38 | 18,840 | -7 |
| 15 Sept 2026, 08:15 | 18,847 | +68 |
| 13 Sept 2026, 17:37 | 18,779 | -24 |
| 11 Sept 2026, 20:19 | 18,803 | +116 |
| 9 Sept 2026, 10:56 | 18,687 | -14 |
| 6 Sept 2026, 04:42 | 18,701 | -11 |
| 2 Sept 2026, 14:47 | 18,712 | -8 |
| 1 Sept 2026, 17:53 | 18,720 | +2 |
| 31 Aug 2026, 21:15 | 18,718 | +2 |
| 30 Aug 2026, 23:53 | 18,716 | -5 |
| 29 Aug 2026, 21:27 | 18,721 | -8 |
| 28 Aug 2026, 23:35 | 18,729 | +4 |
| 27 Aug 2026, 22:38 | 18,725 | +5 |
| 27 Aug 2026, 02:04 | 18,720 | -10 |
| 25 Aug 2026, 22:53 | 18,730 | -6 |
| 24 Aug 2026, 23:34 | 18,736 | -13 |
| 23 Aug 2026, 07:04 | 18,749 | -5 |
| 20 Aug 2026, 11:52 | 18,754 | -3 |
| 19 Aug 2026, 10:28 | 18,757 | -4 |
| 18 Aug 2026, 09:22 | 18,761 | first reading |
480 posts held, back to 4 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 58 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 2 September 2026 |
|---|---|
| Posts held | 480 (4 August 2026 – 2 September 2026) |
| Views total | 1,226,448 |
| Reactions total | 31,184 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 02:19 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.
Measured directly from 4 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.
55,623 reactions across 479 posts, in 66 distinct kinds. The most used accounts for 43.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 24,159 | 43.4% | |
| custom 5449505950283078474 | 7,430 | 13.4% | |
| ❤🔥 | 3,549 | 6.38% | |
| 👍 | 3,186 | 5.73% | |
| 🤡 | 1,904 | 3.42% | |
| 😁 | 1,529 | 2.75% | |
| 🤝 | 1,288 | 2.32% | |
| 🤣 | 1,263 | 2.27% | |
| 👎 | 1,188 | 2.14% | |
| custom 5348533962098621677 | 861 | 1.55% | |
| 🔥 | 839 | 1.51% | |
| custom 5463149880266482597 | 749 | 1.35% | |
| 💩 | 731 | 1.31% | |
| custom 5418126902038649459 | 672 | 1.21% | |
| custom 5363911285048089157 | 622 | 1.12% | |
| 😢 | 594 | 1.07% | |
| custom 5350354826368663271 | 376 | 0.676% | |
| 🤔 | 352 | 0.633% | |
| 👀 | 342 | 0.615% | |
| 🤯 | 304 | 0.547% | |
| 46 further kinds | 3,685 | 6.62% |
Custom emoji. 6 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 479 of the 480 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 55,623 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 480 most recent posts we hold, published 4 August 2026 to 2 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 @redsmu. 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 480 most recent posts we hold for this entry, published 4 August 2026 to 2 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 |
|---|---|---|---|
| 2W5zFG1Z7N9 | 1 | 12 August 2026 | 12 August 2026 |
| 2W5zFHZ7JtZ | 1 | 26 August 2026 | 26 August 2026 |
| 2W5zFHm1tAD | 1 | 6 August 2026 | 6 August 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 480 most recent posts we hold, published 4 August 2026 to 2 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.
✅Наши чистые расходы (разница между купленными и проданными) в сравнении с другими клубами АПЛ по итогам ЛТО.
👎27👍7❤4❤🔥1
✅Глубина состава «Манчестер Юнайтед» на этот сезон.
🤣152😁16custom 536391128504808915714custom 54181269020386494598❤6custom 53485339620986216775💅4💩3
✅Чидо Оби ушел в аренду в «Виллем II». Аренда на сезон.
❤77👍21custom 53485339620986216773❤🔥1🤪1
В OFFSIDE POINT только что вышел интересный пост о том, что вообще происходит с «Манчестер Юнайтед» последние годы. Клуб тратит сотни миллионов, меняет тренеров и игроков, а нормального результата всё нет. 👉 Залетай, читай и пиши в комментариях, в чём, по-твоему, главная проблема МЮ. И раз уж ты здесь — познакомься с самим каналом. OFFSIDE POINT — новый футбольный проект, который мы делаем без привычного мусора в…
custom 535035482636866327116❤7🔥3👎1💩1😁1
Игрок месяца:
The shares total 107%, 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.
😁20👍6custom 53485339620986216772❤🔥1
✅Претенденты на звание игрока месяца в клубе за август: • Бруну Фернандеш • Кобби Майну • Маркус Рэшфорд
custom 544950595028307847473❤12🤔6❤🔥1
✅Бруну в символической сборной второго тура АПЛ по результатам голосования фанатов.
❤53❤🔥1
✅Самые дорогие трансферы в истории Премьер-лиги.
❤51👎7❤🔥1
✅Символическая сборная месяца топ-5 лиг Европы по итогам августа по версии SofaScore.
❤74custom 53639112850480891572❤🔥1
✅ Бруну Фернандеш – лучший игрок второго тура в АПЛ.
❤280❤🔥35👍15🔥5🤡2🫡2🖕1custom 54495059502830784741
✅В этом сезоне дебютанты Лиги чемпионов выйдут на поле с дебютным патчем на рукаве. Это часть нового шестилетнего контракта УЕФА с Fanatics. Затем этот патч вставят в коллекционную карточку Topps с автографом игрока. В НБА всё работает так же, на следующей неделе такую карточку там планируют пустить с молотка примерно за $5 млн. [Дэвид Орнстайн, The Athletic]
❤44👍7🤝3❤🔥1
✅Сколько клубы АПЛ потратили этим летом.
👎53❤5❤🔥1
Showing the 12 most recent of 480 posts we hold for @redsmu. 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.
The 3 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 107%, 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.
Оцените трансферное окно по 10 бальной шкале:
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Место «МЮ» на общем этапе:
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 480 most recent posts we hold, published 4 August 2026 to 2 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.
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 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.
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.
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 6 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Манчестер Юнайтед” (@redsmu), 18,840 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/redsmu.
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.