Telegram RegisterThe public register of Telegram

Channel

🗽

@bronx_05

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

25subscribers

+0 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-1002363084633
TypeChannel
Username@bronx_05
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/bronx_05

Growth

257 August 2026 — 25 subscribers11 August 2026 — 25 subscribers7 August 202611 August 2026
2 measurements spanning 4 days. 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 24–26 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 09:4825no change
7 Aug 2026, 17:4025first reading

Engagement

19 posts held, back to 12 November 2025the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 14 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
30
Videos
84
Links
4

Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
2m 13s
Average length
22s

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

195 reactions across 17 posts, in 26 distinct kinds. The most used accounts for 10.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54137001694409849682010.3%
custom 5461041566720224603189.23%
custom 5235632457436381926178.72%
custom 5251692327998607174168.21%
custom 5237820412561212491147.18%
custom 5404741310043152124126.15%
custom 5355249220775334858105.13%
custom 520657331430204659894.62%
custom 535983595808466704994.62%
custom 539082080134577364294.62%
custom 519287778028659358384.10%
custom 536187905684750016573.59%
custom 523549642293721547752.56%
custom 541588812456581009852.56%
custom 579436705937045131452.56%
custom 523774989778814419442.05%
custom 528961017618840332442.05%
custom 544527597872717082542.05%
custom 521753542375612699931.54%
custom 533690336675471738831.54%
6 further kinds136.67%

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

Measured over the 19 most recent posts we hold, published 12 November 2025 to 14 June 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
15
across the posts below
Posts paid on
2
of 17 we hold a reading for · 12%
Most on one post
14
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @bronx_05. 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 19 most recent posts we hold for this entry, published 12 November 2025 to 14 June 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

14 Jun 2026, 20:30 UTC31 views7 reactionsread 11 August 2026
Video

Video, posted without a caption

custom 52378204125612124913custom 54610415667202246033custom 54047413100431521241

29 Mar 2026, 08:16 UTC54 views8 reactionsread 11 August 2026
Video

Video, posted without a caption

custom 52378204125612124914custom 54610415667202246034

11 Jan 2026, 21:21 UTC72 views1 reactionsread 11 August 2026

Барселона барса барса

custom 54047413100431521241

23 Dec 2025, 18:06 UTC264 views8 reactionsread 11 August 2026
Video

Video, posted without a caption

custom 52065733143020465984custom 54610415667202246032custom 52896101761884033241custom 53552492207753348581

17 Dec 2025, 15:26 UTC128 views15 reactionsread 11 August 2026

на 25 реакций розыгрыш на тг премиум

custom 53552492207753348586custom 54047413100431521246custom 51928777802865935831custom 52896101761884033241custom 54610415667202246031

17 Dec 2025, 15:26 UTC123 views18 reactionsread 11 August 2026
Video

Video, posted without a caption

custom 54610415667202246037custom 54047413100431521244custom 52378204125612124912custom 53552492207753348582custom 53618790568475001652custom 51928777802865935831

15 Dec 2025, 14:39 UTC107 views13 reactionsread 11 August 2026

Ноу Шама итс Шома тайм

custom 51928777802865935835custom 52378204125612124915custom 53618790568475001652custom 52379992678843461391

15 Dec 2025, 14:38 UTC98 views7 reactionsread 11 August 2026
Photo

Photo, posted without a caption

custom 52065733143020465983custom 52896101761884033242custom 51928777802865935831custom 53618790568475001651

12 Dec 2025, 18:34 UTC69 views10 reactionsread 11 August 2026
Forwarded from @iron_editsPhoto

Сделаю такую аву за 5 пересылок 🚀 скрин в комментарии👇🏼

custom 52175354237561269993custom 52356324574363819263custom 53618790568475001652custom 53552492207753348581custom 54610415667202246031

10 Dec 2025, 10:52 UTC96 views13 reactionsread 11 August 2026
Photo

🥴

custom 54158881245658100985custom 54452759787271708254custom 54429701138651865022custom 52516923279986071741custom 59697352942351874031

7 Dec 2025, 09:07 UTC115 views12 reactionsread 11 August 2026
Photo

Сюрприз сюрприз 🇷🇺

custom 52516923279986071746custom 53369033667547173883custom 59720357903880741052custom 52377498977881441941

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

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.

“🗽” (@bronx_05), 25 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/bronx_05.

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.