Telegram RegisterThe public register of Telegram
Telegram profile photo for BesNaBese NEW

Channel

BesNaBese NEW

@highblitz

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

45subscribers

-1 since we began measuring on 7 August 2026

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

Register entry

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

Growth

454645.57 August 2026 — 46 subscribers10 August 2026 — 46 subscribers21 August 2026 — 45 subscribers7 August 202621 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 45–46 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Aug 2026, 12:4845-1
10 Aug 2026, 14:1546no change
7 Aug 2026, 11:1446first reading

Engagement

20 posts held, back to 29 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
74.6%
avg views ÷ 45 subscribers
Avg views / post
33.5
20 posts measured
Reaction rate
4.77%
reactions ÷ views · ER floor
Posts in window
20
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. It is computed over the 12 of 20 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 9 August 2026
Posts held20 (29 July 20269 August 2026)
Views total671
Reactions total20
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 14:15 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.

Reaction mix

20 reactions across 12 posts, in 4 distinct kinds. The most used accounts for 55.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 61925281499604626701155.0%
custom 5244616893364454693735.0%
15.00%
👍15.00%

Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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

Measured over the 20 most recent posts we hold, published 29 July 2026 to 9 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

9 Aug 2026, 15:05 UTC18 views1 reactionsread 10 August 2026

Чат, привет. Интернета почему-то нет Кто играет екап - всем удачи!

1

8 Aug 2026, 17:27 UTC20 viewsread 10 August 2026

Сыграл тренировочный микротурик не отобрался но игрой доволен, учитывая что не знаю абузы и много делал микроошибок Точный рез говорить не буду кто знает тот знает

8 Aug 2026, 12:56 UTC24 viewsread 10 August 2026

Ку Хочу высказаться по паре вещей Первое - снова сваливаю в отпуск скоро, так что стримов до сентября снова не ждите, увы Второе - стрим после микротурика Третье - на этом бездарнейшем микротурнире сделано бездарнейшее ограничение на стримы - 2,5 минуты задержка Четвертое - постараюсь абы как сыграть опенквалу на бобиса 19 августа, телефон у меня благо позволит. Ссылку на регу закину в @jeefhs Пятое - сделаю отдельну

5 Aug 2026, 13:29 UTC33 views4 reactionsread 10 August 2026

НАША ПОБЕДА

custom 52446168933644546934

5 Aug 2026, 13:29 UTC29 views2 reactionsread 10 August 2026
Forwarded from @ecupproPhoto

Голосование за игрока Июля завершено! 💃 Поздравляем! Игрок месяца ECUP.PRO - WeK1ngHS В этой ожесточённой борьбе за звание игрока месяца ему удалось победить с преимуществом в 2 голоса Для нас важно, чтобы участники ECUP.PRO становились заметными внутри комьюнити Спасибо всем, кто поддерживал игроков 🥰

custom 61925281499604626702

4 Aug 2026, 16:36 UTC35 viewsread 10 August 2026

ПОГНАЛИ НОВОЕ МИКРО НОВЫЕ НАУШНИКИ НОВЫЙ СЕЗОН HEARTHSTONE BATTLEGROUNDS (кину сюда оповещалку когда обнова) 📱 twitch.tv/BesNaBese_

4 Aug 2026, 15:30 UTC30 viewsread 10 August 2026

Стрим в 19:30 анпак нового оборудования

3 Aug 2026, 18:44 UTC32 views2 reactionsread 10 August 2026

ку, стрима ночью не будет. Завтра новый сезон запущу гринд

custom 52446168933644546932

3 Aug 2026, 12:46 UTC34 viewsread 10 August 2026

https://youtube.com/shorts/nEMn4m1lV84 Типичный житель Воронежа

2 Aug 2026, 14:58 UTC28 views2 reactionsread 10 August 2026

стрим ночью ща чет пизда как впадлу врубать twitch.tv/just_svyat оф каст турика тут

custom 52446168933644546931custom 61925281499604626701

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

Republishes

Channels on the register whose posts this channel has forwarded.

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

Names

Channels on the register whose handles appear in this channel's posts.

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

“BesNaBese NEW” (@highblitz), 45 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/highblitz.

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.