Channel
@eFootball_Store
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
131subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001507675855 |
|---|---|
| Type | Channel |
| Username | @eFootball_Store |
| Created | Between 1 August 2021 and 28 June 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/eFootball_Store |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 01:00 | 131 | no change |
| 7 Aug 2026, 01:22 | 131 | first reading |
16 posts held, back to 28 June 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 16 posts for this entry, the most recent from 19 July 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
📋 || 𝐏𝐄𝐒𝐌𝐎 𝐓𝐄𝐀𝐌 ™ معرفی مجموعه تیم بزرگ ᏢᎬᏚᎷᏫ ⤵️ ¹ ◂ کانال پیس ام ⇐ @PES_M ² ◂ کانال پیس پارس ⇐ @PESPARS ³ ◂ کانال پیس فوت ⇐ @PESFOOT ⁴ ◂ کانال پیس نیوز ⇐ @PESMOBILE_NEWS ⁵ ◂ گروه پیس جی ⇐ @PES_G ⁶ ◂ گروه پیس پارس ⇐ @PESPARS_GROUP ⁷ ◂ گروه پیس فوت ⇐ @PESFOOT_GROUP ⁸ ◂ گروه پیس نیوز ⇐ @PMN_G ⁹ ◂ کانال ای فوتبال ⇐ @eFootball_PESMO ¹⁰ ◂ کانال جزیره فوتبالی ⇐@Island120 ¹¹ ◂ گروه چت دریم لیگ ⇐ @DLS_G ¹² ◂ ربا…
Signed ⓔⓡⓕⓐⓝ
.
Signed A B B A S
▪️ @PES_G ▶️ گروه
Signed A B B A S
خریدار اک ناب ایکون شاعر بکهام کرایوف نیمار رومی اتوعو حتما داشته باشه/سبک کوییک کانتر فقط درست مکس شده باشه✅ جی پی سکه زیاد لج و بیس هم زیاد داشته باشه بهتر قیمت مهم نی ایدی خریدار: @Hoseein_1386
Signed ●▬▬๑۩۩๑ĦØ$ЄЄĪИ๑۩۩๑▬▬●
✅فروش 630 تخفیف جزئی ❕کوییک کانتر. ❗️27لجندری بی تکرار. ✔️11تیکت تمدید. ☄60کا پوینت 👌8میل جی پی. ✔️150سکه. ↪️@sobhanpes
Signed 𝐒𝐎𝐁𝐇𝐀𝐍
فرم طاق یا فروش ◾مشخصات اکانت 🔽 🔴 لجندری : 46 بدون احتساب تکراری 🟡 سکه : 250 🔵 جیپی : 1400000 🟣 پوینت : 45000 💶قیمت : 120تومن +پول واسطه 👤 آیدی صاحب اکانت ↩️ @Lionel_messi_m_10 👤ادمین واسطه ↩️ @sobhanpes ---------------------------------- © @eFootball_Store
Signed 𝙈𝙀30
فرم فروش ◾مشخصات اکانت 🔽 🔴 لجندری : 50 ( دارای پک نیمار/ کل بازیکنان ۴۰۰/ سبک بازی: پوزیشن و...... ) 🟢 ۳۰ تا تیکت 🟡 سکه : 2 کا 🔵 جیپی : 13میلیون 🟣 پوینت : 58 کا 💶قیمت : پیشنهادی ( مشخصات بیشتر خواستی بیا پیوی ) 👤 آیدی صاحب اکانت ↩️ @Wolverine12 👤ادمین واسطه ↩️ ---------------------------------- © @eFootball_Store
Signed 𝐒𝐎𝐁𝐇𝐀𝐍
▫️فروش توافقی، طاق نی » ▪️45آیکونیک 10 تکرار، 110 لجند، ۱۰ فیو » ▪20 تیکت تمدید، 60 کا پوینت، 500 سکه » دلال نیاد مف نمیدم❌بازیکنا به درستی مکس شدن✅اکثر ایکونا تمدید شدن/کلی بیس ناب/همه لج های بازی جز چند تا داره ایدی صاحب اکانت: @Hoseein_1386
Signed ●▬▬๑۩۩๑ĦØ$ЄЄĪИ๑۩۩๑▬▬●
▪️فروش فوری📌🏴 ▪️خیلی بازیکنا تازه تمدید شدن ]} (24آیکون / 39400کا پوینت / 665 سکه😍) ▪️10تیکت قرارداد✅ ▪️500بازیکن😉🀄️ 🎴قیمت پیشنهادی🏴 کسی خواست بیاد پی♥️ @you_nex3
Signed γoиɘƨ
◽کد آگهی : ◾مشخصات اکانت 🔽 🔘کارت آیکونیک : 13 🔘کارت لجند : 🔘کارت فیچرد : 🔘سکه : 0 🔘پوینت :40k 🔘جی پی : 300k 💶قیمت :70 ◻️جهت ارتباط با فروشنده کد آگهی را به واسطه بفرستید! 👤 آیدی صاحب اکانت ↩️hossein_1c 👤ادمین واسطه ↩️ ---------------------------------- © @eFootball_Store
Signed 𝐒𝐎𝐁𝐇𝐀𝐍
فرم طاق یا فروش ◾مشخصات اکانت 🔽 🔴 لجندری : زیاد 🟡 سکه : 500 🔵 جیپی : 3.2M 🟣 پوینت : 50 20 تیکت تمدید ↩️ بازیکنا رو سبک کوئیک کانتر مکس شده ✅ برای عکس 22 پیوی 😉 👤 آیدی صاحب اکانت ↩️ @leooom30 👤ادمین واسطه ↩️ @You_nex3 ---------------------------------- © @eFootball_Store
Signed 𝙈𝙀30
فرم طاق یا فروش ◾مشخصات اکانت 🔽 🔴 لجندری : زیاد 🟡 سکه : 100 🔵 جیپی : 3.2M 🟣 پوینت : 50 10 تیکت تمدید ↩️ بازیکنا رو سبک کوئیک کانتر مکس شده ✅ برای عکس 22 پیوی 😉 👤 آیدی صاحب اکانت ↩️ @leooom30 👤ادمین واسطه ↩️ @Kian_asghari ---------------------------------- © @eFootball_Store
Signed 𝙈𝙀30
Showing the 12 most recent of 16 posts we hold for @eFootball_Store. 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.
Citation-graph rank — 1,120,076 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
@eFootball_Store named 5 handles 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.
References a handle that is not a live channel — we have no record it ever was one.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“🛒Store | فروشگاه” (@eFootball_Store), 131 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/eFootball_Store.
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.