🕖 Сегодня встретимся против 🇺🇦 NAVI в матче за выход в плей-офф мажора в Кёльне со счётом 2:1! Соперник очень трудный, команде предстоит огненный матч сегодня. 🦅 — Поддержим курагу & co!
❤7custom 52066856964163250313🔥2

Channel
@FalconsFamily
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
413subscribers
-8 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002221985710 |
|---|---|
| Type | Channel |
| Username | @FalconsFamily |
| 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 | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/FalconsFamily |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 06:23 | 413 | -8 |
| 8 Aug 2026, 05:31 | 421 | no change |
| 7 Aug 2026, 14:08 | 421 | first reading |
18 posts held, back to 24 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 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 18 posts for this entry, the most recent from 14 June 2026. An engagement rate over an empty window would be a number about nothing.
65 reactions across 13 posts, in 12 distinct kinds. The most used accounts for 36.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 24 | 36.9% | |
| custom 5206685696416325031 | 13 | 20.0% | |
| custom 5334718589905699546 | 8 | 12.3% | |
| 🔥 | 4 | 6.15% | |
| 😐 | 4 | 6.15% | |
| custom 5235803564638505645 | 3 | 4.62% | |
| 😭 | 3 | 4.62% | |
| 👍 | 2 | 3.08% | |
| custom 5235962753306365095 | 1 | 1.54% | |
| custom 5276454420777827666 | 1 | 1.54% | |
| custom 5332316723934690144 | 1 | 1.54% | |
| 🏆 | 1 | 1.54% |
Custom emoji. 6 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 areTelegram’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 13 of the 18 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 65reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 24 May 2026 to 14 June 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.
🕖 Сегодня встретимся против 🇺🇦 NAVI в матче за выход в плей-офф мажора в Кёльне со счётом 2:1! Соперник очень трудный, команде предстоит огненный матч сегодня. 🦅 — Поддержим курагу & co!
❤7custom 52066856964163250313🔥2
Есть победа! Выходим в сетку 2:1 на Мажоре, остаёмся в одном матче от выхода в плей-офф!
😐2
1:1 Надо дожимать
1:0 Выигрываем пик оппонентов, надо закрывать в сухую!
🗺 Выбор карт на матч против ⚡️ Monte! Должна быть легкая победа, команда просто на голову ниже соколов по всем параметрам.
❤1custom 52066856964163250311custom 53347185899056995461
❗️ Стартуем меньше чем через полчаса!
🕖 Завтра в 14:30 «Соколы» встретятся с тир-2 работягами из ⚡️ Monte в сетке 1 — 1. Тут как будто Макс & компания должны переезжать просто на классе, если не будет завтра уверенной победы 2:0, я уже хз на что тут надеяться. ❤️ — Поддержим ребят!
custom 52066856964163250315❤2custom 52359627533063650951custom 52764544207778276661
🇸🇦 0:2 🇷🇺 Проигрываем матч против ББ, Бумыч прайм. Увидимся завтра в матче за выход на 2:1 по сетке Сори, у админа нет инета
Извините за мой французский, но как это можно было въебать? Проигрываем 🗺️ Nuke, дальше наш пик — 🗺️ Ancient. ⚡️ Falcons 0:1 BB ⚡️
😐2
🗺️ Мап-пик на матч против 🏴☠️ BB на ваших экранах! 🦅 — 2:0 для Соколов!
custom 52066856964163250313❤2custom 52358035646385056452
⏰ Через 15 минут стартуем!
🕖 Завтра у камина в 6 утра в 17:00 по Москве 🇷🇺 Илюха & co сыграют против команды легендарного Бумыча — ⚡️ BB Team за выход на 2 — 0 в групповой стадии Мажора! 🇸🇦 — Изи для Соколов!
custom 53347185899056995467🏆1custom 53323167239346901441
Showing the 12 most recent of 18 posts we hold for @FalconsFamily. 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.
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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“Falcons Family — reborn” (@FalconsFamily), 413 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/FalconsFamily.
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.