Telegram RegisterThe public register of Telegram
Telegram profile photo for BRICK BAZUKA | 06.11.2026, Екатеринбург

Channel

BRICK BAZUKA | 06.11.2026, Екатеринбург

@brickbazukaekb

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

72subscribers

+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-1003164200952
TypeChannel
Username@brickbazukaekb
CreatedBetween 1 September 2025 and 30 November 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/brickbazukaekb

Growth

717271.57 August 2026 — 71 subscribers9 August 2026 — 71 subscribers15 August 2026 — 72 subscribers7 August 202615 August 2026
3 measurements spanning 7 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 71–72 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 03:1672+1
9 Aug 2026, 23:3171no change
7 Aug 2026, 18:1771first reading

Engagement

20 posts held, back to 27 January 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
73.6%
avg views ÷ 72 subscribers
Avg views / post
53.0
3 posts measured
Reaction rate
3.77%
reactions ÷ views · ER floor
Posts in window
3
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 28 July 2026
Posts held20 (27 January 202628 July 2026)
Views total159
Reactions total6
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 23: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

Video runtime
4m 33s
Average length
55s

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

53 reactions across 14 posts, in 6 distinct kinds. The most used accounts for 43.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2343.4%
2139.6%
👍59.43%
💋23.77%
💩11.89%
😭11.89%

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 14 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 53reactions 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 27 January 2026 to 28 July 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

28 Jul 2026, 12:01 UTC27 views1 reactionsread 9 August 2026
Forwarded from @brickbazukaDMTVideo

Brick Bazuka, Niker - едем по району Альбом XIII 🎧 смотреть 📺 YouTube VK

1

24 Jul 2026, 09:28 UTC64 views2 reactionsread 9 August 2026
Video

Впереди нас ждёт 🥩🥩🥩 Зови друзей, с которыми вы знаете каждый трек, и приходите вместе. Потому что на таком концерте гораздо круче, когда рядом свои 👊🏻 🔥 Купить билеты на сайте

🔥2

21 Jul 2026, 07:58 UTC68 views3 reactionsread 9 August 2026
Video

BRICK BAZUKA c сольным концертом в Екатеринбурге 🔥 Пора планировать, где вы проведёте один из самых громких вечеров этой осени. Вас ждёт мощное выступление, увидимся 6 ноября на площадке «Фабрика Ивент Холл». 🎫 Успейте приобрести билет на концерт

🔥2💋1

17 Jul 2026, 07:58 UTC72 views4 reactionsread 9 August 2026
Photo

🔤🔤🔤🔤🔣🔤🔤🔤🔤🔤 важное дополнение. Билет категории «Meet & Greet» не является входным билетом на концерт. Для посещения концерта необходимо дополнительно приобрести билет категории «Танцпол» или «VIP». «Meet & Greet» — это дополнение к билету на концерт, оно включает в себя: • ранний вход на площадку; • фото с артистом; • постер с автографом. Точный тайминг и инструкции обладатели билетов на «Meet & Greet» получат на э

🔥4

14 Jul 2026, 11:58 UTC86 views5 reactionsread 9 August 2026
Photo

BRICK BAZUKA 😎 возвращается с туром по России уже этой осенью. В ноябре пройдут громкие концерты, где прозвучат треки с последних релизов, включая альбом «XIII», а также любимые песни, которые уже стали частью истории. Услышать их вживую — совсем другое ощущение. 🗣 Выбирайте свой город*, увидимся на концерте: 3 ноября — Санкт-Петербург @ Фабрика 3 4 ноября — Москва @ Урбан 6 ноября — Екатеринбург @ Фабрика Ивен Хо

🔥4💋1

17 Feb 2026, 04:44 UTC370 viewsread 9 August 2026
Photo

🔥 ЕКБ ФОТООТЧЁТ Спасибо всем, кто был на концерте. Может, с кем-то из вас пересечемся в Москве или Питере. А пока ловите кайфовые фотки по ссылке ниже. Качайте самые лучшие, хранение ограничено до 16 мая 2026. 🔗 Фото с концерта *если смотрите с ПК, то выбирайте "интернет", с телефона – "полный размер". Всё ради качества снимков.

13 Feb 2026, 17:30 UTC289 views13 reactionsread 9 August 2026
Forwarded from @brickbazukaDMTVideo

Екатеринбург это было очень 🦾💜

13

13 Feb 2026, 07:27 UTC329 views1 reactionsread 9 August 2026
Photo

🔥 КОНЦЕРТ СЕГОДНЯ BRICK BAZUKA выступит на сцене в 20:00. Приходите заранее. Для иногородних действует скидка 30% при покупке билета на входе. Тайминг концерта 👉 здесь 🎫 Купить билеты онлайн на сайте

💩1

12 Feb 2026, 06:11 UTC259 viewsread 9 August 2026
Photo

🥩 КОНЦЕРТ ЗАВТРА Раскрывайте карты: кто купил митку? Запуск на meet&greet в18:10. Не опаздывайте. 📂 Расписание 🎫 Билеты

Showing the 12 most recent of 20 posts we hold for @brickbazukaekb. 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 15 August 2026 — this entry's latest reading, not the date you are reading this.

“BRICK BAZUKA | 06.11.2026, Екатеринбург” (@brickbazukaekb), 72 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/brickbazukaekb.

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.