Telegram RegisterThe public register of Telegram
Telegram profile photo for LiverpoolPersian™| لیورپول پرشین

Channel

LiverpoolPersian™| لیورپول پرشین

@liverpoolpersian

On this record: Topic · Previous handles · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Polls · Citations · Telegram's recommendations · Cite this entry

8,459subscribers

-45 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001001760655
TypeChannel
Username@liverpoolpersian
Description❤️نخستین مرجع هواداری فارسی لیورپول❤️ 📰 وبسایت↙️ Www.liverpoolpersian.com 👥 اینستاگرام 118k↙️ Instagram.com/liverpoolpersian_ 🎬 آرشیو ویدئو ↙️ @LiverpoolPersianArchive 🏅فروشگاه لیورپول ↙️ @Liverpoolstore
CreatedBetween 1 September 2015 and 31 December 2015 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 November 2026
Measurements held27
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/liverpoolpersian

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 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 the other topics.

Previous handles

Recorded in 2019 as “Liverpoolpersian™/لیورپول” — the title held for this same channel (matched by Telegram id, not by handle) in the Pushshift Telegram Dataset, a third-party archive captured in 2019-2020, years before this register made its own first observation. CC BY 4.0, Baumgartner, Zannettou, Squire & Blackburn (2020), Zenodo. A third party’s dated snapshot, not a measurement this register made itself.

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 in near-verbatim form 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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@liverpoolpersian/146046 · this entry24 Aug 2026, 20:14 UTC@LiverpooliFC/1472225 Aug 2026, 10:48 UTC0.9915 hours
@liverpoolpersian/148165 · this entry15 Nov 2026, 10:13 UTC@LiverpooliFC/1812316 Nov 2026, 06:15 UTC0.9920 hours
@liverpoolpersian/148035 · this entry8 Nov 2026, 17:07 UTC@LiverpooliFC/179058 Nov 2026, 18:47 UTC0.991.7 hours
@liverpoolpersian/148043 · this entry8 Nov 2026, 21:01 UTC@LiverpooliFC/179179 Nov 2026, 07:10 UTC0.9910 hours
@liverpoolpersian/148100 · this entry11 Nov 2026, 21:26 UTC@LiverpooliFC/1803112 Nov 2026, 14:27 UTC0.9717 hours
@liverpoolpersian/148059 · this entry10 Nov 2026, 05:42 UTC@LiverpooliFC/1794910 Nov 2026, 07:57 UTC0.962.3 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@LiverpooliFC23 (8/8 hand-verifiable sample passed)0.973.1 hoursthis entry (23–0)
@LFCTEL19 (8/8 hand-verifiable sample passed)0.9834 minutesthis entry (19–0)
@PremierLeague_Irani8 (8/8 hand-verifiable sample passed)0.9863 minutes@PremierLeague_Irani (8–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. 8 of the 8 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 338 comparable posts for this entry, running 5 August 2026 to 18 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.

  • 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).

Recorded under the keys clone_copy · clone_source, last confirmed 19 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.

Growth

