Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝔽𝕒𝕝𝕔𝕠𝕟 𝕚𝕟𝕤𝕚𝕘𝕙𝕥 ᵐᵃᵖ 🦅

Channel

𝔽𝕒𝕝𝕔𝕠𝕟 𝕚𝕟𝕤𝕚𝕘𝕙𝕥 ᵐᵃᵖ 🦅

@Falconins

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

6,362subscribers

+709 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001964684685
TypeChannel
Username@Falconins
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live8 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 8 November 2026
On Telegramt.me/Falconins

Topic

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Views per post sit far above this size band

8,390 average views per post against 6,299 subscribers — an engagement rate of 133.2%. Across the 1,118 registered channels in the same cohort — 3,470–9,998 subscribers, posting mainly in Ukrainian — the middle half sit between 12.8% and 36.4%, with a median of 22.1%.

What this was computed from
Window30 days (6 October 2026 – 5 November 2026)
Posts measured24 of 24 published in the window (1 exact, 23 rounded by Telegram)
Views totalled201,416
Mature posts only190.4% over 16 posts read at least 24h after publication
Subscribers6,299 measured 4 November 2026
Cohortb3162:ukr · 1,118 channels · p10 7.20% · p25 12.8% · p50 22.1% · p75 36.4% · p90 55.0%
Position in cohort99.015th percentile · 6.0× the cohort median
Uncertainty±0.151% of the figure, from Telegram’s rounding
Post languageUkrainian · 82.6% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_high, last confirmed 5 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

5,6456,3626,003.56 August 2026 — 5,653 subscribers7 August 2026 — 5,645 subscribers10 August 2026 — 5,828 subscribers12 August 2026 — 5,849 subscribers16 August 2026 — 5,853 subscribers22 August 2026 — 5,881 subscribers25 August 2026 — 5,903 subscribers28 August 2026 — 5,902 subscribers31 August 2026 — 5,966 subscribers3 September 2026 — 6,008 subscribers9 September 2026 — 6,032 subscribers13 September 2026 — 6,025 subscribers17 September 2026 — 6,056 subscribers25 September 2026 — 6,070 subscribers4 October 2026 — 6,126 subscribers11 October 2026 — 6,211 subscribers14 October 2026 — 6,200 subscribers18 October 2026 — 6,197 subscribers20 October 2026 — 6,240 subscribers23 October 2026 — 6,243 subscribers26 October 2026 — 6,269 subscribers29 October 2026 — 6,266 subscribers1 November 2026 — 6,263 subscribers4 November 2026 — 6,299 subscribers8 November 2026 — 6,362 subscribers6 August 20268 November 2026
25 measurements spanning 94 days, net +709. 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 5,537–6,470 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 25
Measured (UTC)SubscribersChange
8 Nov 2026, 10:066,362+63
4 Nov 2026, 19:266,299+36
1 Nov 2026, 20:216,263-3
29 Oct 2026, 13:486,266-3
26 Oct 2026, 05:156,269+26
23 Oct 2026, 14:276,243+3
20 Oct 2026, 18:516,240+43
18 Oct 2026, 00:346,197-3
14 Oct 2026, 15:176,200-11
11 Oct 2026, 01:006,211+85
4 Oct 2026, 18:576,126+56
25 Sept 2026, 00:186,070+14
17 Sept 2026, 05:426,056+31
13 Sept 2026, 03:396,025-7
9 Sept 2026, 03:546,032+24
3 Sept 2026, 16:586,008+42
31 Aug 2026, 11:185,966+64
28 Aug 2026, 14:545,902-1
25 Aug 2026, 09:185,903+22
22 Aug 2026, 14:485,881first reading

Engagement

103 posts held, back to 5 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 14 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
111.9%
avg views ÷ 6,362 subscribers
Avg views / post
7,120
30 posts measured
Reaction rate
0.65%
reactions ÷ views · ER floor
Posts in window
30
of 103 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 6 November 2026
Posts held103 (5 August 2026 – 6 November 2026)
Views total213,490
Reactions total1,388
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 13:56 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
12m 13s
Average length
1m 01s

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

4,408 reactions across 94 posts, in 29 distinct kinds. The most used accounts for 62.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2,75862.6%
👍67615.3%
👀1753.97%
❤1743.95%
😁1262.86%
💯942.13%
🤣821.86%
😢671.52%
😡420.953%
🫡360.817%
⚡320.726%
🤔260.59%
🤷‍♂260.59%
🤬120.272%
🏆110.25%
🤩100.227%
🎉90.204%
👏70.159%
✍60.136%
🤓60.136%
9 further kinds330.749%

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

Measured over the 103 most recent posts we hold, published 5 August 2026 to 6 November 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

Telegram’s own ‘edited’ marker: 0 of 30 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

6 Nov 2026, 00:05 UTC≈1,160 views42 reactionsread 6 November 2026
Photo

