درود رفقا
custom 58839836994851355674😁1
Signed 𝐊𝐚𝐩𝐭𝐚𝐧

Channel
@efootbal_community
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Handles named that no longer answer · Cite this entry
966subscribers
-62 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002201794477 |
|---|---|
| Type | Channel |
| Username | @efootbal_community |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/efootbal_community |
Other / unclassifiable — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 43% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Oct 2026, 06:19 | 966 | -19 |
| 18 Sept 2026, 00:18 | 985 | -6 |
| 10 Sept 2026, 19:18 | 991 | -8 |
| 2 Sept 2026, 14:09 | 999 | -2 |
| 30 Aug 2026, 22:33 | 1,001 | -7 |
| 24 Aug 2026, 21:08 | 1,008 | -3 |
| 21 Aug 2026, 02:42 | 1,011 | -4 |
| 17 Aug 2026, 23:43 | 1,015 | -5 |
| 14 Aug 2026, 21:35 | 1,020 | -1 |
| 11 Aug 2026, 12:53 | 1,021 | -4 |
| 8 Aug 2026, 16:55 | 1,025 | -3 |
| 8 Aug 2026, 00:31 | 1,028 | no change |
| 7 Aug 2026, 17:13 | 1,028 | first reading |
20 posts held, back to 30 September 2025 — 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 page 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 20 posts for this entry, the most recent from 17 December 2025. 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.
142 reactions across 19 posts, in 6 distinct kinds. The most used accounts for 28.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5883983699485135567 | 41 | 28.9% | |
| custom 4958699241137505132 | 39 | 27.5% | |
| custom 5884163392326866010 | 28 | 19.7% | |
| custom 5130038440196309937 | 18 | 12.7% | |
| custom 4958626617535497157 | 10 | 7.04% | |
| 😁 | 6 | 4.23% |
Custom emoji. 5 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 19 of the 20 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 142 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 30 September 2025 to 17 December 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
درود رفقا
custom 58839836994851355674😁1
Signed 𝐊𝐚𝐩𝐭𝐚𝐧
فروشی رفقا گوگل دیس پیش بدید زیر همین پست دوتا گپ و چنلم فروشی هست
custom 588416339232686601014
Signed 𝐊𝐚𝐩𝐭𝐚𝐧
چنل برسه به 0️⃣0️⃣0️⃣3️⃣ هزار نفر 0️⃣0️⃣5️⃣ استارز⭐️ رایگان بینتون قرئه کشی میکنم برید ببینم چی میکنید💫 فیک بزنید خداتونو در میارم حواستون باشه
custom 513003844019630993715custom 58839836994851355672custom 49586992411375051321
Signed 𝐊𝐚𝐩𝐭𝐚𝐧
درود رفقا یه چالش گاد دارم براتون گاااااد🤝 بگم چیه؟ ری اکشن بزنید جایزش ب ارزش حدود یک میلیون تومانه✅
custom 49586992411375051329custom 49586266175354971573custom 58841633923268660101
Signed - 𝐒𝐡𝐚𝐲𝐚𝐧 ♱
مبارکشون باشه
custom 58841633923268660101
Signed - 𝐒𝐡𝐚𝐲𝐚𝐧 ♱
Video, posted without a caption
custom 58841633923268660102
Signed - 𝐒𝐡𝐚𝐲𝐚𝐧 ♱
بریم نتیجه قرعه کشیو اعلام کنیم
custom 58839836994851355672custom 58841633923268660101
Signed - 𝐒𝐡𝐚𝐲𝐚𝐧 ♱
قرعه کشی بصورت گردونه شانس برگذار میشه
custom 58841633923268660101
Signed - 𝐒𝐡𝐚𝐲𝐚𝐧 ♱
هی ما میگیم تمومه؟باز دو نفر دیگه میزنن😂تا 3 اگه کسی نزد تمومه قرعه کشی راس ساعت 3 برگذار میشه
Signed - 𝐒𝐡𝐚𝐲𝐚𝐧 ♱
اینو دیگه ببندیم قرعه کشیشو بکنیم تمومه زدید؟
custom 58839836994851355676
Signed - 𝐒𝐡𝐚𝐲𝐚𝐧 ♱
درود رفقا یه چالش گاد دارم براتون گاااااد🤝 بگم چیه؟ ری اکشن بزنید جایزش ب ارزش حدود یک میلیون تومانه✅
custom 58839836994851355676custom 49586266175354971571custom 51300384401963099371
Signed 𝐊𝐚𝐩𝐭𝐚𝐧
این چالش باز میمونه تا فردا هر کی زد اسکرینشو زیر این پست بفرسته قرعه کشی فردا ظهر انجام میشه❤️❤️
custom 49586992411375051324custom 49586266175354971571custom 58839836994851355671
Signed - 𝐒𝐡𝐚𝐲𝐚𝐧 ♱
Showing the 12 most recent of 20 posts we hold for @efootbal_community. 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.
@efootbal_community named 3 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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“𝑮𝒊𝒇𝒕 / 𝑰𝒓𝒂𝒏” (@efootbal_community), 966 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/efootbal_community.
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.