Telegram RegisterThe public register of Telegram

Channel

falcon

@falconintel

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

2,534subscribers

+73 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003931856466
TypeChannel
Username@falconintel
CreatedBetween 1 April 2026 and 30 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/falconintel

Growth

2,4612,5342,497.57 August 2026 — 2,461 subscribers7 August 2026 — 2,461 subscribers10 August 2026 — 2,534 subscribers7 August 202610 August 2026
3 measurements spanning 3 days, net +73. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 2,450–2,545 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 22:512,534+73
7 Aug 2026, 20:172,461no change
7 Aug 2026, 19:122,461first reading

Engagement

12 posts held, back to 30 July 2026the 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.

ERR · 30 days
92.9%
avg views ÷ 2,534 subscribers
Avg views / post
2,350
12 posts measured
Reaction rate
0.984%
reactions ÷ views · ER floor
Posts in window
12
of 12 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held12 (30 July 20267 August 2026)
Views total28,239
Reactions total278
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 20:17 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
2m 42s
Average length
23s

Measured directly from 7 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.

Reaction mix

278 reactions across 12 posts, in 19 distinct kinds. The most used accounts for 34.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥9534.2%
6222.3%
🤬3111.2%
😢176.12%
👎134.68%
🤮134.68%
👍124.32%
👏62.16%
🥰62.16%
👀41.44%
😱41.44%
🤣41.44%
🤡31.08%
💩20.719%
😡20.719%
🕊10.36%
🗿10.36%
😐10.36%
🤩10.36%

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 12 of the 12 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 278reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 30 July 2026 to 7 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.

Recent posts

7 Aug 2026, 15:56 UTC429 views11 reactionsread 7 August 2026

💥A ship outside Novorossiysk, Russia has been targetted. ~ Smoke coming from the ship Update: Ship struck a second time 2 minutes ago Update: as of 19:40 Ukranian time, crew rescue in progress by small boat(s). Boat leaving

🔥91🥰1

4 Aug 2026, 23:25 UTC≈2,100 views29 reactionsread 7 August 2026
Video

📍The main targets were: Nova Poshta: Branch completely destroyed in Obolon. Rozetka: Major logistics warehouse destroyed in Brovary. Epicenter: One warehouse destroyed near the DVRZ metro area; another warehouse severely damaged or destroyed in Kalynivka. Regional Logistics: Logistics hubs and commercial warehouse facilities destroyed near Borshchahivka. 📹videos from some of the areas struck

🔥11😢83🤣3👏1🗿1🤬1🤮1

4 Aug 2026, 22:04 UTC≈2,900 views28 reactionsread 7 August 2026
Video

🇷🇺 Russia attacked Kyiv moments ago Weapons used: 🚀 Iskander-M & KN-23 🚀 Zircon ❗️ S-400 The use of Iskander-M with cluster warhead was also observed. Multiple targets struck on both the left and right bank of Kyiv. ❗ The attack is still ongoing, with atleast 10 jet powered drones heading towards the capital. 🇺🇸Air defense has not been used. Kyiv is out of PAC-3 interceptors.

🔥13🤬8😡2😢21👏1🤩1

2 Aug 2026, 18:45 UTC≈3,420 views41 reactionsread 7 August 2026
Photo

🔴🇺🇦Russia about 1+ hour ago took out Cherevkovka bridge in Sloviansk, Donetsk region ~ Likely that this is the first of a couple going to be taken out in the coming days ~ The battle for the city is getting closer and closer by the day ⚪48.838292, 37.627302

🤬169👍8🔥4😢2👎1😐1

31 Jul 2026, 23:50 UTC≈1,960 views28 reactionsread 7 August 2026
Video

🇺🇦Kyiv city, Ukraine was just under a large missile attack Defense: 🇺🇸1-2x Pac-3 missile used Attack: 🚌20-25x Iskander-M/Bastion-M/S-400 used 🛵?x Geran-3/4 📍Several targets were struck since Ukraine really lacks air defense missiles like the PAC-3 Patriot Update: 🚀2x Zircon hypersonic cruise missiles struck Kyiv again (03:20)

🔥124🤮4😢3🤡2👎1👏1🤬1

31 Jul 2026, 19:37 UTC≈3,270 views13 reactionsread 7 August 2026
Video

🇷🇺Russian air defense is working in Taganrog, Rostov region ~ Ballistic missile threat in Ukraine because of this

9😢2🤬1🤮1

31 Jul 2026, 18:30 UTC≈1,670 views24 reactionsread 7 August 2026
Photo

🇺🇦Ukranian FPV drone has apperently managed to reach a S-300V(M) system in Luhansk region. ~ A S-300V(M) system recieved more missiles not long ago ~ Russian 9S36M Radar for the BUK-M3 was also moved into the same area 🎥Photos are mine The source of the FPV strike: kriegsforscherD on Twitter

15👍3🔥3🤮3

30 Jul 2026, 18:55 UTC≈1,530 views23 reactionsread 7 August 2026
Video

🇷🇺🔥Taman port continues to burn tonight

8🔥7👎5👏1🤣1🤬1

30 Jul 2026, 08:27 UTC≈1,850 views11 reactionsread 7 August 2026
Video

🇷🇺🚀Russian KH-101 cruise missile entered 🇵🇱Poland and struck a field near the village Targowisko. ~ Countermeasures were released before impact

🔥4🤬2🥰21🕊1🤡1

30 Jul 2026, 03:14 UTC≈4,390 views26 reactionsread 7 August 2026
Video

📹Video recorded in 🇵🇱Otrocz, Poland. It is unconfirmed if this is related to the missile(s) that entered Polish airspace. ~ This is also several kilometers inside Poland from the Ukranian border and where the missile(s) were first tracked.

🔥104👀4😱4🥰3🤬1

30 Jul 2026, 03:10 UTC≈2,250 views19 reactionsread 7 August 2026

📍The target was Lviv Danylo Halytskyi Airport and the aviation plant. ~ several people have been wounded

🔥5🤮43👎2👏2💩2👍1

30 Jul 2026, 02:15 UTC≈2,470 views25 reactionsread 7 August 2026
Photo

🔥🇷🇺Taman port, Krasnodar krai region, Russia burning in the morning hours. ~ A large scale 🇺🇦 FP-1/2 attack occured on the port/depot during the night

🔥174👎4

Showing the 12 most recent of 12 posts we hold for @falconintel. 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

Citation-graph rank — 544 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.

Forward network

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.

Mentions

Named by 2 registered channels — 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.

Cite this entry

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 10 August 2026 — this entry's latest reading, not the date you are reading this.

“falcon” (@falconintel), 2,534 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/falconintel.

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.