Telegram RegisterThe public register of Telegram
Telegram profile photo for Zона приграничья🇷🇺

Channel

Zона приграничья🇷🇺

@glaZ_graniZa

On this record: Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry

21,032subscribers

-47 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002008347544
TypeChannel
Username@glaZ_graniZa
Description📸 Мониторинг БПЛА по Белгородской области. Прислать новость/заказать рекламу: @Zonapir_bot
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 August 2026
Measurements held11
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/glaZ_graniZa

Growth

21,03221,07921,055.57 August 2026 — 21,079 subscribers7 August 2026 — 21,079 subscribers7 August 2026 — 21,076 subscribers9 August 2026 — 21,071 subscribers10 August 2026 — 21,070 subscribers11 August 2026 — 21,067 subscribers12 August 2026 — 21,064 subscribers12 August 2026 — 21,051 subscribers14 August 2026 — 21,045 subscribers15 August 2026 — 21,037 subscribers17 August 2026 — 21,032 subscribers7 August 202617 August 2026
11 measurements spanning 10 days, net -47. 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 21,025–21,086 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 09:4821,032-5
15 Aug 2026, 20:0521,037-8
14 Aug 2026, 07:3621,045-6
12 Aug 2026, 23:3321,051-13
12 Aug 2026, 01:4321,064-3
11 Aug 2026, 05:0121,067-3
10 Aug 2026, 01:5121,070-1
9 Aug 2026, 00:5121,071-5
7 Aug 2026, 23:5521,076-3
7 Aug 2026, 12:4621,079no change
7 Aug 2026, 12:3321,079first reading

Engagement

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

ERR · 30 days
8.16%
avg views ÷ 21,032 subscribers
Avg views / post
1,720
76 posts measured
Reaction rate
0.327%
reactions ÷ views · ER floor
Posts in window
76
of 76 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 63 of 76 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 13 August 2026
Posts held76 (1 August 202613 August 2026)
Views total130,496
Reactions total356
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Aug 2026, 15:31 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
13,200
Videos
13,300
Links
982

Lifetime counters from Telegram’s own channel header, read 17 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 42s
Average length
37s

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

356 reactions across 63 posts, in 6 distinct kinds. The most used accounts for 43.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏15343.0%
🤬13036.5%
😢5114.3%
😭123.37%
😱92.53%
🤯10.281%

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

Measured over the 76 most recent posts we hold, published 1 August 2026 to 13 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.

Advertising

Ad load
1.32%
1 of 76 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
1,480
over 1 measured post
Median views · rest
1,590
over 75 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2VtzqwzsZnK110 August 202610 August 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 76 most recent posts we hold, published 1 August 2026 to 13 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

13 Aug 2026, 19:12 UTC≈1,540 views5 reactionsread 17 August 2026

⚡️ В течение дня в период с 8.00 мск до 20.00 мск дежурными средствами ПВО перехвачены и уничтожены 193 украинских беспилотных летательных аппарата самолетного типа над территориями Белгородской, Брянской, Курской, Орловской, Калужской, Тульской областей, Московского региона, Краснодарского края, Республики Башкортостан, Республики Крым и над акваториями Азовского и Черного морей.

🙏4🤬1

13 Aug 2026, 13:19 UTC≈1,690 views3 reactionsread 17 August 2026

⚡️Беспилотники ВСУ продолжают атаки на нашу область. Пострадали пять человек В посёлке Красная Яруга от детонации FPV-дрона трое мужчин получили осколочные ранения различных частей тела. Бригады скорой помощи транспортируют их в городскую больницу №2 г. Белгорода. В результате атаки второго дрона на автомобиль пострадали двое. У мужчины — осколочное ранение ягодичной области, у женщины — осколочное ранение плеча. По

🙏3

13 Aug 2026, 12:08 UTC≈1,400 views3 reactionsread 17 August 2026

⚡️Четыре муниципалитета подверглись атакам ВСУ. Один человек погиб, один получил ранения В Белгородском округе в селе Варваровка FPV-дрон ударил по частному дому. От полученных ранений мужчина скончался на месте. Выражаем соболезнования его родным и близким. В городе Грайворон дрон атаковал женщину, которая ехала на велосипеде. Пострадавшую в тяжёлом состоянии с травматической ампутацией кисти, множественными оскол

🙏2😢1

13 Aug 2026, 09:48 UTC≈1,050 views1 reactionsread 17 August 2026