8,4488,5668,5075 August 2026 — 8,504 subscribers6 August 2026 — 8,503 subscribers6 August 2026 — 8,503 subscribers9 August 2026 — 8,448 subscribers12 August 2026 — 8,457 subscribers16 August 2026 — 8,471 subscribers19 August 2026 — 8,483 subscribers22 August 2026 — 8,489 subscribers25 August 2026 — 8,527 subscribers28 August 2026 — 8,550 subscribers31 August 2026 — 8,551 subscribers3 September 2026 — 8,565 subscribers9 September 2026 — 8,554 subscribers13 September 2026 — 8,560 subscribers16 September 2026 — 8,558 subscribers1 October 2026 — 8,566 subscribers8 October 2026 — 8,556 subscribers13 October 2026 — 8,537 subscribers16 October 2026 — 8,550 subscribers20 October 2026 — 8,547 subscribers22 October 2026 — 8,544 subscribers29 October 2026 — 8,531 subscribers1 November 2026 — 8,514 subscribers4 November 2026 — 8,498 subscribers7 November 2026 — 8,483 subscribers12 November 2026 — 8,480 subscribers16 November 2026 — 8,459 subscribers8,4595 August 202616 November 2026
27 measurements spanning 103 days, net -45. 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 8,430–8,584 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
16 Nov 2026, 23:488,459-21
12 Nov 2026, 00:468,480-3
7 Nov 2026, 21:488,483-15
4 Nov 2026, 10:488,498-16
1 Nov 2026, 10:468,514-17
29 Oct 2026, 06:488,531-13
22 Oct 2026, 22:398,544-3
20 Oct 2026, 01:378,547-3
16 Oct 2026, 20:188,550+13
13 Oct 2026, 21:308,537-19
8 Oct 2026, 12:428,556-10
1 Oct 2026, 20:158,566+8
16 Sept 2026, 17:028,558-2
13 Sept 2026, 05:418,560+6
9 Sept 2026, 06:398,554-11
3 Sept 2026, 14:168,565+14
31 Aug 2026, 06:568,551+1
28 Aug 2026, 12:238,550+23
25 Aug 2026, 02:538,527+38
22 Aug 2026, 03:088,489first reading

Engagement

534 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 60 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
22.7%
avg views ÷ 8,459 subscribers
Avg views / post
1,920
187 posts measured
Reaction rate
2.59%
reactions ÷ views · ER floor
Posts in window
196
of 534 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 19 November 2026
Posts held534 (5 August 2026 – 19 November 2026)
Views total358,346
Reactions total9,272
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken19 Nov 2026, 16:11 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

Photos
≈47,100
Videos
≈4,920
Links
≈3,300

Lifetime counters from Telegram’s own channel header, read 19 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
13m 24s
Average length
26s

Measured directly from 31 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.

Reaction mix

21,779 reactions across 505 posts, in 12 distinct kinds. The most used accounts for 52.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤11,51652.9%
👍3,26715.0%
👎1,9849.11%
🔥1,5667.19%
😁1,1785.41%
💔1,0404.78%
😭7043.23%
❤‍🔥1830.84%
🤝990.455%
👏950.436%
🫡950.436%
👌520.239%

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 518 of the 534 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 22,351 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 534 most recent posts we hold, published 5 August 2026 to 19 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.

Recent posts

Telegram’s own ‘edited’ marker: 72 of 196 posts held from the last 30 days (36.7%) 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).

19 Nov 2026, 13:56 UTC705 views26 reactionsread 19 November 2026

🟥 آخرین وضعیت از دیگر مصدومان لیورپول: رایان گراونبرخ و جرمی فریمپونگ به تمرینات گروهی بازگشته اند. همچنین نگرانی‌ای بابت مصدومیت ویرجیل فن‌دایک و دومینیک سوبوسلای وجود ندارد. هر دو امروز در تمرینات حضور داشتند. 🔗 Source: Sky Sports 🆔@LiverpoolPersian

❤26

Signed Amirhossein

19 Nov 2026, 08:05 UTC≈1,410 views59 reactionsread 19 November 2026
Photo

🔴 رئال مادرید درحال بررسی شرایط، برای جذب الکسیس مک آلیستر در پایان ماه می[خرداد] بود؛ اما لیورپول از ادامه همکاری با مک آلیستر خوشحال است. ما میتونیم تایید کنیم که مذاکرات بین لیورپول و مک آلیستر برای یک قرارداد جدید در جریان است، البته در مراحل اولیه قرار دارند. 🔗Source: 🥇Fabrizio romano 🆔@LiverpoolPersian

👍36❤23

Signed MaK

19 Nov 2026, 07:45 UTC≈1,460 views38 reactionsread 19 November 2026
Photo

🎙️ دکو، مدیر ورزشی بارسلونا: آرائوخو و لیورپول؟ در تابستان بعدی قابل بحثه. ما باهم رابطه خوبی داریم و به تصمیمش احترام میزاریم. مهم ترین چیز اینه که خوشحال ببینیمش. اگه اون تصمیم به موندن تو لیورپول بگیره، ما باهاش مشکلی نداریم. البته یک مقدار پول هم بدک نیست… 🔗Source: 🥇Fabrizio romano 🆔@LiverpoolPersian

