Channel
@FJTFootball
On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
1,174subscribers
-13 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001674817700 |
|---|---|
| Type | Channel |
| Username | @FJTFootball |
| Created | 29 January 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/FJTFootball |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 10:15 | 1,174 | -1 |
| 2 Sept 2026, 05:23 | 1,175 | +1 |
| 29 Aug 2026, 21:45 | 1,174 | -3 |
| 26 Aug 2026, 14:34 | 1,177 | -3 |
| 19 Aug 2026, 16:26 | 1,180 | -3 |
| 16 Aug 2026, 19:54 | 1,183 | -7 |
| 10 Aug 2026, 14:51 | 1,190 | +3 |
| 7 Aug 2026, 19:51 | 1,187 | no change |
| 7 Aug 2026, 07:15 | 1,187 | first reading |
20 posts held, back to 17 May 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 16 July 2026. An engagement rate over an empty window would be a number about nothing.
116 reactions across 15 posts, in 8 distinct kinds. The most used accounts for 79.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 92 | 79.3% | |
| 🤣 | 9 | 7.76% | |
| 🤯 | 5 | 4.31% | |
| 💯 | 4 | 3.45% | |
| 👏 | 2 | 1.72% | |
| 🔥 | 2 | 1.72% | |
| 💔 | 1 | 0.862% | |
| 🤝 | 1 | 0.862% |
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 15 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 116 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 17 May 2026 to 16 July 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.
БЛЯЯ, Аргентина в финале с Испанией. Тут даже говорить не о чем. Я просто буду расслаблено смотреть финал и получать удовольствие от матча. И совсем неважно кто победит, победит Барселона
❤8🤣2💯1
Signed Жорик Аспидов
Рафинья получил травму во втором же матче на чм. Звучит печально, Бразилец потихоньку становится хроником
🤯5💔1💯1
Signed Жорик Аспидов
ЛЕО ЛЕО ЛЕО. Лучший игрок во всем Млечном Пути даже в 38 показывает всем свой класс. Эх, сколько еще прекрасных моментов он мог принести Барселоне 😞
❤17
Signed Жорик Аспидов
Блеклый первый тайм от Франции, но Мбаппе есть Мбаппе. А Олисе просто БРАВО!
❤5👏1🔥1
Signed Жорик Аспидов
Пока Япония и Марокко обрадовали своей игрой. Я думаю в 1/4 будет много сюрпризов. Бразилия вообще не впечатлила, Нидерланды so so
❤5💯1
Signed Жорик Аспидов
Сегодня первый матч Чемпионата Мира. Напишите какую сборную будете поддерживать на мундиале
Signed Жорик Аспидов
Особо инфоповодов нет. Перес выиграл выборы, ожидаемо. А Агкацевым интересуется Юве. Интересно было бы посмотреть за еще одним нашим парнем в Европе, так еще и осетином
❤5💯1🔥1
Signed Жорик Аспидов
Не скажу, что я прям жестко болел за ПСЖ, но в этом матче да. Мотя двухкратный, 2 подряд, и в этот раз в основе. БРАВО!
❤7🤣1
Signed Жорик Аспидов
Очень потный матч. Хочется серию пенальти глянуть
Signed Жорик Аспидов
🔴 ПРЯМАЯ ТРАНСЛЯЦИЯ В Telegram 🏆 ПСЖ — Арсенал Смотри бесплатно прямо в боте 👇 https://t.me/SportLiveRuBot?start=Jor3005
Signed Жорик Аспидов
А вот и составы на самый главный матч клубного футбола этого года. За кого будете болеть?
Signed Жорик Аспидов
Слот уволен из Ливерпуля ✅ Чудаки еще те, Алонсо просрали. Я думаю, что возьмут Ираолу или Гласнера. Хотя влажная мечта это Хави, но вероятность этого 1 процент
Signed Жорик Аспидов
Showing the 12 most recent of 20 posts we hold for @FJTFootball. 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.
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.
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.
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.
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“Три Бездаря | FJT” (@FJTFootball), 1,174 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/FJTFootball.
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.