🇭🇺✅ Dominik Szoboszlai est apte et disponible pour le match de la Hongrie contre la Géorgie en Ligue des Nations, confirme le sélectionneur Marco Rossi.
❤15🥰3💔2
Signed BLV03♾️🇸🇳🇵🇸

Channel
@LiverpoolFra
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry
18,444subscribers
-214 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001689662789 |
|---|---|
| Type | Channel |
| Username | @LiverpoolFra |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 62 |
| Confirmed unchanged | 1 time, most recently 14 November 2026 |
| On Telegram | t.me/LiverpoolFra |
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 10 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 8 other registered channels. This entry also sits inside a group of 58 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @PremierLeaguefra/3989818 Aug 2026, 18:18 UTC | @LiverpoolFra/26201 · this entry18 Aug 2026, 19:39 UTC | 1.00 | 81 minutes |
| @LiverpoolFra/26215 · this entry19 Aug 2026, 15:14 UTC | @PremierLeaguefra/3995719 Aug 2026, 15:14 UTC | 1.00 | under a minute |
| @LiverpoolFra/26239 · this entry20 Aug 2026, 18:25 UTC | @PremierLeaguefra/4004320 Aug 2026, 18:27 UTC | 1.00 | 2 minutes |
| @PremierLeaguefra/4085729 Aug 2026, 08:21 UTC | @LiverpoolFra/26485 · this entry29 Aug 2026, 08:47 UTC | 1.00 | 26 minutes |
| @LiverpoolFra/28970 · this entry3 Nov 2026, 10:49 UTC | @PremierLeaguefra/443673 Nov 2026, 10:49 UTC | 1.00 | under a minute |
| @PremierLeaguefra/444555 Nov 2026, 09:26 UTC | @LiverpoolFra/29047 · this entry5 Nov 2026, 09:27 UTC | 1.00 | 72 seconds |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @PremierLeaguefra | 32 (8/8 hand-verifiable sample passed) | 1.00 | 72 seconds | this entry (22–10) |
| @PLFRANCE | 19 (8/8 hand-verifiable sample passed) | 1.00 | 2.4 hours | this entry (15–4) |
| @PremierLeague_fr | 11 (8/8 hand-verifiable sample passed) | 1.00 | 2.1 hours | this entry (10–1) |
| @ParisSGFr | 9 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (6–3) |
| @Canal_foot | 9 (8/8 hand-verifiable sample passed) | 1.00 | 1.9 hours | this entry (7–2) |
| @liverpool225 | 8 (8/8 hand-verifiable sample passed) | 1.00 | 48 minutes | this entry (8–0) |
| @liverpoolfanclub | 6 (6/6 hand-verifiable sample passed) | 1.00 | 43 minutes | this entry (6–0) |
| @Actufoot_Archive | 6 (6/6 hand-verifiable sample passed) | 1.00 | 5 minutes | @Actufoot_Archive (4–2) |
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. 24 of the 24 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 514 comparable posts for this entry, running 6 August 2026 to 13 November 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.
Of the group of 58 channels, the one whose matching posts we hold earliest is @Beautyinblacksaison3_vf. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_source, last confirmed 14 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.
This channel is in a group of 58 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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.
7 more channels are in this same group but not listed individually here.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Nov 2026, 06:56 | 18,444 | -24 |
| 11 Nov 2026, 12:00 | 18,468 | -14 |
| 9 Nov 2026, 19:28 | 18,482 | -22 |
| 8 Nov 2026, 14:40 | 18,504 | -5 |
| 7 Nov 2026, 08:46 | 18,509 | -8 |
| 6 Nov 2026, 06:49 | 18,517 | -9 |
| 5 Nov 2026, 03:16 | 18,526 | -8 |
| 3 Nov 2026, 23:42 | 18,534 | -9 |
| 2 Nov 2026, 20:46 | 18,543 | -27 |
| 1 Nov 2026, 17:41 | 18,570 | -12 |
| 31 Oct 2026, 14:46 | 18,582 | -33 |
| 30 Oct 2026, 11:50 | 18,615 | -20 |
| 29 Oct 2026, 11:36 | 18,635 | -23 |
| 28 Oct 2026, 11:16 | 18,658 | -20 |
| 27 Oct 2026, 12:51 | 18,678 | -14 |
| 26 Oct 2026, 11:36 | 18,692 | +8 |
| 25 Oct 2026, 11:44 | 18,684 | -9 |
| 24 Oct 2026, 13:29 | 18,693 | -21 |
| 23 Oct 2026, 16:45 | 18,714 | -29 |
| 22 Oct 2026, 13:17 | 18,743 | first reading |
732 posts held, back to 6 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 76 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. It is computed over the 238 of 239 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 13 November 2026 |
|---|---|
| Posts held | 732 (6 August 2026 – 13 November 2026) |
| Views total | 124,822 |
| Reactions total | 4,048 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Nov 2026, 04:55 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.
18,800 reactions across 728 posts, in 18 distinct kinds. The most used accounts for 86.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 16,202 | 86.2% | |
| 👍 | 909 | 4.84% | |
| 🔥 | 420 | 2.23% | |
| 💔 | 333 | 1.77% | |
| 🥰 | 197 | 1.05% | |
| 👏 | 175 | 0.931% | |
| 🤣 | 138 | 0.734% | |
| 😭 | 95 | 0.505% | |
| 😢 | 92 | 0.489% | |
| 😱 | 73 | 0.388% | |
| 😁 | 46 | 0.245% | |
| 🤯 | 43 | 0.229% | |
| 🎉 | 28 | 0.149% | |
| 😘 | 26 | 0.138% | |
| 🫡 | 11 | 0.059% | |
| 🙏 | 6 | 0.032% | |
| 👌 | 3 | 0.016% | |
| 🤩 | 3 | 0.016% |
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 729 of the 732 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 18,800 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 732 most recent posts we hold, published 6 August 2026 to 13 November 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 @LiverpoolFra. 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 732 most recent posts we hold for this entry, published 6 August 2026 to 13 November 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.
Telegram’s own ‘edited’ marker: 3 of 239 posts held from the last 30 days (1.26%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🇭🇺✅ Dominik Szoboszlai est apte et disponible pour le match de la Hongrie contre la Géorgie en Ligue des Nations, confirme le sélectionneur Marco Rossi.
❤15🥰3💔2
Signed BLV03♾️🇸🇳🇵🇸
🥇 | JamesPearceLFC pour TheRedmenTV : « Ce qui va se passer avec Lamine Camara sera intéressant. » « Je ne serais pas surpris qu'un scénario similaire à celui de la signature de Luis Díaz par Liverpool en janvier 2022 se produise : le club pourrait décider de recruter dès janvier un joueur qui figurait initialement sur sa liste pour l'été. »
❤11
Signed BLV03♾️🇸🇳🇵🇸
🏴 Trey Nyoni est sur le banc pour l'Angleterre U21 contre le Portugal.
❤12🤯6
Signed Taphar68
🚨🇳🇱 Cody Gakpo est titulaire avec les Pays-Bas face à la Grèce !
❤19
Signed BLV03♾️🇸🇳🇵🇸
🇩🇪👀 Florian Wirtz sera titulaire dans la composition attendue de l'Allemagne selon BILD pour affronter la Serbie.
❤20
Signed Taphar68
🚨🇳🇱 INFO : En l’état actuel des choses, ce serait assez surprenant que Virgil van Dijk quitte Liverpool cet été, malgré l’intérêt de plusieurs clubs à travers l’Europe, rapporte aadamp9.
👍10❤4
Signed BLV03♾️🇸🇳🇵🇸
🚨 Liverpool est très peu susceptible de dépenser une grosse somme pour recruter un défenseur central en janvier ou lors du prochain mercato estival, ce poste n’étant pas considéré comme une priorité. Jérémy Jacquet a fait une très forte impression, tandis que le club fonde de grands espoirs sur ses jeunes défenseurs Giovanni Leoni, Ifeanyi Ndukwe et Mor Talla Ndiaye. 🗞️ JamesPearceLFC
❤22
Signed BLV03♾️🇸🇳🇵🇸
Rio Ngumoha sur ce que Mohamed Salah lui a enseigné : « Il y a eu un moment dont je me souviens. Il disait simplement, il sait évidemment que je suis talentueux, mais pour atteindre le tout haut niveau, dans les 20 dernières minutes du match, il faut juste rester en vie, être devant tout le monde, être plus rapide que tout le monde, et c'est là que tu marques le plus de buts vraiment, quand tous les défenseurs sont …
❤12
Signed Taphar68
On a déjà vu celle-là auparavant 😉 Célébration glaciale, spidadmitchell 🥶
❤27
Signed BLV03♾️🇸🇳🇵🇸
💬 - Alexander Isak : « C'est rare qu'ils [donnent un penalty] si tu restes debout. Une telle situation est un peu plus évidente que d'autres, il devrait y avoir une sanction quand même. Ça avait un goût amer. Tu te demandes ce que tu aurais pu faire différemment. Devrais-tu avoir à le faire ? Non. »
❤10
Signed Taphar68
🚨✅ 𝗡𝗘𝗪 - DaleJohnsonBBC: Liverpool aurait dû se voir accorder un penalty contre Arsenal après qu’Alexander Isak a été retenu par Jurrien Timber, a statué le Panel des Incidents Clés des Matchs de la Premier League. Le Panel KMI a voté 4:1 en faveur de l’attribution du penalty sur le terrain, avec un vote 3:2 indiquant que le VAR aurait dû intervenir et envoyer l’arbitre au moniteur situé en bord de terrain.
❤14
Signed Taphar68
💬 - Rio Ngumoha sur l'accent mis par Andoni Iraola sur la polyvalence des ailiers : « Évidemment, je n'ai pas encore maîtrisé quoi que ce soit, bien sûr. J'apprends encore. Je pense que savoir que le manager peut dire : "On peut jouer Rio à gauche aujourd'hui" ou "On pourrait jouer Rio à droite" ou que je sois sur le banc et "On peut faire entrer Rio à gauche et à droite", je trouve simplement que c'est un ensemble …
❤12
Signed Taphar68
Showing the 12 most recent of 732 posts we hold for @LiverpoolFra. 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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 5 October 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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 27 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 14 November 2026 — this entry's latest reading, not the date you are reading this.
“LIVERPOOL FC ™️🔴” (@LiverpoolFra), 18,444 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/LiverpoolFra.
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.