7 measurements spanning 39 days, net -21. 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 229–256 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
15 Sept 2026, 08:21
232
-4
7 Sept 2026, 21:41
236
-5
30 Aug 2026, 11:35
241
-4
23 Aug 2026, 22:46
245
-4
16 Aug 2026, 05:36
249
-4
8 Aug 2026, 09:19
253
no change
7 Aug 2026, 16:56
253
first reading
Engagement
4 posts held, back to 3 October 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 page of 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 4 posts for this entry, the most recent from 9 October 2025. An engagement rate over an empty window would be a number about nothing.
Reaction mix
54 reactions across 3 posts, in 10 distinct kinds. The most used accounts for 22.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5274193038892081385
12
22.2%
custom 5273819677385040066
9
16.7%
custom 5271960587906064980
8
14.8%
🔥
6
11.1%
custom 5271861911032439803
5
9.26%
custom 5273926909833518992
5
9.26%
custom 5274018160708690390
3
5.56%
custom 5271751569027637049
2
3.70%
custom 5274037393572240943
2
3.70%
custom 5355314839285669701
2
3.70%
Custom emoji. 9 of the rows above are 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 3 of the 4 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 54 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 3 October 2025 to 9 October 2025, 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
7
across the posts below
Posts paid on
2
of 3 we hold a reading for · 67%
Most on one post
4
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @premium_xizmati4. 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 4 most recent posts we hold for this entry, published 3 October 2025 to 9 October 2025. 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.
Stars narxlari⭐️
Starslar gift (Sovg'a)qilib olib beriladi
100 ta stars 35.000 sõm⭐️
150 ta stars 49.000 sõm⭐️
250 ta stars 78.000 sõm⭐️
350 ta stars 104.000 sõm⭐️
500 ta stars 140.000 sõm⭐️
750 ta stars 198.000 sõm⭐️
1000 ta stars 260.000 sõm⭐️
Premium narxlari✅
Premiumni accauntga kirib olib berish
1 oylik obuna 46 000 sõm⭐️
12 oylik obuna 293 000 sõm⭐️
Premiumni accauntga kirmasdan gift(sovg'a) sifatida olib berish🎁
3 oylik obuna 175 000 sõm⭐️
6 oylik obuna 230 000 sõm⭐️
12 oylik obuna 399 000 sõm⭐️
Showing the 4 most recent of 4 posts we hold for @premium_xizmati4. 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.
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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@premium_xizmati4 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@katsuo_premium named in 1 post, 9 August 2026 – 9 August 2026
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 September 2026 — this
entry's latest reading, not the date you are reading this.
“𝙋𝙧𝙚𝙢𝙞𝙪𝙢 𝙭𝙞𝙯𝙢𝙖𝙩𝙞” (@premium_xizmati4), 232 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/premium_xizmati4.
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.
