Telegram RegisterThe public register of Telegram
Telegram profile photo for OSINTWarfare

Channel

OSINTWarfare

@OSINTWarfare

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

9,051subscribers

+3,066 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-1002620993796
TypeChannel
Username@OSINTWarfare
DescriptionOpen Source Intelligence • Tracking Real-Time News and Conflicts Across the World.
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live11 November 2026
Measurements held28
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/OSINTWarfare

Topic

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

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 2 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@OSINTWarfare/6252 · this entry11 Aug 2026, 15:02 UTC@intelslava/9242911 Aug 2026, 15:04 UTC1.0072 seconds
@OSINTWarfare/7820 · this entry2 Nov 2026, 14:24 UTC@intelslava/974272 Nov 2026, 19:25 UTC1.005.0 hours
@OSINTWarfare/7826 · this entry3 Nov 2026, 13:24 UTC@intelslava/974553 Nov 2026, 13:35 UTC1.0011 minutes
@intelslava/975365 Nov 2026, 10:26 UTC@OSINTWarfare/7868 · this entry5 Nov 2026, 10:26 UTC1.00under a minute
@The_Europe_Update/140204 Nov 2026, 17:19 UTC@OSINTWarfare/7857 · this entry4 Nov 2026, 17:30 UTC1.0012 minutes
@OSINTWarfare/7853 · this entry4 Nov 2026, 17:22 UTC@The_Europe_Update/140214 Nov 2026, 17:31 UTC1.0010 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@intelslava13 (8/8 hand-verifiable sample passed)1.0072 secondsthis entry (10–3)
@The_Europe_Update5 (5/5 hand-verifiable sample passed)1.0012 minutesthis entry (3–2)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 3 of the 3 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 148 comparable posts for this entry, running 4 August 2026 to 11 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the keys clone_mutual · clone_source, last confirmed 12 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,9859,0517,5186 August 2026 — 5,985 subscribers6 August 2026 — 5,985 subscribers6 August 2026 — 6,001 subscribers9 August 2026 — 6,018 subscribers12 August 2026 — 6,135 subscribers15 August 2026 — 6,162 subscribers18 August 2026 — 6,243 subscribers22 August 2026 — 6,287 subscribers25 August 2026 — 6,302 subscribers27 August 2026 — 6,409 subscribers30 August 2026 — 6,488 subscribers3 September 2026 — 6,717 subscribers8 September 2026 — 6,824 subscribers12 September 2026 — 7,045 subscribers16 September 2026 — 7,154 subscribers26 September 2026 — 7,576 subscribers5 October 2026 — 7,759 subscribers11 October 2026 — 8,045 subscribers14 October 2026 — 8,130 subscribers17 October 2026 — 8,213 subscribers21 October 2026 — 8,357 subscribers24 October 2026 — 8,467 subscribers26 October 2026 — 8,587 subscribers29 October 2026 — 8,709 subscribers1 November 2026 — 8,748 subscribers4 November 2026 — 8,888 subscribers8 November 2026 — 8,951 subscribers11 November 2026 — 9,051 subscribers6 August 202611 November 2026
28 measurements spanning 98 days, net +3,066. 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,525–9,511 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)SubscribersChange
11 Nov 2026, 22:169,051+100
8 Nov 2026, 04:218,951+63
4 Nov 2026, 16:398,888+140
1 Nov 2026, 16:108,748+39
29 Oct 2026, 21:368,709+122
26 Oct 2026, 16:518,587+120
24 Oct 2026, 00:398,467+110
21 Oct 2026, 09:568,357+144
17 Oct 2026, 22:178,213+83
14 Oct 2026, 23:108,130+85
11 Oct 2026, 23:378,045+286
5 Oct 2026, 02:007,759+183
26 Sept 2026, 00:397,576+422
16 Sept 2026, 23:397,154+109
12 Sept 2026, 15:017,045+221
8 Sept 2026, 11:586,824+107
3 Sept 2026, 00:436,717+229
30 Aug 2026, 12:566,488+79
27 Aug 2026, 18:236,409+107
25 Aug 2026, 03:256,302first reading

Engagement

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

ERR · 30 days
37.6%
avg views ÷ 9,051 subscribers
Avg views / post
3,410
121 posts measured
Reaction rate
0.459%
reactions ÷ views · ER floor
Posts in window
121
of 194 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. It is computed over the 120 of 121 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 November 2026
Posts held194 (4 August 2026 – 12 November 2026)
Views total412,280
Reactions total1,887
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Nov 2026, 00:35 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

Photos
≈3,130
Videos
≈3,570
Links
≈349

Lifetime counters from Telegram’s own channel header, read 13 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
1h 00m
Average length
44s

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

2,576 reactions across 178 posts, in 49 distinct kinds. The most used accounts for 30.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤78730.6%
🔥38214.8%
🤣2308.93%
👍2037.88%
🤬1305.05%
👎1104.27%
💩953.69%
👏863.34%
🤡722.80%
🤮682.64%
😁461.79%
🖕431.67%
❤‍🔥311.20%
🤯281.09%
🥰271.05%
👀250.97%
🫡190.738%
🏆170.66%
🤔130.505%
🍾120.466%
29 further kinds1525.90%

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

