Telegram RegisterThe public register of Telegram
Telegram profile photo for Фокус Израиля: Тревоги | Цева Адом | Воздушная тревога | Ракетный обстрел

Channel

Фокус Израиля: Тревоги | Цева Адом | Воздушная тревога | Ракетный обстрел

@FocusRedAlert

On this record: Growth · Engagement · Posts · Citations · Cite this entry

588subscribers

-1 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002495725313
TypeChannel
Username@FocusRedAlert
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live22 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/FocusRedAlert

Growth

588589588.58 August 2026 — 589 subscribers8 August 2026 — 589 subscribers22 August 2026 — 588 subscribers8 August 202622 August 2026
3 measurements spanning 14 days, net -1. 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 588–589 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 13:56588-1
8 Aug 2026, 20:56589no change
8 Aug 2026, 06:47589first reading

Engagement

20 posts held, back to 27 June 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
28.6%
avg views ÷ 588 subscribers
Avg views / post
168
11 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
11
of 20 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 August 2026
Posts held20 (27 June 20266 August 2026)
Views total1,850
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 06:47 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.

Recent posts

6 Aug 2026, 20:59 UTC148 viewsread 8 August 2026

🇮🇱 Итоги тревог за 06/08/2026 📊 За минувшие сутки в Израиле было зафиксировано 1 сигнал тревоги. Из них: ⚠️ 1 проникновение террористов. 🕐 Первая тревога: Террористы в Кохав Яаков (Самария) в 08:41. 🏙 Города, где фиксировались срабатывания: ⚠️ Проникновение террористов 1. Кохав Яаков (Самария) — 1 2. Тель Цион (Самария) — 1 📣 Новости Израиля: @IsraelFocusNews 🚨 Канал тревог: @FocusRedAlert⁣​⁣

6 Aug 2026, 06:17 UTC112 viewsread 8 August 2026
Photo

⚠️ Срочное сообщение Командования тыла - Раннее предупреждение (06/08/2026 09:17) Затронутые районы: Самария 🇮🇱 Фокус Израиля: Тревоги⁣​⁣

6 Aug 2026, 05:41 UTC169 viewsread 8 August 2026
Photo

🇮🇱 Фокус Израиля: Тревоги⁣​⁣

6 Aug 2026, 05:41 UTC111 viewsread 8 August 2026

⚠️ Проникновение террористов (06/08/2026) 08:41: • Самария: Кохав Яаков, Тель Цион 🇮🇱 Фокус Израиля: Тревоги⁣​⁣

28 Jul 2026, 20:59 UTC176 viewsread 8 August 2026

🇮🇱 Итоги тревог за 28/07/2026 📊 За минувшие сутки в Израиле было зафиксировано 2 сигнала тревоги. Из них: 🚨 2 ракетных обстрела. 🕐 Первая тревога: Цева Адом в Кисуфим (Граница с Газой) в 05:24. 🏙 Города, где фиксировались срабатывания: 🚨 Цева Адом 1. Кисуфим (Граница с Газой) — 1 2. Нахаль Оз (Граница с Газой) — 1 📣 Новости Израиля: @IsraelFocusNews 🚨 Канал тревог: @FocusRedAlert⁣​⁣

28 Jul 2026, 19:06 UTC178 viewsread 8 August 2026
Photo

✅ Инцидент завершен (28/07/2026 22:06) Инцидент завершен в районах: Граница с Газой 🇮🇱 Фокус Израиля: Тревоги⁣​⁣

28 Jul 2026, 19:03 UTC171 viewsread 8 August 2026
Photo

🇮🇱 Фокус Израиля: Тревоги⁣​⁣

28 Jul 2026, 19:03 UTC171 viewsread 8 August 2026

🚨 Ракетная тревога (28/07/2026) 22:03: • Граница с Газой: Нахаль Оз (15 секунд) 🇮🇱 Фокус Израиля: Тревоги⁣​⁣

28 Jul 2026, 02:27 UTC202 viewsread 8 August 2026
Photo

✅ Инцидент завершен (28/07/2026 05:27) Инцидент завершен в районах: Граница с Газой 🇮🇱 Фокус Израиля: Тревоги⁣​⁣

28 Jul 2026, 02:24 UTC204 viewsread 8 August 2026
Photo

🇮🇱 Фокус Израиля: Тревоги⁣​⁣

28 Jul 2026, 02:24 UTC208 viewsread 8 August 2026

🚨 Ракетная тревога (28/07/2026) 05:24: • Граница с Газой: Кисуфим (15 секунд) 🇮🇱 Фокус Израиля: Тревоги⁣​⁣

20 Jul 2026, 20:59 UTC242 viewsread 8 August 2026

🇮🇱 Итоги тревог за 20/07/2026 📊 За минувшие сутки в Израиле было зафиксировано 1 сигнал тревоги. Из них: 🚨 1 ракетный обстрел. 🕐 Первая тревога: Цева Адом в Кфар Аза (Граница с Газой) в 02:59. 🏙 Города, где фиксировались срабатывания: 🚨 Цева Адом 1. Кфар Аза (Граница с Газой) — 1 2. Саад (Граница с Газой) — 1 📣 Новости Израиля: @IsraelFocusNews 🚨 Канал тревог: @FocusRedAlert⁣​⁣

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

Mentions

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

“Фокус Израиля: Тревоги | Цева Адом | Воздушная тревога | Ракетный обстрел” (@FocusRedAlert), 588 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/FocusRedAlert.

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.