Привет.

Channel
Brüzen's
@Bruzens
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
1,541subscribers
-18 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002685706152 |
|---|---|
| Type | Channel |
| Username | @Bruzens |
| Created | 1 May 2025 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/Bruzens |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 01:01 | 1,541 | -14 |
| 8 Aug 2026, 09:32 | 1,555 | -4 |
| 7 Aug 2026, 21:31 | 1,559 | no change |
| 7 Aug 2026, 15:52 | 1,559 | first reading |
Engagement
14 posts held, back to 1 May 2025 — the 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
- 12.8%
- avg views ÷ 1,541 subscribers
- Avg views / post
- 197
- 1 post measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1
- of 14 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.
| Window | Rolling 30 days · latest post in window 4 August 2026 |
|---|---|
| Posts held | 14 (1 May 2025 – 4 August 2026) |
| Views total | 197 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 21: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
- 1m 35s
- Average length
- 19s
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
3,645 reactions across 12 posts, in 29 distinct kinds. The most used accounts for 18.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5193013578562548300 | 667 | 18.3% | |
| custom 5400225151931396851 | 576 | 15.8% | |
| custom 5192716826387165311 | 376 | 10.3% | |
| custom 5400119474261078386 | 281 | 7.71% | |
| custom 5262906461838665147 | 244 | 6.69% | |
| custom 5337179365648125592 | 226 | 6.20% | |
| custom 5337311341403195697 | 218 | 5.98% | |
| custom 5400026088787161978 | 159 | 4.36% | |
| custom 5339378139795573684 | 151 | 4.14% | |
| custom 5440685749609449792 | 146 | 4.01% | |
| custom 5237965535211178178 | 73 | 2.00% | |
| custom 5319070993254201336 | 67 | 1.84% | |
| custom 5399941787169076474 | 64 | 1.76% | |
| custom 5399983487006552895 | 60 | 1.65% | |
| custom 5316994101688677895 | 49 | 1.34% | |
| custom 5316941118972115293 | 41 | 1.12% | |
| custom 5337230024787382695 | 39 | 1.07% | |
| custom 5400333269143138343 | 38 | 1.04% | |
| custom 5339032815835041011 | 37 | 1.02% | |
| custom 5238148560947534573 | 33 | 0.905% | |
| 9 further kinds | 100 | 2.74% |
Custom emoji. Every row above is a 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 14 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 3,645reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 1 May 2025 to 4 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.
Telegram Stars
- Stars received
- 16,066
- across the posts below
- Posts paid on
- 11
- of 13 we hold a reading for · 85%
- Most on one post
- 6,380
- single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Bruzens. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 14 most recent posts we hold for this entry, published 1 May 2025 to 4 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Recent posts
Photo, posted without a caption
custom 540022515193139685123custom 540002608878716197819custom 540011947426107838618custom 51930135785625483001
File, posted without a caption
custom 540002608878716197822custom 540022515193139685116custom 51930135785625483008custom 54001194742610783861
Photo, posted without a caption
custom 540022515193139685130custom 540002608878716197821custom 540011947426107838620custom 51930135785625483001
🌟
custom 519301357856254830043custom 519271682638716531128custom 540002608878716197824custom 54003332691431383437custom 54002251519313968516custom 54001194742610783865
🔞
custom 5192716826387165311135custom 519301357856254830090custom 540022515193139685184custom 523796553521117817816custom 540033326914313834315custom 523814856094753457313custom 54001194742610783868
Signed Brüzen
🌟
custom 519301357856254830093custom 523796553521117817853custom 519271682638716531144custom 540033326914313834316custom 523814856094753457315custom 540002608878716197815custom 540022515193139685115custom 54001194742610783869
Signed Brüzen
🌟
custom 540011947426107838629custom 519301357856254830017custom 519271682638716531116custom 54002251519313968516custom 52381485609475345735custom 52379655352111781784
Signed D
🌟
custom 5400225151931396851203custom 5193013578562548300130custom 5192716826387165311117custom 540011947426107838628custom 539994178716907647427custom 539998348700655289525custom 540002608878716197823
Signed Brüzen
🌟
custom 5193013578562548300284custom 5400225151931396851193custom 5400119474261078386163custom 539994178716907647437custom 519271682638716531136custom 539998348700655289535custom 540002608878716197835
Signed Brüzen
🤩
custom 5337311341403195697196custom 5339378139795573684137custom 5262906461838665147123custom 533723002478738269517custom 544068574960944979217custom 533903281583504101115custom 533717936564812559213
Signed Brüzen
🌟
custom 5337179365648125592213custom 5440685749609449792129custom 5262906461838665147121custom 526280226163709722425custom 533723002478738269522custom 533731134140319569722custom 533903281583504101122custom 533937813979557368414
Signed Brüzen
Showing the 12 most recent of 14 posts we hold for @Bruzens. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank
Citation-graph rank — 375,660 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
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Brüzen's” (@Bruzens), 1,541 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/Bruzens.
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.