Measured over the 194 most recent posts we hold, published 4 August 2026 to 12 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: 2 of 121 posts held from the last 30 days (1.65%) 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).

12 Nov 2026, 21:47 UTC506 views3 reactionsread 13 November 2026
Video

🇺🇸🇮🇷⚡️ — Earlier, a U.S. drone, apparently a LUCAS one-way attack drone, was spotted flying along the Hormozgan coastline in southern Iran. Iranian forces attempted to shoot it down using small arms fire. @OSINTWarfare

❤3

12 Nov 2026, 21:38 UTC552 views9 reactionsread 13 November 2026

🇺🇸🇮🇷⚡️ — Reports of an explosion in Sirik, Hormozgan Province, southern Iran. @OSINTWarfare

👀5🔥3🤬1

12 Nov 2026, 21:31 UTC789 views14 reactionsread 13 November 2026
Video

🇮🇷⚡️ — Iran displayed its Kheibar Shekan ballistic missile during a nighttime gathering at Enghelab Square (Revolution Square) in Tehran. @OSINTWarfare

❤4👏4🤡3🫡3

12 Nov 2026, 20:05 UTC≈14,600 views10 reactionsread 13 November 2026
Video

🇮🇷🇺🇸🇮🇱⚡️ — IRIB has released footage showing an IRGC Aerospace Force missile unit operating during the latest war against Israel and the United States. The footage shows a missile launcher exploding, possibly as a result of an airstrike or an operational accident, while a successful ballistic missile launch is captured in the background.

🤔5❤2😱2🫡1

12 Nov 2026, 19:44 UTC≈4,550 views5 reactionsread 13 November 2026
Video

🇹🇷⚡️ — A Turkish Land Forces S-70A-series utility helicopter assigned to the 2nd Army Aviation Regiment in Malatya Province has crashed. All four military personnel on board were killed. @OSINTWarfare

🎉5

12 Nov 2026, 19:29 UTC792 views9 reactionsread 13 November 2026

🇮🇷⚡️ — Iran’s Assembly of Experts issued an unprecedented statement today, calling for consideration of a withdrawal from the Nuclear Non-Proliferation Treaty (NPT), a review of the country's defense doctrine, and the establishment of the necessary deterrence measures. The Assembly described these steps as an unavoidable necessity and a public and national demand, urging officials to heed this demand under the guida…

❤6👏3

12 Nov 2026, 12:02 UTC≈1,110 views11 reactionsread 13 November 2026
Photo

🇺🇸🇮🇶⚡️ — A U.S. Air Force (USAF) MQ-9A Reaper unmanned combat aerial vehicle (UCAV) was spotted flying over Baghdad, Iraq.

🤬9🔥2

12 Nov 2026, 10:13 UTC≈1,180 views14 reactionsread 13 November 2026

🇮🇷⚡️ — Reports of two ballistic missiles being launched from Nojeh Air Base in Hamadan Province, western Iran.

❤10🥰2👀1🥱1

12 Nov 2026, 09:49 UTC≈1,150 views10 reactionsread 13 November 2026
Video

🇸🇾⚡️ — Angry protesters in Raqqa blocked roads to stop oil tankers heading to Damascus and Turkey, setting tires on fire as residents protested oil exports while their own communities face shortages of diesel and fuel.

🔥8😢2

11 Nov 2026, 17:27 UTC≈1,560 views23 reactionsread 13 November 2026
Photo

This is the second Iranian stealth cruise missile, which I overlooked yesterday but was later pointed out to me by a friend. Anyway, it seems Iran is starting to take its cruise missile program more seriously, with an increasing focus on incorporating low-observable design features into its newer missiles. However, a more accurate technical assessment will require further information about the missile's radar cross…

❤20🤣3

11 Nov 2026, 16:58 UTC≈7,120 views7 reactionsread 13 November 2026
Photo

I've been asked this question several times and have already addressed it, but I've seen claims circulating that Iran used a Fattah-1 warhead mounted on a Kheibar Shekan booster, based solely on the fact that the boosters shown in the footage are unpainted. This claim is incorrect. The Fattah-1 and Kheibar Shekan share an identical booster design, or at the very least, one that is extremely similar. Unpainted booste…

❤7

11 Nov 2026, 12:12 UTC≈1,500 views10 reactionsread 13 November 2026
Video

🇩🇿⚡️ — The Algerian Ministry of National Defence has released new footage showing the Algerian Navy launching Chinese-made CM-302 (YJ-12B) supersonic anti-ship cruise missiles. @OSINTWarfare

👏9❤1

Showing the 12 most recent of 194 posts we hold for @OSINTWarfare. 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 12 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 11 November 2026 — this entry's latest reading, not the date you are reading this.

“OSINTWarfare” (@OSINTWarfare), 9,051 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/OSINTWarfare.

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.