❤33👍5

Signed MaK

19 Nov 2026, 07:22 UTC≈1,450 views97 reactionsread 19 November 2026
Photo

🔴 لیورپول ترجیح میدهد برای پست دفاع راست، بازیکن بزرگی به خدمت نگیرد؛ زیرا آنها به کانر بردلی اعتماد دارند. همچنین ایرائولا زمانی که در بورنموث بود، علاقه به جذب کانر بردلی به صورت قرضی داشت. 🔗Source: 🥇Paul joyce 🆔@LiverpoolPersian

👍67👎17❤10😁3

Signed MaK

19 Nov 2026, 03:35 UTC≈1,700 views25 reactionsread 19 November 2026
Photo

و بازم داستان تکراری اشتباهات داوری و VAR برای لیورپول که البته هواداراش دیگه به این قضیه عادت کردند؛ این بار پنل کارشناسی داوری kmi خطای پنالتی دقیقه ۹۳ کرکز مقابل کریستال پالاس را اشتباه تشخیص داد تا امتیاز منفی برای تیم داوری اون بازی ثبت بشه. پ.ن ۱: از وقتی هوادار این تیم شدم و یادمه این اشتباهات فقط بضرر این باشگاه بوده و هیچ وقت واسه یک بار اشتباهم که شده این تصمیمات به نفع لیورپول نبود! نمونه خیلی خنده دارش ک…

❤21🤝3👍1

Signed . ༄ḪᎯᗰᎥᗪ࿐.

18 Nov 2026, 19:51 UTC≈1,850 views55 reactionsread 19 November 2026
Video

🔴 بردلی آن فایرر 🔥👀 🆔 @LiverpoolPersian

❤49🔥6

Signed Mazhari

18 Nov 2026, 19:39 UTC≈1,850 views47 reactionsread 19 November 2026
Photo

🔴👀 تصاویری از تمرین امروز تیم لیورپول با حضور کانر بردلی ، جرمی فریمپونگ و لیونی در تمرینات گروهی تیم 🆔 @LiverpoolPersian

🔥40❤3😁3👍1

Signed Mazhari

18 Nov 2026, 12:09 UTC≈2,040 views75 reactionsread 19 November 2026

🔴 دقایقی پیش بن جیکوبز در صفحه شخصی توییتر خود این خبر را تایید کرد و گفت جولین وارد مذاکرت اولیه‌ای با پدر مک آلیستر در این خصوص داشته است. 🔗Source: 🥇Ben Jacobs 🆔@LiverpoolPersian

❤74👍1

Signed Amirhossein

18 Nov 2026, 11:57 UTC≈2,090 views63 reactionsread 19 November 2026
Photo

🟥 کانر بردلی و جیووانی لئونی به تمرینات گروهی بازگشتند. هوگو اکیتیکه تنها مصدوم بلندمدت باقی‌مانده لیورپول است. روند بهبودی مهاجم فرانسوی نیز مثبت پیش می‌رود و او امیدوار است در ماه دسامبر به میادین بازگردد. 🔗Source: 🥇James Pearce 🆔@LiverpoolPersian

❤59👍4

Signed Amirhossein

18 Nov 2026, 10:58 UTC≈1,980 views48 reactionsread 19 November 2026
Photo

📣 بازی بعدی (پرمیرلیگ - هفته یازدهم) ⚔️ لیورپول 🆅🆂 منچستریونایتد 🗓 یکشنبه ۱ آذر ⏰ ساعت: ۲۰:۰۰ 🏟 ورزشگاه: آنفیلد 📺 پخش زنده: نامشخص #LIVMUN @LiverpoolPersian

❤43🔥5

Signed امیرعلی؛

17 Nov 2026, 21:53 UTC≈2,120 views71 reactionsread 19 November 2026
Photo