Схема-візуалізація (хронологія): Присутність українських БпЛА у повітряному просторі країни-агресора та окупованих регіонів України (станом на 06.11.2026, 01:55)

🔥31👀5👍5❤1

5 Nov 2026, 22:40 UTC≈1,280 views41 reactionsread 6 November 2026
Photo

Схема-візуалізація (хронологія): Присутність українських БпЛА у повітряному просторі країни-агресора та окупованих регіонів України (станом на 06.11.2026, 00:30) UPD: 19:00 05.11

🤔19🔥14❤4👀4

5 Nov 2026, 03:41 UTC≈1,660 views66 reactionsread 6 November 2026
Photo

Рязань, Рязанська область, рф. Рязанський НПЗ. Попередні напрямки з точки зору та можливі локації займання.

🔥66

5 Nov 2026, 02:25 UTC≈1,590 views44 reactionsread 6 November 2026

У нас в Рязани - грибы с глазами: их едят, они глядят!

😁33💯5🤣5🫡1

5 Nov 2026, 02:22 UTC≈1,500 views59 reactionsread 6 November 2026
Photo

Рязань, Рязанська область, рф. Атака на Рязанський нафтопереробний завод РОV: 54°37'53.46"N 39°46'38.18"E

🔥46👍6❤4🫡2🥱1

5 Nov 2026, 01:40 UTC≈1,550 views35 reactionsread 6 November 2026
Photo

Схема-візуалізація (хронологія): Присутність українських БпЛА у повітряному просторі країни-агресора та окупованих регіонів України (станом на 05.11.2026, 03:30)

🔥32👍3

4 Nov 2026, 21:52 UTC≈1,800 views41 reactionsread 6 November 2026
Photo

Схема-візуалізація (хронологія): Присутність українських БпЛА у повітряному просторі країни-агресора та окупованих регіонів України (станом на 04.11.2026, 23:40) UPD: 19:30

👍22🔥14❤5

4 Nov 2026, 20:28 UTC≈1,470 views26 reactionsread 6 November 2026

Трохи контексту - башта «IQ-квартал» це багаторівневий комплекс (42-поверхова вежа ) її ще називають «Башня министерств» або "Башня номер 1", у діловому центрі «москва-Сіті» єдиний урядовий комплекс. Там дислокуються такі федеральні міністерства та відомства рф як: мінекономрозвитку, мінпромторг, мінцифри. Підпорядковані агентства та федеральні служби, росстандарт, росакредитація, ФАДН, федеральне казначейство та і…

👍22👀4

4 Nov 2026, 20:28 UTC≈1,530 views27 reactionsread 6 November 2026

Ця башта є одним з найбільш захищених місць в рф, хибну тривогу, помилку тощо можна виключати (підвищений контроль силових структур). ФеСеО: Забезпечує фізичну безпеку, контррозвідувальний режим та охорону посадових осіб комплексу. Захист від кіберзагрози та витоків: У будівлі діють суворі протоколи технічного захисту інформації (захист від радіоелектронного перехоплення, прослуховування та витоку даних). А після ата…

👍16👀9❤2

4 Nov 2026, 20:28 UTC≈1,670 views49 reactionsread 6 November 2026
Photo

Тож що це було? Напрямок і вектор руху атаки по заводу «Протон» у м. Орел міг "випадково" збігтися з вежею «IQ-квартал», також він збігається з маршрутом високої інтенсивності українських БпЛА. Можливо, саме в цей момент весь повітряний коридор від кордону України до центру москви не був захищений. Це непрямі свідчення нездатності захистити найзахищеніше місце в центрі москви...

👍34👀11💯3🥴1

4 Nov 2026, 20:28 UTC≈1,520 views27 reactionsread 6 November 2026
Photo

Пам'ятаєте випадок із шорохом у башті «IQ-квартал» у діловому центрі «москва-Сіті»? Двіж збігся з ударом по заводу «Протон» у м. Орел, собянін звітував у той час про 17 збитих БпЛА від загальної кількості збитих у денний час (87), враховуючи всі регіони. Кількість невелика, але московська ППО тоді спрацювала майже одночасно в 5 локаціях у безпосередній близькості до москви. По колу в південній, південно-східній, схід…

👍20🔥6❤1

4 Nov 2026, 18:02 UTC≈1,480 views19 reactionsread 6 November 2026

Протягом дня з 09:00 до 19:00 черговими силами ППО знищено 46 українських БпЛА над територіями Бєлгородської, Брянської, Курської, Самарської, Саратовської, Свердловської, Тюменської, Ульяновської областей, московського регіону, Пермського краю, Республіки Башкортостан, Республіки Крим та Республіки Татарстан - міноборони рф

😁14👀4👍1

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

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 8 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.

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

“𝔽𝕒𝕝𝕔𝕠𝕟 𝕚𝕟𝕤𝕚𝕘𝕙𝕥 ᵐᵃᵖ 🦅” (@Falconins), 6,362 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/Falconins.

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.