ะธะทะฒะธะฝะธัะต ัะตะฑัั ะพะณัะพะผะฝะพะต ะบะพะปะธัะตััะฒะพ ะฝะฐัะตะทะพะบ ะพัะผะตะฝัะตััั ะดะพ ัะปะตะดัััะตะณะพ ะฒะพัะบัะตัะตะฝัะต, ั ะฑะตะท ะฒัั ะพะดะฝัั
โค1

Channel
@KAZ5CS
On this record: Growth ยท Engagement ยท Reactions ยท Stars ยท Posts ยท Citations ยท Cite this entry
255subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register ยท movement among entries of Under 1,000.
| Telegram ID | -1003899355266 |
|---|---|
| Type | Channel |
| Username | @KAZ5CS |
| Created | Between 1 February 2026 and 4 June 2026โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 7 August 2026 |
| On Telegram | t.me/KAZ5CS |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 21:33 | 255 | -1 |
| 7 Aug 2026, 02:02 | 256 | no change |
| 6 Aug 2026, 22:02 | 256 | first reading |
20 posts held, back to 4 June 2026 โ 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 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 2 August 2026 |
|---|---|
| Posts held | 20 (4 June 2026 โ 2 August 2026) |
| Views total | 984 |
| Reactions total | 52 |
| Forwards / comments | not exposed by the public surface โ not measured, not estimated |
| Readings taken | 7 Aug 2026, 02:02 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.
912 reactions across 20 posts, in 6 distinct kinds. The most used accounts for 23.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| โค | 213 | 23.4% | |
| โคโ๐ฅ | 165 | 18.1% | |
| ๐ | 146 | 16.0% | |
| ๐ | 144 | 15.8% | |
| ๐ฅ | 134 | 14.7% | |
| ๐ | 110 | 12.1% |
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 20 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 912reactions 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 4 June 2026 to 2 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.
A paid reaction is a reader spending Telegram Stars โ bought with money โ on a post by @KAZ5CS. 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 4 June 2026 to 2 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.
ะธะทะฒะธะฝะธัะต ัะตะฑัั ะพะณัะพะผะฝะพะต ะบะพะปะธัะตััะฒะพ ะฝะฐัะตะทะพะบ ะพัะผะตะฝัะตััั ะดะพ ัะปะตะดัััะตะณะพ ะฒะพัะบัะตัะตะฝัะต, ั ะฑะตะท ะฒัั ะพะดะฝัั
โค1
ะฝะฐัะตะทะบะธ ะฟะตัะตะฝะพััััั ะฝะฐ ะฟะพะฝะตะดะตะปัะฝะธะบ, ั ะผะตะฝั ะฝะฐ ะฒะพัะบัะตัะตะฝัะต ะฒะฝะตะฟะปะฐะฝะพะฒะฐั ัะผะตะฝะฐ
๐1
๐๐๐๐ ๐๐ ๐๐๐ญ โ ๐๐ฌ๐ ๐๐ฒ๐ ๐๐ฒ๐ฟ | ๐ช๐ต๐ถ๐ ๐๐ผ๐ฎ๐ธ๐ฒ๐ "+" ๐ถ๐ป ๐๐ต๐ฒ ๐ฐ๐ผ๐บ๐บ๐ฒ๐ป๐๐ โยฐ.
โคโ๐ฅ20๐11โค10๐ฅ4๐3๐2
๐๐๐๐ ๐๐ ๐๐๐ญ โ ๐๐ฌ๐ ๐ฉ๐ฎ๐น๐ฒ๐ฟ๐ถ๐ฎ๐ป ๐ฎ๐ป๐ฑ ๐๐ต๐ฒ ๐๐ถ๐๐ ๐ผ๐ณ ๐ฎ ๐ง๐ต๐ผ๐๐๐ฎ๐ป๐ฑ ๐ฃ๐น๐ฎ๐ป๐ฒ๐๐ | ๐ช๐ต๐ถ๐ ๐๐๐ฏ๐ฏ๐น๐ฒ "+" ๐ถ๐ป ๐๐ต๐ฒ ๐ฐ๐ผ๐บ๐บ๐ฒ๐ป๐๐ โยฐ.
โคโ๐ฅ21๐10๐ฅ10๐7โค4๐4
๐๐๐๐ ๐๐ ๐๐๐ญ โ ๐๐ฌ๐ ๐ง๐ต๐ฒ ๐๐ผ๐๐ | ๐ช๐ต๐ถ๐ ๐ฆ๐๐ฎ๐ฟ๐น๐ถ๐ด๐ต๐ "+" ๐ถ๐ป ๐๐ต๐ฒ ๐ฐ๐ผ๐บ๐บ๐ฒ๐ป๐๐ โยฐ.
๐15๐15๐ฅ11๐5โค2โคโ๐ฅ2
๐๐๐๐ ๐๐ ๐๐๐ญ โ ๐๐ฌ๐ ๐ง๐ต๐ฒ ๐ฉ๐ฎ๐บ๐ฝ๐ถ๐ฟ๐ฒ ๐๐ถ๐ฎ๐ฟ๐ถ๐ฒ๐ | ๐ช๐ต๐ถ๐ ๐ฆ๐๐ฒ๐ณ๐ฎ๐ป ๐ฆ๐ฎ๐น๐๐ฎ๐๐ผ๐ฟ๐ฒ "+" ๐ถ๐ป ๐๐ต๐ฒ ๐ฐ๐ผ๐บ๐บ๐ฒ๐ป๐๐ โยฐ.
โคโ๐ฅ18๐12๐12โค6๐ฅ2๐2
๐๐๐๐ ๐๐ ๐๐๐ญ โ ๐๐ฌ๐ ๐ง๐ต๐ฒ ๐ ๐ฒ๐ป๐๐ฎ๐น๐ถ๐๐ | ๐ช๐ต๐ถ๐ ๐ช๐ฎ๐๐ป๐ฒ ๐ฅ๐ถ๐ด๐๐ฏ๐ "+" ๐ถ๐ป ๐๐ต๐ฒ ๐ฐ๐ผ๐บ๐บ๐ฒ๐ป๐๐ โยฐ.
๐15โค10๐8๐6๐ฅ3โคโ๐ฅ2
๐๐๐๐ ๐๐ ๐๐๐ญ โ ๐๐ฌ๐ ๐ง๐ต๐ฒ ๐ ๐ฒ๐ป๐๐ฎ๐น๐ถ๐๐ | ๐ช๐ต๐ถ๐ ๐๐ฟ๐ฎ๐ฐ๐ฒ ๐ฉ๐ฎ๐ป ๐ฃ๐ฒ๐น๐ "+" ๐ถ๐ป ๐๐ต๐ฒ ๐ฐ๐ผ๐บ๐บ๐ฒ๐ป๐๐ โยฐ.
๐10๐9โค8๐5โคโ๐ฅ2๐ฅ2
๐๐๐๐ ๐๐ ๐๐๐ญ โ ๐๐ฌ๐ ๐ง๐ต๐ฒ ๐๐ผ๐๐ | ๐ช๐ต๐ถ๐ ๐ค๐๐ฒ๐ฒ๐ป ๐ ๐ฎ๐ฒ๐๐ฒ "+" ๐ถ๐ป ๐๐ต๐ฒ ๐ฐ๐ผ๐บ๐บ๐ฒ๐ป๐๐ โยฐ.
๐15โคโ๐ฅ8๐8โค5๐5๐ฅ4
๐๐๐๐ ๐๐ ๐๐๐ญ โ ๐๐ฌ๐ ๐๐ฎ๐ฟ๐ธ ๐๐ป๐ด๐ฒ๐น | ๐ช๐ต๐ถ๐ ๐๐ฒ๐ป "+" ๐ถ๐ป ๐๐ต๐ฒ ๐ฐ๐ผ๐บ๐บ๐ฒ๐ป๐๐ โยฐ.
๐ฅ20โค12๐12โคโ๐ฅ2๐2๐2
๐๐๐๐ ๐๐ ๐๐๐ญ โ ๐๐ฌ๐ ๐๐ฒ๐ ๐๐ฒ๐ฟ | ๐ช๐ต๐ถ๐ ๐๐ฒ๐ฏ๐ฟ๐ฎ ๐ ๐ผ๐ฟ๐ด๐ฎ๐ป "+" ๐ถ๐ป ๐๐ต๐ฒ ๐ฐ๐ผ๐บ๐บ๐ฒ๐ป๐๐ โยฐ.
๐16โค10๐8๐5๐ฅ4โคโ๐ฅ2
๐๐๐๐ ๐๐ ๐๐๐ญ โ ๐๐ฌ๐ ๐๐ฒ๐ ๐๐ฒ๐ฟ | ๐ช๐ต๐ถ๐ ๐๐ฒ๐ ๐๐ฒ๐ฟ ๐ ๐ผ๐ฟ๐ด๐ฎ๐ป "+" ๐ถ๐ป ๐๐ต๐ฒ ๐ฐ๐ผ๐บ๐บ๐ฒ๐ป๐๐ โยฐ.
โคโ๐ฅ18โค13๐8๐ฅ7๐4๐4
Showing the 12 most recent of 20 posts we hold for @KAZ5CS. 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 โ 573,907 of 1,160,990entries 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.
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.
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 7 August 2026 โ this entry's latest reading, not the date you are reading this.
โ๐๐๐๐ โ ๐๐๐ ๐๐๐โ (@KAZ5CS), 255 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/KAZ5CS.
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.