Telegram RegisterThe public register of Telegram
Telegram profile photo for Zenus & Bagu servise

Channel

Zenus & Bagu servise

@Bagu_bs

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

550subscribers

-70 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1003981822415
TypeChannel
Username@Bagu_bs
CreatedBetween 1 April 2026 and 12 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live3 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 3 September 2026
On Telegramt.me/Bagu_bs

Growth

55065260112 August 2026 — 620 subscribers12 August 2026 — 615 subscribers20 August 2026 — 652 subscribers26 August 2026 — 613 subscribers3 September 2026 — 550 subscribers12 August 20263 September 2026
5 measurements spanning 22 days, net -70. 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 535–667 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Sept 2026, 02:57550-63
26 Aug 2026, 06:54613-39
20 Aug 2026, 07:34652+37
12 Aug 2026, 17:53615-5
12 Aug 2026, 10:32620first reading

Engagement

20 posts held, back to 12 August 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
16.6%
avg views ÷ 550 subscribers
Avg views / post
91.0
20 posts measured
Reaction rate
8.96%
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 19 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 12 August 2026
Posts held20 (12 August 202612 August 2026)
Views total1,821
Reactions total156
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 10:32 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

156 reactions across 19 posts, in 3 distinct kinds. The most used accounts for 39.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54516736804069317086139.1%
custom 54516810720456451925434.6%
custom 53460337972111342014126.3%

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 are Telegram’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 19 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 156 reactions 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 12 August 2026 to 12 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
108
across the posts below
Posts paid on
9
of 20 we hold a reading for · 45%
Most on one post
28
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Bagu_bs. 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 20 most recent posts we hold for this entry, published 12 August 2026 to 12 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

12 Aug 2026, 08:07 UTC69 views4 reactionsread 12 August 2026

👤 Ishtirokchi: Норматов (@normatov_999) 👍 Reaksiyalar: 0 (0 ball) ⭐️ Stars: 0 (0 ball) 💬 Kommentlar: 0 (0 ball) 📊 Jami: 0 ball

custom 53460337972111342014

Signed Nft Battle

12 Aug 2026, 07:19 UTC81 views4 reactionsread 12 August 2026

👤 Ishtirokchi: Todoshi (@Todoshi777) 👍 Reaksiyalar: 4 (4 ball) ⭐️ Stars: 0 (0 ball) 💬 Kommentlar: 1 (3 ball) 📊 Jami: 7 ball

custom 54516736804069317084

Signed Nft Battle

12 Aug 2026, 07:13 UTC81 views5 reactions20 Starsread 12 August 2026

👤 Ishtirokchi: . (@Laziz2124) 👍 Reaksiyalar: 5 (5 ball) ⭐️ Stars: 20 (100 ball) 💬 Kommentlar: 5 (15 ball) 📊 Jami: 120 ball

custom 54516736804069317085

Signed Nft Battle

12 Aug 2026, 07:05 UTC85 views1 reactionsread 12 August 2026

👤 Ishtirokchi: Nodirbek🥋 (@Akhmatov_00) 👍 Reaksiyalar: 1 (1 ball) ⭐️ Stars: 0 (0 ball) 💬 Kommentlar: 1 (3 ball) 📊 Jami: 4 ball

custom 54516810720456451921

Signed Nft Battle

12 Aug 2026, 07:03 UTC109 views7 reactionsread 12 August 2026

👤 Ishtirokchi: X7 | CTYLE (@ortiqov717) 👍 Reaksiyalar: 7 (7 ball) ⭐️ Stars: 0 (0 ball) 💬 Kommentlar: 2 (6 ball) 📊 Jami: 13 ball

custom 53460337972111342013custom 54516810720456451923custom 54516736804069317081

Signed Nft Battle

12 Aug 2026, 06:55 UTC120 views27 reactions28 Starsread 12 August 2026

👤 Ishtirokchi: Abbos 🦦 (@Fkh_Abbos) 👍 Reaksiyalar: 27 (27 ball) ⭐️ Stars: 28 (140 ball) 💬 Kommentlar: 19 (57 ball) 📊 Jami: 224 ball

custom 545168107204564519217custom 53460337972111342015custom 54516736804069317085

Signed Nft Battle

12 Aug 2026, 06:55 UTC84 views4 reactions8 Starsread 12 August 2026

👤 Ishtirokchi: _nematov_24 (@Xamidov19) 👍 Reaksiyalar: 4 (4 ball) ⭐️ Stars: 8 (40 ball) 💬 Kommentlar: 2 (6 ball) 📊 Jami: 50 ball

custom 53460337972111342012custom 54516736804069317081custom 54516810720456451921

Signed Nft Battle

12 Aug 2026, 06:53 UTC105 views4 reactionsread 12 August 2026

👤 Ishtirokchi: 𝓚𝓪𝓼𝟙𝓶𝓸𝓿𝓿 (@kas1mov_221020) 👍 Reaksiyalar: 4 (4 ball) ⭐️ Stars: 0 (0 ball) 💬 Kommentlar: 4 (12 ball) 📊 Jami: 16 ball

custom 54516810720456451924

Signed Nft Battle

12 Aug 2026, 06:43 UTC114 views15 reactions9 Starsread 12 August 2026

👤 Ishtirokchi: CI♤TE♧R (@Mujihs) 👍 Reaksiyalar: 15 (15 ball) ⭐️ Stars: 9 (45 ball) 💬 Kommentlar: 9 (27 ball) 📊 Jami: 87 ball

custom 545167368040693170810custom 54516810720456451923custom 53460337972111342012

Signed Nft Battle

12 Aug 2026, 06:41 UTC127 views12 reactions21 Starsread 12 August 2026

👤 Ishtirokchi: Bobur! (@agzamovbobur) 👍 Reaksiyalar: 12 (12 ball) ⭐️ Stars: 21 (105 ball) 💬 Kommentlar: 4 (12 ball) 📊 Jami: 129 ball

custom 54516736804069317086custom 53460337972111342013custom 54516810720456451923

Signed Nft Battle

12 Aug 2026, 06:40 UTC84 views9 reactionsread 12 August 2026

👤 Ishtirokchi: Farmonov (@uzb_sheykh) 👍 Reaksiyalar: 9 (9 ball) ⭐️ Stars: 0 (0 ball) 💬 Kommentlar: 4 (12 ball) 📊 Jami: 21 ball

custom 54516810720456451924custom 53460337972111342013custom 54516736804069317082

Signed Nft Battle

12 Aug 2026, 06:30 UTC124 views21 reactions8 Starsread 12 August 2026

👤 Ishtirokchi: JIROINCHII (@JIIROINCHII) 👍 Reaksiyalar: 21 (21 ball) ⭐️ Stars: 8 (40 ball) 💬 Kommentlar: 9 (27 ball) 📊 Jami: 88 ball

custom 545167368040693170810custom 53460337972111342016custom 54516810720456451925

Signed Nft Battle

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

Forward network

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 3 registered channels — 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 3 September 2026 — this entry's latest reading, not the date you are reading this.

“Zenus & Bagu servise” (@Bagu_bs), 550 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/Bagu_bs.

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.