Telegram RegisterThe public register of Telegram
Telegram profile photo for FIGHT or FLIGHT

Channel

FIGHT or FLIGHT

@Fight_or_Flight

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

346subscribers

-2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001078137208
TypeChannel
Username@Fight_or_Flight
Created18 April 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded8 August 2026
Last confirmed live7 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 7 October 2026
On Telegramt.me/Fight_or_Flight

Topic

National news — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 79% 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.

Growth

3463483477 August 2026 — 348 subscribers8 August 2026 — 348 subscribers6 September 2026 — 347 subscribers14 September 2026 — 346 subscribers27 September 2026 — 347 subscribers7 October 2026 — 346 subscribers7 August 20267 October 2026
6 measurements spanning 61 days, net -2. 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 346–348 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Oct 2026, 22:19346-1
27 Sept 2026, 11:41347+1
14 Sept 2026, 16:01346-1
6 Sept 2026, 10:00347-1
8 Aug 2026, 06:49348no change
7 Aug 2026, 19:50348first reading

Engagement

20 posts held, back to 26 December 2025 — 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 31 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
12m 02s
Average length
38s

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

26 reactions across 16 posts, in 10 distinct kinds. The most used accounts for 38.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1038.5%
❤‍🔥311.5%
😢311.5%
👏27.69%
🔥27.69%
🫡27.69%
👍13.85%
😁13.85%
😎13.85%
🥰13.85%

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 16 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 26 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 26 December 2025 to 31 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.

Recent posts

29 Jul 2026, 08:11 UTC96 views2 reactionsread 8 August 2026
Video

عقاب وطن به آشیانه بازگشت پرواز برای او مأموریت نبود؛ عهدی بود با ایران روابط عمومی ارتش: 🔹شهادت امیر سرتیپ دوم خلبان مجید کاظمی، یکی از خلبانان دلیر سوخو ۲۴ نیروی هوایی ارتش، احراز شد و پیکر مطهر این شهید والامقام، تا ساعاتی دیگر به آغوش میهن اسلامی، باز می‌گردد. 🔹این شهید عزیز خلبان یکی از جنگنده‌های سوخو ۲۴ ایرانی بود که در جریان حمله ۱۱ اسفند سال گذشته، خسارات سنگینی را به پایگاه العدید آمریکا در کشور قطر وا…

❤2

24 Jul 2026, 14:18 UTC120 viewsread 8 August 2026
Video

قاهر F-313؛ جنگنده یا پروژه تبلیغاتی؟ قاهر F-313 در سال ۱۳۹۱ توسط جمهوری اسلامی رونمایی و به‌عنوان یک جنگنده نسل پنجم رادارگریز معرفی شد. مقامات ایران مدعی بودند این هواپیما از فناوری‌های پیشرفته، سرعت بالا و توان حمل تسلیحات در محفظه داخلی برخوردار است. اما از همان ابتدا بسیاری از کارشناسان این ادعاها را زیر سؤال بردند. مهم‌ترین انتقادها عبارت بودند از: * کابین بسیار کوچک و غیرعملیاتی * موتور نامشخص و فاقد توان …

19 Jul 2026, 16:11 UTC102 views1 reactionsread 8 August 2026
Video

The classic J3 ©️ @fight_or_flight 〽️

😁1

15 Jul 2026, 14:33 UTC103 views1 reactionsread 8 August 2026
Video

نبرد هنوز تمام نشده بود... در ارتفاعی که هر تصمیم، مرز میان پیروزی و شهادت بود، عقاب‌های ایرانی لحظه‌ای میدان را خالی نکردند. دشمن با تمام توان برای فرار می‌کوشید، اما در آسمانی که پاسدارانش بیدار بودند، گریزی وجود نداشت. چند ثانیه بعد، قفل شکار کامل شد؛ موشک از دل فانتوم رها شد و با دقتی خیره‌کننده، میگ-۲۳ عراقی را در آسمان ایلام در هم کوبید. شعله‌های سقوط، تنها پایان یک جنگنده نبود؛ نشانه‌ای بود از برتری خلبانانی…

👏1

10 Jul 2026, 11:01 UTC101 views2 reactionsread 8 August 2026
Video

F-4D معروف به فانتوم دیزل ©️ @fight_or_flight 〽️

❤1🔥1

4 Jul 2026, 11:36 UTC164 views2 reactionsread 8 August 2026
Video

Boeing 787 ©️ @fight_or_flight 〽️

❤2

29 Jun 2026, 19:03 UTC184 views1 reactionsread 8 August 2026
Photo

چرا هنگام برخاست اف-۴ فانتوم از ناو، دماغه هواپیما بالا می‌آمد؟ در نسخه‌های ناونشین اف-۴ فانتوم، ارابه فرود جلویی به سامانه‌ای مجهز بود که پیش از پرتاب با منجنیق، چرخ جلو را حدود ۱ متر بلند می‌کرد. این کار باعث می‌شد دماغه هواپیما بالا آمده و زاویه حمله بال افزایش یابد. این ویژگی چند مزیت مهم داشت: تولید نیروی برا (Lift) بیشتر در لحظه ترک عرشه کاهش خطر واماندگی در سرعت پایین امکان برخاست با سوخت و مهمات بیشتر ک…

👍1

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

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

“FIGHT or FLIGHT” (@Fight_or_Flight), 346 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/Fight_or_Flight.

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.