🔴 بازی مجارستان با ایرلند شمالی با نتیجه یک بر یک به پایان رسید. 🔺 دومینیک سوبوسلای و میلوش کرکز از ابتدا در ترکیب مجارستان حضور داشتند. 🔺 میلوش کرکز به عنوان بهترین بازیکن زمین انتخاب شده. 🆔 @LiverpoolPersian

😁46❤22😭3

Signed Mazhari

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

Posts edited after publishing

@liverpoolpersian edited 4 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
10 August 2026
Most recent edit
18 November 2026

Posts recorded as deleted after publishing

We recorded 5 posts on @liverpoolpersian as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
9 August 2026
Most recent seen missing
17 November 2026
Median time before seen missing
20 hours
Seen missing in the last 30 days
4

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

1 Nov 2026, 18:48 UTCAnonymous Poll1,260 voters approx.

بدترین بازیکن تیم مقابل آرسنال❓

  1. ژاکه8%
  2. گاگپو23%
  3. آلیسون14%
  4. ایساک10%
  5. کرکز47%
  6. فندایک5%
  7. بارکولا26%

The shares total 133%, 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.

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 534 most recent posts we hold, published 5 August 2026 to 19 November 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.

Forward network

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.

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.

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.

Appears in Telegram’s recommendations for other channels

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.

Liverpool | لیورپول
@LiverpoolClub · 43,067
Telegram ranks this channel #5 of 87 here — alongside 86 others — read 29 August 2026
FootFun | فوتفان
@FootFun2020 · 82,965
Telegram ranks this channel #35 of 94 here — alongside 93 others — read 18 August 2026
نقل و انتقالات فوتبالی
@TransferMarketsIran · 21,048
Telegram ranks this channel #42 of 88 here — alongside 87 others — read 22 September 2026
طرفداری
@tarafdari · 99,363
Telegram ranks this channel #45 of 96 here — alongside 95 others — read 15 August 2026
Football Forever
@Ritzobet_En · 40,211
Telegram ranks this channel #46 of 71 here — alongside 70 others — read 30 August 2026
دانش معنوی و خودشناسی
@Skolony · 27,007
Telegram ranks this channel #52 of 61 here — alongside 60 others — read 11 September 2026
ترول فوتبال
@trollfootball_persian · 94,369
Telegram ranks this channel #55 of 93 here — alongside 92 others — read 22 August 2026
نقل و انتقالات فوتبال
@Footitransfers · 58,627
Telegram ranks this channel #57 of 96 here — alongside 95 others — read 19 August 2026
آپارات اسپرت | پخش زنده
@aparatsport · 73,612
Telegram ranks this channel #60 of 91 here — alongside 90 others — read 2 September 2026
⚽️Dashagh News⚽️
@Dashaghnews · 111,748
Telegram ranks this channel #60 of 93 here — alongside 92 others — read 14 August 2026
فابریتزیو رومانو | Fabrizio Romano
@FabirizioRomano · 54,425
Telegram ranks this channel #61 of 98 here — alongside 97 others — read 19 August 2026
فاضل نظری
@fazelnazarigram · 39,585
Telegram ranks this channel #68 of 69 here — alongside 68 others — read 31 August 2026
امتحان نهایی
@nahayi_emtehan1403 · 31,351
Telegram ranks this channel #74 of 74 here — alongside 73 others — read 31 August 2026
کتاب سرا دهم یازدهم دوازدهم 📚
@ketabsara_konkor · 197,170
Telegram ranks this channel #76 of 79 here — alongside 78 others — read 17 August 2026
🎵آوایِ حقوق🎵
@LAWSONG · 21,174
Telegram ranks this channel #81 of 83 here — alongside 82 others — read 25 September 2026
فوت توییت ⚽️
@Foot_twitte · 26,863
Telegram ranks this channel #83 of 89 here — alongside 88 others — read 11 September 2026
ابوطالب حسینی
@abutalebhosseini · 96,985
Telegram ranks this channel #85 of 92 here — alongside 91 others — read 16 August 2026

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.

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

“LiverpoolPersian™| لیورپول پرشین” (@liverpoolpersian), 8,459 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/liverpoolpersian.

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.