👀 اکانتسل با کلی اکانت آلتیمیت خفن اومده که میتونید با بهترین قیمت خریداری کنید!🤩 💡 اگه اکانت خفن داری و میخوای بفروشی هم میتونی بدون هزینه و به صورت رایگان داخل کانال آگهی کنید👇🏻 💬 @AccountSellFans
👍22❤3👎1

Channel
@EAFC_IR
On this record: Topic · Observations · Growth · Engagement · What this channel posts · View velocity · Reactions · Stars · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Telegram's recommendations · Domains linked from posts · Cite this entry
1,159,637subscribers
+27,510 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1001639226169 |
|---|---|
| Type | Channel |
| Username | @EAFC_IR |
| Description | ارادتمند همگی به چنل EAFC IR بزرگ ترین و فعال ترین چنل خبری FIFA/FC در ایران خوش آمدید 🌹 پوشش دهی اخبار و اتفاقات مربوط به التیمیت تیم و کریر مود به صورت کاملا آنی 🗣⚡ ترجمه ابجکتیوها و بررسی تمام اس بی سی ها 📝 مدیریت مجموعه : @AmirFrhadi 👤 |
| 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 | 25 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/EAFC_IR |
Gaming — 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 8 August 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 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.
On 430 of the 507 posts we watched over 30 days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.0047 reactions per view.
| Post | Over | Views | Reactions | Expected |
|---|---|---|---|---|
| /371253 Sept 2026, 14:20 UTC | 30 minutes | 14,700 → 21,100at least +6,300 | 289 → 290at most +2 | +29.6 |
| /371253 Sept 2026, 14:20 UTC | 3.1 hours | 24,300 → 29,000at least +4,600 | 302 → 304at most +3 | +21.6 |
| /371253 Sept 2026, 14:20 UTC | 30 minutes | 29,000 → 37,100at least +8,000 | 304 → 304at most +1 | +37.6 |
| /371253 Sept 2026, 14:20 UTC | 30 minutes | 37,100 → 44,200at least +7,000 | 304 → 304at most +1 | +32.9 |
| /371253 Sept 2026, 14:20 UTC | 34 minutes | 44,200 → 51,200at least +6,900 | 304 → 304at most +1 | +32.4 |
| /371253 Sept 2026, 14:20 UTC | 1.9 hours | 52,300 → 71,400at least +19,000 | 307 → 307at most +1 | +89.4 |
| /3700528 Aug 2026, 10:46 UTC | 30 minutes | 8,970 → 15,000at least +5,930 | 389 → 390at most +2 | +27.9 |
| /3700528 Aug 2026, 10:46 UTC | 30 minutes | 15,400 → 21,000at least +5,500 | 391 → 393at most +3 | +25.9 |
| /3700528 Aug 2026, 10:46 UTC | 35 minutes | 24,900 → 35,100at least +10,100 | 401 → 401at most +1 | +47.5 |
| /3700528 Aug 2026, 10:46 UTC | 30 minutes | 35,200 → 56,000at least +20,700 | 401 → 401at most +1 | +97.3 |
| /3700528 Aug 2026, 10:46 UTC | 30 minutes | 63,800 → 77,300at least +13,400 | 404 → 404at most +1 | +63.0 |
| /3704830 Aug 2026, 07:03 UTC | 35 minutes | 17,700 → 20,800at least +3,000 | 248 → 248at most +1 | +14.1 |
| /3704830 Aug 2026, 07:03 UTC | 30 minutes | 21,200 → 26,900at least +5,600 | 249 → 250at most +2 | +26.3 |
| /3704830 Aug 2026, 07:03 UTC | 29 minutes | 27,600 → 32,800at least +5,100 | 251 → 251at most +1 | +24.0 |
| /3704830 Aug 2026, 07:03 UTC | 41 minutes | 32,800 → 48,300at least +15,400 | 251 → 251at most +1 | +72.4 |
| /3704830 Aug 2026, 07:03 UTC | 8.5 hours | 49,100 → 77,400at least +28,200 | 251 → 251at most +1 | +132.6 |
| /3705030 Aug 2026, 12:06 UTC | 35 minutes | 10,200 → 16,400at least +6,100 | 356 → 362at most +7 | +28.7 |
| /3705030 Aug 2026, 12:06 UTC | 30 minutes | 17,200 → 22,900at least +5,600 | 367 → 368at most +2 | +26.3 |
| /3705030 Aug 2026, 12:06 UTC | 29 minutes | 24,300 → 28,900at least +4,500 | 374 → 374at most +1 | +21.2 |
| /3705030 Aug 2026, 12:06 UTC | 41 minutes | 28,900 → 45,400at least +16,400 | 374 → 374at most +1 | +77.1 |
| /3705030 Aug 2026, 12:06 UTC | 9.5 hours | 46,700 → 76,900at least +30,100 | 379 → 379at most +1 | +141.6 |
| /370941 Sept 2026, 17:47 UTC | 30 minutes | 14,000 → 17,100at least +3,000 | 239 → 241at most +3 | +14.1 |
| /370941 Sept 2026, 17:47 UTC | 35 minutes | 21,200 → 25,500at least +4,200 | 242 → 243at most +2 | +19.8 |
| /370941 Sept 2026, 17:47 UTC | 31 minutes | 25,500 → 32,400at least +6,800 | 243 → 246at most +4 | +32.0 |
| /370941 Sept 2026, 17:47 UTC | 54 minutes | 32,400 → 38,700at least +6,200 | 246 → 246at most +1 | +29.2 |
| /370941 Sept 2026, 17:47 UTC | 35 minutes | 38,800 → 45,500at least +6,600 | 246 → 246at most +1 | +31.0 |
| /370971 Sept 2026, 19:04 UTC | 30 minutes | 16,100 → 19,300at least +3,100 | 340 → 340at most +1 | +14.6 |
| /370971 Sept 2026, 19:04 UTC | 35 minutes | 19,300 → 24,300at least +4,900 | 340 → 342at most +3 | +23.0 |
| /370971 Sept 2026, 19:04 UTC | 54 minutes | 27,400 → 36,800at least +9,300 | 343 → 344at most +2 | +43.7 |
| /370971 Sept 2026, 19:04 UTC | 5.3 hours | 44,800 → 51,800at least +6,900 | 360 → 360at most +1 | +32.4 |
| /370971 Sept 2026, 19:04 UTC | 30 minutes | 65,000 → 76,500at least +11,400 | 360 → 360at most +1 | +53.6 |
| /370981 Sept 2026, 19:27 UTC | 35 minutes | 16,400 → 19,000at least +2,500 | 230 → 230at most +1 | +11.8 |
| /370981 Sept 2026, 19:27 UTC | 31 minutes | 19,000 → 25,200at least +6,100 | 230 → 231at most +2 | +28.7 |
| /370981 Sept 2026, 19:27 UTC | 54 minutes | 25,200 → 35,800at least +10,500 | 231 → 233at most +3 | +49.4 |
| /370981 Sept 2026, 19:27 UTC | 35 minutes | 36,200 → 42,400at least +6,100 | 234 → 234at most +1 | +28.7 |
| /370981 Sept 2026, 19:27 UTC | 6.8 hours | 45,100 → 52,200at least +7,000 | 266 → 266at most +1 | +32.9 |
| /371162 Sept 2026, 20:34 UTC | 31 minutes | 17,000 → 22,200at least +5,100 | 484 → 485at most +2 | +24.0 |
| /371162 Sept 2026, 20:34 UTC | 34 minutes | 29,400 → 35,400at least +5,900 | 489 → 489at most +1 | +27.7 |
| /371162 Sept 2026, 20:34 UTC | 62 minutes | 35,400 → 41,200at least +5,700 | 489 → 489at most +1 | +26.8 |
| /371162 Sept 2026, 20:34 UTC | 3.0 hours | 43,800 → 53,000at least +9,100 | 507 → 508at most +2 | +42.8 |
| /371162 Sept 2026, 20:34 UTC | 5.0 hours | 62,900 → 76,200at least +13,200 | 508 → 508at most +1 | +62.1 |
| /371213 Sept 2026, 12:48 UTC | 30 minutes | 19,600 → 23,400at least +3,700 | 146 → 146at most +1 | +17.4 |
| /371213 Sept 2026, 12:48 UTC | 5.3 hours | 24,200 → 32,100at least +7,800 | 147 → 148at most +2 | +36.7 |
| /371213 Sept 2026, 12:48 UTC | 30 minutes | 32,100 → 39,000at least +6,800 | 148 → 148at most +1 | +32.0 |
| /371213 Sept 2026, 12:48 UTC | 34 minutes | 39,000 → 48,400at least +9,300 | 148 → 148at most +1 | +43.7 |
| /371213 Sept 2026, 12:48 UTC | 5.2 hours | 53,400 → 77,600at least +24,100 | 149 → 149at most +1 | +113.3 |
| /371293 Sept 2026, 17:00 UTC | 30 minutes | 17,400 → 23,900at least +6,400 | 474 → 476at most +3 | +30.1 |
| /371293 Sept 2026, 17:00 UTC | 54 minutes | 25,400 → 30,700at least +5,200 | 483 → 483at most +1 | +24.5 |
| /371293 Sept 2026, 17:00 UTC | 30 minutes | 30,700 → 36,300at least +5,500 | 483 → 483at most +1 | +25.9 |
| /371293 Sept 2026, 17:00 UTC | 30 minutes | 36,300 → 42,200at least +5,800 | 483 → 483at most +1 | +27.3 |
| /371293 Sept 2026, 17:00 UTC | 5.2 hours | 49,000 → 71,300at least +22,200 | 487 → 487at most +1 | +104.4 |
Expected is the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).
What this does and does not say. It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.
Recorded under the key view_reaction_decoupling, last confirmed 27 September 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 |
|---|---|---|
| 25 Sept 2026, 19:02 | 1,159,637 | +25,881 |
| 17 Sept 2026, 09:56 | 1,133,756 | +4,752 |
| 15 Sept 2026, 08:38 | 1,129,004 | +2,619 |
| 13 Sept 2026, 19:18 | 1,126,385 | -9,393 |
| 12 Sept 2026, 01:20 | 1,135,778 | +16,120 |
| 9 Sept 2026, 19:55 | 1,119,658 | -4,694 |
| 6 Sept 2026, 09:54 | 1,124,352 | -597 |
| 4 Sept 2026, 05:35 | 1,124,949 | -10,501 |
| 2 Sept 2026, 15:43 | 1,135,450 | +17,822 |
| 1 Sept 2026, 15:14 | 1,117,628 | -12,566 |
| 31 Aug 2026, 14:53 | 1,130,194 | -7,896 |
| 30 Aug 2026, 14:55 | 1,138,090 | +21,736 |
| 29 Aug 2026, 14:38 | 1,116,354 | -15,872 |
| 28 Aug 2026, 17:53 | 1,132,226 | -14,465 |
| 27 Aug 2026, 17:57 | 1,146,691 | +31,774 |
| 26 Aug 2026, 15:53 | 1,114,917 | -9,646 |
| 25 Aug 2026, 18:24 | 1,124,563 | -13,766 |
| 24 Aug 2026, 19:36 | 1,138,329 | -14,653 |
| 23 Aug 2026, 04:46 | 1,152,982 | +28,222 |
| 21 Aug 2026, 16:27 | 1,124,760 | first reading |
994 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 138 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 26 September 2026 |
|---|---|
| Posts held | 994 (6 August 2026 – 26 September 2026) |
| Views total | 40,039,580 |
| Reactions total | 233,005 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 06:00 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.
Lifetime counters from Telegram’s own channel header, read 26 September 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.
Measured directly from 41 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.
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 516 of this channel’s own posts over the last 30 days (8 of the 24-hour readings behind this are interpolated, not measured directly): across 467 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 7.3 hours of being posted; a typical post has already reached 34.3% of its 24-hour view count within the first hour, and 55.6% within the first six; the median 24-hour reach across those posts is 49,300 views — 4.25% of this channel’s own subscriber count (90th percentile 56,600).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /3763726 Sept 2026, 21:24 UTC | 1526 minutes – 8.6 hours old | 46,600 views ~26 reactions | 60 minutes: 22,336 interp. → 3.0 hours: 22,856 interp. → 6.0 hours: 45,800still climbing at last reading | not yet at 24h | 3.8 hoursprovisional — final view count still climbing |
| /3763626 Sept 2026, 20:58 UTC | 1622 minutes – 9.0 hours old | 47,800 views ~297 reactions | 60 minutes: 21,778 interp. → 3.0 hours: 22,600 → 6.0 hours: 45,800still climbing at last reading | not yet at 24h | 4.2 hoursprovisional — final view count still climbing |
| /3763526 Sept 2026, 20:34 UTC | 1716 minutes – 9.4 hours old | 48,000 views ~1,427 reactions | 60 minutes: 19,237 interp. → 3.0 hours: 22,400 → 6.0 hours: 47,234 interp.still climbing at last reading | not yet at 24h | 4.6 hoursprovisional — final view count still climbing |
| /3763426 Sept 2026, 19:39 UTC | 196 minutes – 10 hours old | 48,300 views ~28 reactions | 60 minutes: 15,318 interp. → 3.0 hours: 22,253 interp. → 6.0 hours: 47,800still climbing at last reading | not yet at 24h | 5.6 hoursprovisional — final view count still climbing |
| /3763326 Sept 2026, 19:14 UTC | 1930 minutes – 11 hours old | 48,900 views ~223 reactions | 60 minutes: 14,100 → 3.0 hours: 22,900 → 6.0 hours: 23,200views have flattened out | not yet at 24h | 6.0 hours |
| /3763226 Sept 2026, 19:01 UTC | 214 minutes – 11 hours old | 49,800 views ~491 reactions | 60 minutes: 15,517 interp. → 3.0 hours: 24,036 interp. → 6.0 hours: 24,400still climbing at last reading | not yet at 24h | 6.2 hoursprovisional — final view count still climbing |
| /3763126 Sept 2026, 18:36 UTC | 2129 minutes – 11 hours old | 53,000 views ~289 reactions | 60 minutes: 16,570 interp. → 3.0 hours: 24,606 interp. → 6.0 hours: 25,000still climbing at last reading | not yet at 24h | 6.6 hoursprovisional — final view count still climbing |
| /3763026 Sept 2026, 17:41 UTC | 234 minutes – 12 hours old | 53,200 views ~55 reactions | 60 minutes: 17,613 interp. → 3.0 hours: 25,500 → 6.0 hours: 26,100 → 12 hours: 53,200views have flattened out | not yet at 24h | 7.5 hours |
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
397,209 reactions across 989 posts, in 39 distinct kinds. The most used accounts for 21.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 87,184 | 21.9% | |
| 👎 | 50,137 | 12.6% | |
| 🔥 | 40,240 | 10.1% | |
| 🤣 | 33,352 | 8.40% | |
| ❤ | 30,611 | 7.71% | |
| 💔 | 22,946 | 5.78% | |
| 👀 | 13,424 | 3.38% | |
| 🤯 | 13,144 | 3.31% | |
| 😐 | 10,935 | 2.75% | |
| 🕊 | 10,278 | 2.59% | |
| 💩 | 8,402 | 2.12% | |
| 👌 | 7,929 | 2.00% | |
| ❤🔥 | 7,776 | 1.96% | |
| 🥱 | 6,699 | 1.69% | |
| 😢 | 6,248 | 1.57% | |
| 👏 | 5,415 | 1.36% | |
| 🍌 | 5,099 | 1.28% | |
| 💯 | 4,664 | 1.17% | |
| ⚡ | 4,644 | 1.17% | |
| 😍 | 4,627 | 1.16% | |
| 19 further kinds | 23,455 | 5.90% |
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 989 of the 994 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 397,209 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 994 most recent posts we hold, published 6 August 2026 to 26 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 @EAFC_IR. 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 994 most recent posts we hold for this entry, published 6 August 2026 to 26 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.
👀 اکانتسل با کلی اکانت آلتیمیت خفن اومده که میتونید با بهترین قیمت خریداری کنید!🤩 💡 اگه اکانت خفن داری و میخوای بفروشی هم میتونی بدون هزینه و به صورت رایگان داخل کانال آگهی کنید👇🏻 💬 @AccountSellFans
👍22❤3👎1
📌 دومین جوایز اسکواد بتل FC27 فردا راس ساعت 10:30 منتشر میشه 🔥🚫 🎮The Most Active EAFC Channel 👇 😀☺️😃😉😍 😍 @EAFC_IR ➖➖➖➖➖
🔥218💯37😍24❤7👌4👏3🆒3👍1
📌 پک لاک FC27 تا اینجا چطور بوده براتون 📦❓ 🎮The Most Active EAFC Channel 👇 ✍️🔹✍️ 🔹✍️ 🔤🔤🔤🔤 🔤🔤 ✍️🔹✍️ 🔹✍️ ✉️ @EAFC_IR 🔥 🔹🔹🔹🔹🔹
👎949👍366💩36💔32🍌28🕊13❤3
🥸 قرعه کشی یک عدد GTA 6 پلی استیشن ظرفیت ۲ یا ۳ یا ایکس باکس ظرفیت هوم یا سوویچ ( بستگی به پلتفرم کاربر و انتخاب ظرفیت دلخواه )🔥🔥🔥یا معادل وجه نقد ظرفیت دوم پلی استیشن برای شرکت در قرعه کشی کافیه ربات زیر رو استارت کنید و عضو کانال رنک ۱ بشید 🔐 یک کد اختصاصی براتون ارسال میشه 🗓 تاریخ قرعه کشی GTA پنجشنبه ۹ مهر ساعت ۱۰ شب ربات شرکت در قرعه کشی⬇️⬇️ 📱 @rank1Boss_bot 📌دوستانی که آیدیشون مخفی هست پیغام بات و کدشون ر…
👍24❤3🍾1
📌 خیلیا امروز مشکل ورود به بازی یا دیسکانکت شدن رو داشتن...🤦♂️ 🎮The Most Active EAFC Channel 👇 ✍️🔹✍️ 🔹✍️ 🔤🔤🔤🔤 🔤🔤 ✍️🔹✍️ 🔹✍️ ✉️ @EAFC_IR 🔥 🔹🔹🔹🔹🔹
🍌94💔43👍19😢18🤯11👎10😭10💩9
📌 نحوه گل کردن هر ضربه ایستگاهی در FC27 اونم به سادهترین شکل ممکن!🔥😎 حرکت خیلی ساده ای هست و اگه درست اجراش کنی دروازهبان هیچ شانسی نداره 🥶 🎮 فقط کافیه آنالوگ رو 5 جهت بچرخونی + L1 + مربع ✅ 🎮The Most Active EAFC Channel 👇 ✍️🔹✍️ 🔹✍️ 🔤🔤🔤🔤 🔤🔤 ✍️🔹✍️ 🔹✍️ ✉️ @EAFC_IR 🔥 🔹🔹🔹🔹🔹
❤293👍55🆒44🔥32🙏23👀18⚡14👎12
📌 10 تا از بهترین مهاجم های حال حاضر بازی با بودجه 50K 🔥💰 🎮The Most Active EAFC Channel 👇 ✍️🔹✍️ 🔹✍️ 🔤🔤🔤🔤 🔤🔤 ✍️🔹✍️ 🔹✍️ ✉️ @EAFC_IR 🔥 🔹🔹🔹🔹🔹
👍152❤83💯33👏12👌4😍4🔥1
🚀 سرویس وایرگارد توربو 🇳🇱🇩🇪🇹🇷 ❤️🔥اگر از سرویس های ضعیف و پر و نوسان خسته شدی یک بار وایرگارد رو امتحان کن ! 🟢 ویژگی ها: ✅ مناسب گیم سنگین ، استریم، وبگردی و شبکههای اجتماعی 🔝 پایداری و سرعت بالا 🔝 ⚡️ پینگ بسیار پایین ⚡️ 💎 همراه با ضمانت بازگشت وجه ⭐️مخصوص هوش مصنوعی و ابزارهای AI 👍 • تست رایگان قبل از خرید 🎁 💰 با افتخار پایین ترین قیمت وایرگارد ایران 👍 با ضمانت بازگشت وجه خرید کنید ❤️ @Almavpn1_bot
👍51❤3👎1
📌 به کدوم باید خندید 😂😂 🎮The Most Active EAFC Channel 👇 ✍️🔹✍️ 🔹✍️ 🔤🔤🔤🔤 🔤🔤 ✍️🔹✍️ 🔹✍️ ✉️ @EAFC_IR 🔥 🔹🔹🔹🔹🔹
🤣435😁63👀33😐25🗿22🤯18👍12❤4
#رسمی✔️ 📌 کانتنت جدیدی که امشب منتشر شد 📦 اس بی سی یا آبجکتیو منتشر شد ❌ 🎮The Most Active EAFC Channel 👇 😀☺️😃😉😍 😍 @EAFC_IR ➖➖➖➖➖
🥱156🥴79🍌77👎40👍24🤔21🤣19❤18
⚽️ پرشین آلتیمیت: انتخاب حرفه ای ها برای FC ⚽️ 🔸 خرید کوین fc27 به روش کوییک سل و وب اپ باز 🎮 💵تسویه آنی 💵 📱 لینک کانال تلگرام ( جهت فروش کوین به ما ) 👇 https://t.me/persianultimate 📱 آدرس سایت تخصصی پرشین آلتیمیت 👇 https://persianultimate.ir/
👍20❤3👎2
📌رکورد یکی از پلیر ها در لایو ایونت 💀 🎮The Most Active EAFC Channel 👇 ✍️🔹✍️ 🔹✍️ 🔤🔤🔤🔤 🔤🔤 ✍️🔹✍️ 🔹✍️ ✉️ @EAFC_IR 🔥 🔹🔹🔹🔹🔹
🤣397🕊57👍34🔥33❤31👎21👀14🗿14
Showing the 12 most recent of 994 posts we hold for @EAFC_IR. 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.
@EAFC_IR edited 49 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.
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.
@EAFC_IR named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 11 August 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 13 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
2 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“🎮 FC27 | EAFC IR 🎮” (@EAFC_IR), 1,159,637 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/EAFC_IR.
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.