Channel
@idfofficial
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Referenced elsewhere · Cite this entry
160,804subscribers
-3,548 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1001341028511 |
|---|---|
| Type | Channel |
| Username | @idfofficial |
| Description | Official Telegram channel of the Israel Defense Forces - Real time security updates and IDF announcements | www.idf.il/en |
| Created | 12 August 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/idfofficial |
National news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 96% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 05:18 | 160,804 | -120 |
| 15 Sept 2026, 04:39 | 160,924 | -141 |
| 13 Sept 2026, 10:21 | 161,065 | -132 |
| 11 Sept 2026, 17:21 | 161,197 | -183 |
| 9 Sept 2026, 03:21 | 161,380 | -237 |
| 5 Sept 2026, 20:15 | 161,617 | -130 |
| 3 Sept 2026, 20:36 | 161,747 | -111 |
| 2 Sept 2026, 10:48 | 161,858 | -83 |
| 1 Sept 2026, 09:46 | 161,941 | -93 |
| 31 Aug 2026, 07:43 | 162,034 | -60 |
| 30 Aug 2026, 10:26 | 162,094 | -114 |
| 29 Aug 2026, 09:34 | 162,208 | -76 |
| 28 Aug 2026, 11:46 | 162,284 | -71 |
| 27 Aug 2026, 13:46 | 162,355 | -68 |
| 26 Aug 2026, 11:53 | 162,423 | -78 |
| 25 Aug 2026, 14:24 | 162,501 | -93 |
| 24 Aug 2026, 13:05 | 162,594 | -183 |
| 23 Aug 2026, 00:14 | 162,777 | -99 |
| 21 Aug 2026, 12:27 | 162,876 | -80 |
| 20 Aug 2026, 15:11 | 162,956 | first reading |
236 posts held, back to 31 July 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 96 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 21 September 2026 |
|---|---|
| Posts held | 236 (31 July 2026 – 21 September 2026) |
| Views total | 1,149,050 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 21 Sept 2026, 19:55 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.
Lifetime counters from Telegram’s own channel header, read 21 September 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.
Measured directly from 2 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.
IDF: Today (Monday), during routine activity by IDF troops in the Yellow Line area, an IDF engineering vehicle drove over an explosive device. No IDF injuries were reported. This constitutes a blatant violation of the ceasefire agreement by the Hamas terrorist organization. In response, the IDF struck Hamas infrastructure that was used by the terrorist organization to advance attacks against Israeli civilians and I…
IDF: Following the siren that sounded a short while ago in the area of Malkia , it was determined to be a false identification.
IDF: Initial report - Sirens sound in the area of Malkia. The details are under review.
IDF: The IDF Chief of the General Staff at the scene of the shooting attack in the Neve Tzuf area: “The IDF is on high alert, deployed and prepared with soldiers reinforced across all sectors, including throughout the fast. Our mission is clear and ongoing—to thwart terrorism, act decisively against every threat, and protect the citizens of the State of Israel.” The IDF Chief of the General Staff, LTG Eyal Zamir, ar…
Joint IDF and ISA announcement: The IDF and ISA eliminated two terrorists who infiltrated Israel on October 7th and a Nukhba commander Yesterday (Saturday), the IDF and ISA struck and eliminated Yahya Hamdouna, a terrorist in Hamas’ military wing. The terrorist infiltrated Israeli territory during the October 7th Massacre. In additional strikes over the weekend, the IDF and ISA eliminated two additional Hamas ter…
IDF: Following a joint pursuit by security forces and ISA guidance, IDF soldiers apprehended the terrorist who carried out the shooting attack in Neve Tzuf area. Minutes after the shooting, a soldier who was operating near the scene arrived at the location and fired at the terrorist. As a result, the terrorist was injured and fled the scene. IDF soldiers apprehended the terrorist after he fled to a hospital near th…
IDF: A short while ago, IDF soldiers eliminated a terrorist who attempted to carry out a ramming attack against IDF soldiers operating in the Ganim area. No IDF injuries were reported.
IDF: Following a report that was received of a shooting attack in the Neve Tzuf area, numerous IDF soldiers were dispatched to the area and launched a pursuit after the terrorist. The soldiers are establishing roadblocks in the area.
IDF: Initial report - A report was received regarding a shooting near the area of Neveh Tzuf, the details are under review. IDF soldiers have been dispatched to the area.
IDF: The IDF eliminated a Hamas commander who infiltrated Israeli territory during the October 7th Massacre Two days ago (Thursday), the IDF struck in the Khan Younis area and eliminated Muhammad Suleiman Byouk, a commander in the military wing of the Hamas terrorist organization. The terrorist infiltrated Israeli territory during the October 7th Massacre. Throughout the war, including recently, the terrorist opera…
IDF: In response to an explosive device detonating in the Security Zone: The IDF struck Hezbollah infrastructure in southern Lebanon Earlier today (Saturday), an IDF engineering vehicle drove over an explosive device belonging to the Hezbollah terrorist organization in the Security Zone in southern Lebanon. As a result, two IDF soldiers were lightly injured and were evacuated to receive medical treatment. Their fam…
IDF: The IDF eliminated a Nukhba commander who infiltrated Israel during the October 7th Massacre and a commander in Hamas’ Naval Array Yesterday (Wednesday), the IDF struck in the Al-Bureij area and eliminated the terrorist Muhammad Jamal Ahmad Eid, a Nukhba commander in Hamas’ military wing. The terrorist infiltrated Israeli territory during the October 7th Massacre. In an additional strike two days ago (Tuesday)…
Showing the 12 most recent of 236 posts we hold for @idfofficial. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 16 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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 12 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 53 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.
Wikipedia
One Wikipedia article names this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.
Hacker News
This handle was named once in a Hacker News comment or story, via the public Algolia search API. HN comment and story text has no confirmed reuse licence, so nothing quoted from either is reproduced here — only that a mention exists, when, and by whom, with a link to read it at the source.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Israel Defense Forces” (@idfofficial), 160,804 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/idfofficial.
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.