Channel
@MFC_ESKAR
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
582subscribers
-9 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001262744828 |
|---|---|
| Type | Channel |
| Username | @MFC_ESKAR |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/MFC_ESKAR |
Sports — 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 21 September 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 20:01 | 582 | -2 |
| 9 Sept 2026, 13:01 | 584 | -6 |
| 31 Aug 2026, 14:57 | 590 | +6 |
| 25 Aug 2026, 01:16 | 584 | -1 |
| 17 Aug 2026, 16:18 | 585 | -6 |
| 9 Aug 2026, 14:14 | 591 | no change |
| 8 Aug 2026, 21:30 | 591 | first reading |
20 posts held, back to 2 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 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 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
12 reactions across 3 posts, in 6 distinct kinds. The most used accounts for 25.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 3 | 25.0% | |
| 😢 | 3 | 25.0% | |
| custom 5400364940231988000 | 2 | 16.7% | |
| ❤🔥 | 2 | 16.7% | |
| ⚡ | 1 | 8.33% | |
| 🤬 | 1 | 8.33% |
Custom emoji. One row above is a 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 count beside it is 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 3 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 12 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 2 August 2026 to 8 August 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.
🔥 MATCHDAY! Уже сегодня отправляемся в Аргун на выездной матч против «Вайнах Аргун»! ⚽️ Будет непросто, но мы готовы бороться за результат до финального свистка. 💪🏻 📍 Место: г. Аргун 🕟 Начало: 16:30 До встречи на поле! 🫡
🔥2
К сожалению, наше выступление в Кубке Ахмат подошло к концу. 0:3 Это поражение мы принимаем достойно. Спасибо всем, кто поддерживал команду, ваша поддержка очень многое значит для нас. Теперь полностью переключаемся на Высшую лигу Чеченской Республики. Впереди важные матчи, и все наши силы, внимание и настрой будут направлены именно туда. Работа продолжается. Мы еще обязательно скажем свое слово. 💚⚽
😢3❤🔥2custom 54003649402319880002⚡1
Финальный свисток Проигрываем и покидаем Кубок «Ахмат» ⚽️0️⃣➗3️⃣⚽️
69’| Тройная замена Дидаев М 🔄 Байбатыров Гациев 🔄 Исаев Хаджимурадов 🔄 Оздамиров ⚽️0️⃣➗3️⃣⚽️
61’| Еще одна замена Давлитгереев 🔄 Далиев ⚽️0️⃣➗3️⃣⚽️
60’| Третий мяч в наши ворота… ⚽️0️⃣➗3️⃣⚽️
🔥1🤬1
57’| Еще одна замена Алиев 🔄 Дидаев И ⚽️0️⃣➗2️⃣⚽️
55’| Вынужденная замена… Исраилов 🔄 Курумов ⚽️0️⃣➗2️⃣⚽️
48’| Пропускаем второй… ⚽️0️⃣➗2️⃣⚽️
46’| Второй тайм Надо забивать ЭСКАР🤜🤛 ⚽️0️⃣➗1️⃣⚽️
Перерыв Проигрываем после первого тайма с минимальным счетом ⚽️0️⃣➗1️⃣⚽️
43’| Не реализуем грубую ошибку обороны соперника… ⚽️0️⃣➗1️⃣⚽️
Showing the 12 most recent of 20 posts we hold for @MFC_ESKAR. 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.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“MFC ESKAR” (@MFC_ESKAR), 582 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/MFC_ESKAR.
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.