Telegram RegisterThe public register of Telegram

Channel

ZОНА ПРАВДЫ

@ZONA_P

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

11,818subscribers

-15 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001873710302
TypeChannel
Username@ZONA_P
Descriptionhttps://gosuslugi.ru/snet/67adae323c3e6d7843a973a5 № 5038929422 История про жизнь там… про воинов и про мирных, про проблемы и помощь, про хорошее и к сожалению плохое, одним словом про жизнь, и конечно же про помощь. Мы сила когда мы вместе.
Created19 February 2023measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held7
Confirmed unchanged2 times, most recently 12 August 2026
On Telegramt.me/ZONA_P

Growth

11,81811,83611,8275 August 2026 — 11,833 subscribers6 August 2026 — 11,833 subscribers6 August 2026 — 11,836 subscribers7 August 2026 — 11,835 subscribers9 August 2026 — 11,826 subscribers10 August 2026 — 11,820 subscribers11 August 2026 — 11,818 subscribers5 August 202611 August 2026
7 measurements spanning 6 days, net -15. 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 11,815–11,839 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 21:4311,818-2
10 Aug 2026, 18:2411,820-6
9 Aug 2026, 16:2111,826-9
7 Aug 2026, 16:0011,835-1
6 Aug 2026, 14:2011,836+3
6 Aug 2026, 02:3511,833no change
5 Aug 2026, 23:5011,833first reading

Engagement

23 posts held, back to 26 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 16 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
11.6%
avg views ÷ 11,818 subscribers
Avg views / post
1,370
23 posts measured
Reaction rate
0.864%
reactions ÷ views · ER floor
Posts in window
23
of 23 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 11 August 2026
Posts held23 (26 July 202611 August 2026)
Views total31,493
Reactions total272
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 03:52 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
5,700
Videos
9,820
Links
1,760

Lifetime counters from Telegram’s own channel header, read 13 August 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
3m 58s
Average length
48s

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

272 reactions across 23 posts, in 8 distinct kinds. The most used accounts for 62.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏16962.1%
🔥6122.4%
186.62%
👍176.25%
🤝31.10%
💯20.735%
🍾10.368%
👏10.368%

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

Measured over the 23 most recent posts we hold, published 26 July 2026 to 11 August 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

11 Aug 2026, 05:25 UTC705 views10 reactionsread 13 August 2026

⚡️Фронтовая сводка на утро 11.08.26⚡️ Запорожский фронт На Каменском направлении сообщается о боях в районе Павловки и к северу от Малых Щербаков. На Гуляйпольском направлении ВС РФ ведут бои в Долинке. Продолжаются столкновения в районе Зарницы. Донецкий фронт На Красноармейском направлении ВС РФ продвигаются южнее Новоподгороднего. Активные боевые действия идут в Матяшево и Красноподолье. Есть продвижение в стор

🙏82

10 Aug 2026, 06:19 UTC854 views6 reactionsread 13 August 2026

⚡️Фронтовая сводка на утро 10.08.26⚡️ Запорожский фронт На Каменском направлении продолжаются бои в Приморском и на подступах к Степногорску. На Гуляйпольском направлении идут ожесточённые боестолкновения в районе Новосёловки. Донецкий фронт На Добропольском направлении ВС РФ закрепились на позициях в Новом Донбассе и формируют плацдарм для дальнейшего наступления в сторону Доброполья. МО РФ сообщило об освобожден

🙏6

9 Aug 2026, 07:23 UTC914 views10 reactionsread 13 August 2026

⚡️Фронтовая сводка на утро 09.08.26⚡️ Запорожский фронт На Каменском направлении сохраняется сложная обстановка в Приморском, продолжаются боестолкновения. ВС РФ ведут бои в районе Степногорска и на южных окраинах Новояковлевки, расширяют зону контроля севернее Малых Щербаков. Появляются сведения о начале штурма Орехова. Войска РФ занимают новые рубежи в западной части Малой Токмачки. На Гуляйпольском направлении и

🙏8🔥2

8 Aug 2026, 09:38 UTC920 views5 reactionsread 13 August 2026

⚡️Фронтовая сводка на утро 08.08.26⚡️ Запорожский фронт На Каменском направлении сообщается о продвижении к Юрковке со стороны Малых Щербаков. На Гуляйпольском направлении об изменениях в ЛБС не сообщается. На Ореховском направлении ВС РФ продвигаются и занимают новые позиции на подступах к западной части Малой Токмачки. Появляются сведения об успехах в Новоданииловке. Донецкий фронт На Красноармейском направлении

🙏5

7 Aug 2026, 05:45 UTC≈1,030 views14 reactionsread 13 August 2026

