Channel
@liverpool_f
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
1,782subscribers
-31 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001266825036 |
|---|---|
| Type | Channel |
| Username | @liverpool_f |
| Created | 14 June 2018 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/liverpool_f |
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 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 3 other registered channels. 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 |
|---|---|---|---|
| @rfliverpool/2739331 Jul 2026, 12:40 UTC | @liverpool_f/9993 · this entry31 Jul 2026, 14:33 UTC | 1.00 | 1.9 hours |
| @rfliverpool/2739431 Jul 2026, 18:36 UTC | @liverpool_f/9994 · this entry1 Aug 2026, 05:53 UTC | 1.00 | 11 hours |
| @rfliverpool/273961 Aug 2026, 13:03 UTC | @liverpool_f/9997 · this entry2 Aug 2026, 06:08 UTC | 1.00 | 17 hours |
| @rfliverpool/273971 Aug 2026, 16:27 UTC | @liverpool_f/9998 · this entry2 Aug 2026, 06:08 UTC | 1.00 | 14 hours |
| @rfliverpool/274054 Aug 2026, 12:01 UTC | @liverpool_f/10006 · this entry4 Aug 2026, 14:41 UTC | 1.00 | 2.7 hours |
| @rfliverpool/274126 Aug 2026, 10:41 UTC | @liverpool_f/10010 · this entry6 Aug 2026, 16:24 UTC | 1.00 | 5.7 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @rfliverpool | 8 (8/8 hand-verifiable sample passed) | 1.00 | 8.2 hours | @rfliverpool (8–0) |
| @Liverpoolc | 7 (7/7 hand-verifiable sample passed) | 1.00 | 2.0 hours | @Liverpoolc (4–3) |
| @Liverpulz | 5 (5/5 hand-verifiable sample passed) | 1.00 | 2.0 hours | this entry (4–1) |
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. 5 of the 13 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 17 comparable posts for this entry, running 30 July 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 4, the earliest publisher we hold is @rfliverpool. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_mutual · clone_source, 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 3 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 04:38 | 1,782 | -1 |
| 11 Sept 2026, 12:55 | 1,783 | -1 |
| 6 Sept 2026, 16:57 | 1,784 | +1 |
| 1 Sept 2026, 20:25 | 1,783 | -1 |
| 29 Aug 2026, 15:56 | 1,784 | -4 |
| 27 Aug 2026, 00:24 | 1,788 | -6 |
| 24 Aug 2026, 01:55 | 1,794 | -3 |
| 20 Aug 2026, 13:52 | 1,797 | -1 |
| 17 Aug 2026, 10:58 | 1,798 | -7 |
| 13 Aug 2026, 10:35 | 1,805 | -1 |
| 10 Aug 2026, 00:29 | 1,806 | -7 |
| 6 Aug 2026, 09:33 | 1,813 | no change |
| 6 Aug 2026, 09:28 | 1,813 | first reading |
23 posts held, back to 30 July 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 2 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 23 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
«Ливерпуль» рассматривает варианты усиления на позиции правого защитника, центрального защитника и центрального полузащитника. По моему мнению, «Ливерпуль» будет очень активен на трансферном рынке до закрытия летнего окна — Бен Джейкобс
«Ливерпуль» рассматривает возможность приобретения 24-летнего нападающего «Ньюкасла» и сборной Германии Ника Вольтемаде этим летом. Руководство клуба активно анализирует варианты усиления атаки и видит огромный потенциал в немецком форварде — CaughtOffside
«Ливерпуль» проявляет интерес к защитнику «Тоттенхэма» Джеду Спенсу. Спенс крайне положительно относится к возможному переходу в «Ливерпуль». У Андони Ираолы есть опасения по поводу нынешних правых защитников команды. Спенс — не единственный кандидат, которого рассматривает клуб, поэтому пока неясно, получит ли эта сделка развитие. Однако интерес со стороны «Ливерпуля» действительно существует, даже несмотря на поп…
✔️ОФИЦИАЛЬНО:«Ливерпуль» представил трансфер Виктора Муньоса из «Осасуны» за 34,5 миллиона фунтов стерлингов.
🚨 Фабрицио Романо: «Ливерпуль» связался с новым агентом Ибрагимы Мбайе Жорже Мендешем. У Мбайе также есть предложения от клубов Бундеслиги, однако полузащитник отдаёт приоритет проекту «Ливерпуля». Сделка с «Лейпцигом» была близка к завершению, но сорвалась после того, как трансфер Диоманде в «ПСЖ» не состоялся.
📶Фабрицио Романо: «Байер» сделал предложение ПСЖ по Мбайе, и между клубами шли переговоры, но сейчас для вингера предложение «Ливерпуля» является приоритетным. Ранее Мбайе был близок к переходу в «Лейпциг», но после срыва трансфера Диоманде в ПСЖ переговоры завершились.
«Ливерпуль» планирует активизироваться на трансферном рынке и потратить около 320 млн евро на четырёх игроков. Главной целью «красных» является вингер ПСЖ Брэдли Баркола. Французский клуб оценивает 23-летнего игрока в 188 млн евро, но «Ливерпуль» рассчитывает договориться о сумме в 161 млн. Баркола заинтересован в переходе и хочет играть ключевую роль в проекте Андони Ираолы. Также «Ливерпуль» нацелен на защитника «…
😮💨
Прямые переговоры о трансфере Барколя между «Ливерпулем» и ПСЖ стартовали вчера. «Ливерпуль» изъявил готовность заплатить более 100 миллионов евро за игрока, что далеко от стартовых запросов ПСЖ, но диалог начался. Барколя хочет перейти в «Ливерпуль» — Фабрицио Романо
Саймон Джонс пишет, что учитывая длительный контракт и общий рост цен на качественных игроков, «Ливерпуль» отпустит Гакпо только за огромную сумму.
Андони Ираола: «Это не тот результат, которого мы хотели, но это был самый полезный матч. Мы многое узнали. Можем сделать правильные выводы и исправить некоторые вещи». «Это огромный клуб, у нас невероятная поддержка болельщиков. Мы должны быть полностью готовы к началу сезона». О травме Фримпонга Андони Ираола заявил, что, по его мнению, у Фримпонга нет травмы — это была лишь перегрузка.
«Ливерпуль» проиграл «Лидсу» в товарищеском матче. Возвращаемся в Англию и ждём новостей на трансферном рынке.
Showing the 12 most recent of 23 posts we hold for @liverpool_f. 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.
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.
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 2 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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Liverpool FC | Ливерпуль” (@liverpool_f), 1,782 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/liverpool_f.
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.