Telegram RegisterThe public register of Telegram
Telegram profile photo for Copper Birzha | @xebku

Channel

Copper Birzha | @xebku

@copperbirzha

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

11subscribers

+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-1003692706144
TypeChannel
Username@copperbirzha
Created19 January 2026measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/copperbirzha

Growth

117 August 2026 — 11 subscribers12 August 2026 — 11 subscribers7 August 202612 August 2026
2 measurements spanning 5 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 10–12 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 07:3011no change
7 Aug 2026, 18:1911first reading

Engagement

3 posts held, back to 19 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.

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

Recent posts

20 Jan 2026, 08:46 UTCviews —

Copper Birzha | @xebku pinned «✍️ Выложить ваш товар в этот канал на время/навсегда ⏱1 час-20🪙 ⏱6 часов-50🪙 ⏱12часов-100🪙 ⏱24часа-150🪙 ⏱48часов-200🪙 ⏱неделя-500🪙 В закреп- +20🪙сверху ⚖️⚖️Так же пост будет рассылаться из за маленького количества подписчиков(рассылаться в 600+ чатов)⚖️⚖️…»

20 Jan 2026, 08:46 UTC474 viewsread 12 August 2026

✍️ Выложить ваш товар в этот канал на время/навсегда ⏱1 час-20🪙 ⏱6 часов-50🪙 ⏱12часов-100🪙 ⏱24часа-150🪙 ⏱48часов-200🪙 ⏱неделя-500🪙 В закреп- +20🪙сверху ⚖️⚖️Так же пост будет рассылаться из за маленького количества подписчиков(рассылаться в 600+ чатов)⚖️⚖️ 🛫 @xebka - купить место в бирже

Showing the 3 most recent of 3 posts we hold for @copperbirzha. 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.

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

“Copper Birzha | @xebku” (@copperbirzha), 11 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/copperbirzha.

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.