Channel
@telegfoot
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
4,952subscribers
-46 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001205163929 |
|---|---|
| Type | Channel |
| Username | @telegfoot |
| Created | 2 October 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/telegfoot |
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 13 September 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 the other topics.
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 in near-verbatim form 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 |
|---|---|---|---|
| @telegfoot/39496 · this entry7 Aug 2026, 21:26 UTC | @sportnexto/73068 Aug 2026, 11:04 UTC | 1.00 | 14 hours |
| @telegfoot/39521 · this entry8 Aug 2026, 20:20 UTC | @sportnexto/73109 Aug 2026, 15:45 UTC | 1.00 | 19 hours |
| @telegfoot/39568 · this entry11 Aug 2026, 11:23 UTC | @sportnexto/731712 Aug 2026, 08:15 UTC | 1.00 | 21 hours |
| @telegfoot/39571 · this entry11 Aug 2026, 15:59 UTC | @sportnexto/731912 Aug 2026, 14:17 UTC | 1.00 | 22 hours |
| @telegfoot/39499 · this entry8 Aug 2026, 08:30 UTC | @sportnexto/73079 Aug 2026, 08:34 UTC | 0.98 | 24 hours |
| @telegfoot/39474 · this entry6 Aug 2026, 20:25 UTC | @sportnexto/73027 Aug 2026, 13:12 UTC | 0.92 | 17 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @sportnexto | 6 (6/6 hand-verifiable sample passed) | 0.98 | 20 hours | this entry (6–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. 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 63 comparable posts for this entry, running 5 August 2026 to 11 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.
Recorded under the key clone_source, last confirmed 11 November 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 17:57 | 4,952 | +1 |
| 7 Nov 2026, 09:07 | 4,951 | -2 |
| 4 Nov 2026, 10:46 | 4,953 | -4 |
| 1 Nov 2026, 12:47 | 4,957 | +1 |
| 26 Oct 2026, 09:56 | 4,956 | -1 |
| 23 Oct 2026, 07:06 | 4,957 | +11 |
| 20 Oct 2026, 07:56 | 4,946 | +6 |
| 17 Oct 2026, 06:28 | 4,940 | -21 |
| 14 Oct 2026, 17:11 | 4,961 | -5 |
| 11 Oct 2026, 03:37 | 4,966 | -15 |
| 5 Oct 2026, 07:20 | 4,981 | -14 |
| 27 Sept 2026, 07:58 | 4,995 | -24 |
| 17 Sept 2026, 23:16 | 5,019 | -5 |
| 13 Sept 2026, 11:20 | 5,024 | -6 |
| 9 Sept 2026, 07:59 | 5,030 | -1 |
| 3 Sept 2026, 17:42 | 5,031 | +2 |
| 31 Aug 2026, 00:15 | 5,029 | -3 |
| 27 Aug 2026, 16:42 | 5,032 | +1 |
| 24 Aug 2026, 12:05 | 5,031 | +43 |
| 21 Aug 2026, 06:13 | 4,988 | first reading |
91 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 8 pages 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 91 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
2,083 reactions across 91 posts, in 28 distinct kinds. The most used accounts for 24.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤯 | 519 | 24.9% | |
| 👍 | 292 | 14.0% | |
| ❤ | 261 | 12.5% | |
| 🤡 | 225 | 10.8% | |
| 😁 | 211 | 10.1% | |
| 🤣 | 147 | 7.06% | |
| 🕊 | 123 | 5.90% | |
| 🔥 | 72 | 3.46% | |
| 💩 | 66 | 3.17% | |
| 👎 | 38 | 1.82% | |
| 😢 | 29 | 1.39% | |
| 🖕 | 28 | 1.34% | |
| 💔 | 21 | 1.01% | |
| 👏 | 9 | 0.432% | |
| ✍ | 8 | 0.384% | |
| 👌 | 5 | 0.24% | |
| 🥱 | 5 | 0.24% | |
| 🫡 | 4 | 0.192% | |
| 🏆 | 3 | 0.144% | |
| 🤝 | 3 | 0.144% | |
| 8 further kinds | 14 | 0.672% |
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 91 of the 91 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 2,083 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 91 most recent posts we hold, published 5 August 2026 to 11 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.
📞«Манчестер Сити» вышел на контакт с окружением Энцо Фернандеса — но судьба сделки зависит от оценки игрока со стороны «Челси». «Челси» запрашивает 120 млн фунтов и при этом был бы не против оставить футболиста в команде. «Сити», в свою очередь, надеется договориться о снижении цены. Источник: FabrizioRomano
😁5🖕1🤯1
🆓Мемфис Депай стал свободным агентом - «Коринтианс» расторгли с ним контракт. 32-летний голландский форвард может бесплатно перейти в новый клуб.
🤣10🤯10🖕1🥱1
🤣Брэд Питт пообещал научить Неймара лучше падать и правдоподобнее симулировать травмы: «Я собираюсь провести уроки по симуляции фолов — эти ребята в этом совершенно не разбираются. И начну я с Неймара. Хоть он и двигается на поле как артист балета, ему нужна помощь. Я покажу ему, как „продавать“ эпизод, как делать это тонко — и как не переборщить, чтобы всё выглядело реалистично. У меня есть полноценная программа тр…
😁10🤯2
🐓«Тоттенхэм» активно ведёт работу над трансфером Фоларина Балогуна. Лондонский клуб начал переговоры с «Монако» о возможном переходе американского нападающего — сумма сделки может составить 60 млн евро. Источник: lequipe
😁16👎4❤2🤯2👍1
Ура! Роналду и Джорджина поженились.
❤19🤯5👍1
⚡️«Монако» хочет распрощаться с Погба до 1 сентября. 🇫🇷 «Монако» предложил Полю Погба взаимное расторжение контракта — клуб хочет освободить место и дать игроку шанс найти новую команду уже в этом сезоне. Дедлайн — 1 сентября. ⚽️ Но финальное слово — за самим Полем. И тут важный нюанс: сейчас француз травмирован, так что решение придётся принимать с учётом состояния здоровья. Источники: Le Parisien
❤6👍1🤯1
💰«Барселона» готова предложить 65 млн евро плюс 5 млн евро в виде бонусов за Родри. Руководство «Барсы» хочет завершить сделку как можно скорее. Источник: diarioas
❤6🤯5💩3👍1
😔🇫🇷 Поль Погба снова получил травму на тренировке «Монако». Француз вскрикнул от боли, а затем рухнул на землю во время занятия. Ему пришлось покинуть поле — его унесли два сотрудника клуба.
🤯14🤨1
❌🇧🇷 Окружение Винисиуса Жуниора 🚫 отклонило предложение «Арсенала» — из‑за привязанности игрока к «Реал Мадриду» и финансовых обязательств клуба. При этом окружение футболиста выразило благодарность «Арсеналу» за отношение к игроку. Источник: TheAthletic
🤡25🤯8❤3👌1
😳🇦🇷 В раздевалке «Атлетико Мадрид» ждут извинений от Хулиана Альвареса. Товарищи по команде считают, что его недавние высказывания о желании перейти в «Барселону» усугубили ситуацию. Игроки полагают, что Альварес должен признать свою ошибку и извиниться перед болельщиками «Атлетико», прежде чем пытаться вновь завоевать их доверие на поле. Источник: La SER
🤯11🤣9👍7
❤️🩹 Лионелю Месси разрешили остаться в Аргентине с близкими на неопределённый срок. Аргентинец хочет быть рядом со своей семьёй в этот трудный период после смерти своего отца.
❤15🕊13💔7
👀«Арсенал» заинтересован в Жюле Кунде. «Канониры» особенно ценят его универсальность и способность играть как на позиции центрального, так и правого защитника. «Барселона» готова рассмотреть предложения по французскому защитнику. Источник: Diario
👍11🤯7🥴3👎1
Showing the 12 most recent of 91 posts we hold for @telegfoot. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 17 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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“ФУФА” (@telegfoot), 4,952 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/telegfoot.
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.