⚡️Фронтовая сводка на утро 07.08.26⚡️ Запорожский фронт На Каменском направлении ВС РФ расширяют контроль территорий и продвигаются севернее Малых Щербаков. Сообщается об успехах в селе Павловка и восточнее, а также на южных окраинах Новояковлевки. На Гуляйпольском направлении войска РФ продвигаются в районе освобожденной накануне Зарницы. Продолжаются боестолкновения у Терноватого. Выше по фронту идут бои в районе

🙏93🔥2

5 Aug 2026, 07:04 UTC≈1,590 views33 reactionsread 13 August 2026

Наконец-то на пятый год войны наши взялись за логистику противника! Сегодня был нанесён самый массированный удар за всю историю конфликта, направленный именно на логистические терминалы, задействованные в цепочках поставок дронов и снаряжения. Похоже, с хирургическими операциями, гуманитарными соображениями и «там наши люди» покончено! Началась война без белых перчаток, как и должно было быть с самого начала! — В п

🔥20👍11💯2

5 Aug 2026, 06:58 UTC≈1,310 views7 reactionsread 13 August 2026

⚡️Фронтовая сводка на утро 05.08.26⚡️ Запорожский фронт На Каменском направлении ВС РФ отражают контратаки противника в районе Степногорска и Плавней. Ситуация остаётся напряжённой. На Гуляйпольском направлении ВС РФ занимают новые позиции на рубеже Новосёловка – Копани. Продолжаются бои на подступах и в черте населённого пункта Долинка. Сообщается о контратаках ВСУ в районах Воздвижевки, Староукраинки, Цветково и

🙏5👍2

4 Aug 2026, 05:55 UTC≈1,430 views5 reactionsread 13 August 2026

⚡️Фронтовая сводка на утро 04.08.26⚡️ Запорожский фронт На Каменском направлении продолжаются столкновения в районе Степногорска и Новояковлевки. На Гуляйпольском направлении идут бои за Долинку. Продолжаются боестолкновения в районе Терноватого. Донецкий фронт На Добропольском направлении ВС РФ продолжают сужать полукольцо вокруг Доброполья. Есть продвижение к южным и восточным окраинам города. Сообщается, что во

🙏5

3 Aug 2026, 05:49 UTC≈1,360 views11 reactionsread 13 August 2026

⚡️Фронтовая сводка на утро 03.08.26⚡️ Запорожский фронт На Каменском направлении об изменениях в ЛБС не сообщается. На Гуляйпольском направлении продолжается расширение плацдарма на восточном берегу реки Верхняя Терса. ВС РФ развивают наступление в сторону населенных пунктов Даниловка, Мировка, Новое Поле, Рыбальское и усиливают давление на позиции противника в районе Терноватого. Донецкий фронт На Добропольском н

🙏92

2 Aug 2026, 09:23 UTC≈1,340 views8 reactionsread 13 August 2026

⚡️Фронтовая сводка на утро 02.08.26⚡️ Запорожский фронт На Каменском направлении без изменений. На Гуляйпольском направлении МО РФ сообщило об освобождении населённого пункта Любицкое. Продолжатся бои в Терноватом. ВС РФ наступают в направлении Нового Поля и Рыбальского. Донецкий фронт На Добропольском направлении войска РФ ведут бои в районе населённых пунктов Рубежное, Степи, а также Новониколаевка и Новогригоро

🔥6🙏2

1 Aug 2026, 19:07 UTC≈1,340 views11 reactionsread 13 August 2026

⚡️Фронтовая сводка на утро 01.08.26⚡️ Запорожский фронт На Каменском направлении без изменений. На Гуляйпольском направлении идут бои в районе Долинки, а также у Терноватого. В Покровском районе есть продвижение у Благодатного. Донецкий фронт На Добропольском направлении ВС РФ расширяют зону контроля на подступах к городу Доброполье. Продолжается зачистка Белицкого и Водянского, идут бои в районе Красноярского (Че

🙏11

31 Jul 2026, 16:58 UTC≈1,410 views7 reactionsread 13 August 2026

⚡️Фронтовая сводка на утро 31.07.26⚡️ Запорожский фронт На Каменском направлении об изменении в ЛБС не сообщается. На Гуляйпольском направлении не стихают бои в районе Терноватого. Донецкий фронт На Добропольском направлении продолжается продвижение. МО РФ сообщило об освобождении Красноярского (Черниговки). ВС РФ закрепляются на занятых позициях и производят зачистку территории. На Константиновском направлении и

🙏7

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

Citation-graph rank

Citation-graph rank — 756,137 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

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

“ZОНА ПРАВДЫ” (@ZONA_P), 11,818 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/ZONA_P.

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.