Внимание, отбой! По всем ранее объявленным тревогам.

🙏1

13 Aug 2026, 09:47 UTC≈2,300 views1 reactionsread 17 August 2026

Внимание Маслова, пристань, Бургерное заправки. Кольцо срочно всем в укрытие выйти из машин.

🙏1

13 Aug 2026, 09:47 UTC957 views1 reactionsread 17 August 2026

Внимание Маслова, Пристань в вашем направлении летит ударный дрон. Займите безопасны места.

🙏1

13 Aug 2026, 09:46 UTC933 views1 reactionsread 17 August 2026

❗️РФ передала Украине 261 тело погибших солдат ВСУ. Взамен России возвращены 24 тела погибших военных, сообщил военкор Александр Коц.

🙏1

13 Aug 2026, 09:46 UTC949 viewsread 17 August 2026

Внимание от двадцать шестого километра до Масловой пристани Дрон контролирует трассу, будет искать цель для атаки. Остановите движение. Заметьте безопасные места.

13 Aug 2026, 09:45 UTC893 viewsread 17 August 2026

Внимание, Ржавец Маслова, пристань. ТэБойл "Белнефть" Роснефть "Займите укрытие в вашем направлении летит ударный дрон".

13 Aug 2026, 08:43 UTC902 viewsread 17 August 2026

⚡️ В течение прошедшей ночи с 20.00 мск 12 августа до 8.00 мск 13 августа дежурными средствами ПВО перехвачены и уничтожены 362 украинских беспилотных летательных аппарата самолетного типа над территориями Белгородской, Брянской, Воронежской, Калужской, Курской, Оренбургской, Орловской, Пензенской, Ростовской, Рязанской, Самарской, Тульской, Ульяновской областей, Московского региона, Республики Башкортостан, Республи

13 Aug 2026, 08:34 UTC787 viewsread 17 August 2026
Photo

⚡️Во время атак ВСУ пострадали два мирных жителя В Ракитянском округе в селе Трефиловка дрон атаковал грузовой автомобиль. Мужчину в тяжёлом состоянии с осколочным ранением живота доставили в Борисовскую ЦРБ. Для продолжения лечения он переведён в городскую больницу №2 г. Белгорода. Транспорт повреждён. В городе Шебекино FPV-дрон ударил по машине. Пострадавшего доставили в Шебекинскую ЦРБ, где у мужчины диагностиро

13 Aug 2026, 08:12 UTC675 viewsread 17 August 2026

⚡️В городе Шебекино дрон ВСУ нанёс удар по автомобилю Двоих мужчин с осколочными ранениями доставили в Шебекинскую ЦРБ. После оказания помощи они будут переведены в областную клиническую больницу. Транспортное средство повреждено, —оперштаб.

Showing the 12 most recent of 76 posts we hold for @glaZ_graniZa. 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 — 348,415 of 1,480,975entries 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

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.

Mentions

Named by 1 registered channel — 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.

Appears in Telegram’s recommendations for other channels

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.

ПОГРАНИЧНИК ИЗ АДА
@pograni4nik_iz_ada · 105,145
Telegram ranks this channel #24 of 80 here — alongside 79 others — read 15 August 2026
Чё в Белгороде?
@belgorod_granica · 180,303
Telegram ranks this channel #25 of 70 here — alongside 69 others — read 14 August 2026
Радар Белгород
@radarb31 · 138,950
Telegram ranks this channel #32 of 79 here — alongside 78 others — read 13 August 2026
БЕЛГОРОДЕЦ
@belgorodecRU · 92,888
Telegram ranks this channel #37 of 57 here — alongside 56 others — read 16 August 2026
Грохот Приграничья🇷🇺
@grohot_pgr · 117,167
Telegram ranks this channel #42 of 77 here — alongside 76 others — read 14 August 2026
Блэтгород
@bletgorod · 106,566
Telegram ranks this channel #43 of 81 here — alongside 80 others — read 15 August 2026
Белгород №1
@belgorod01 · 192,340
Telegram ranks this channel #45 of 84 here — alongside 83 others — read 11 August 2026
Жесть Белгород
@zhest_belgorod · 594,409
Telegram ranks this channel #52 of 75 here — alongside 74 others — read 8 August 2026

This channel appears in 8 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Zона приграничья🇷🇺” (@glaZ_graniZa), 21,032 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/glaZ_graniZa.

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.