как жаль, что тг съедает половину качества фоток
custom 521338977529314488028custom 518860407307871225313custom 520403743246650172612

Channel
@katoqq
On this record: Growth · Engagement · Reactions · Stars · Posts · Cite this entry
55subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002437390076 |
|---|---|
| Type | Channel |
| Username | @katoqq |
| Created | Between 1 September 2024 and 27 November 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/katoqq |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 18:43 | 55 | -2 |
| 16 Aug 2026, 08:34 | 57 | -1 |
| 10 Aug 2026, 06:30 | 58 | no change |
| 7 Aug 2026, 15:03 | 58 | first reading |
10 posts held, back to 27 November 2024 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 10 posts for this entry, the most recent from 20 February 2025. An engagement rate over an empty window would be a number about nothing.
964 reactions across 10 posts, in 17 distinct kinds. The most used accounts for 20.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5354923692319074444 | 198 | 20.5% | |
| custom 5352765402533356489 | 140 | 14.5% | |
| custom 5355257329673590143 | 90 | 9.34% | |
| custom 5213389775293144880 | 89 | 9.23% | |
| custom 5262522801000043220 | 89 | 9.23% | |
| custom 5386656955106353818 | 64 | 6.64% | |
| custom 5188604073078712253 | 63 | 6.54% | |
| custom 5276206712833985061 | 59 | 6.12% | |
| custom 5312381328287612926 | 51 | 5.29% | |
| custom 5204037432466501726 | 50 | 5.19% | |
| custom 5474667530855398683 | 39 | 4.05% | |
| custom 5463028697764216051 | 10 | 1.04% | |
| custom 5354997514216953739 | 6 | 0.622% | |
| custom 5380049646137663815 | 5 | 0.519% | |
| custom 5355204235287881708 | 4 | 0.415% | |
| custom 5357585910617626300 | 4 | 0.415% | |
| custom 5363839082352900446 | 3 | 0.311% |
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 10 of the 10 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 964reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 27 November 2024 to 20 February 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @katoqq. 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 10 most recent posts we hold for this entry, published 27 November 2024 to 20 February 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.
как жаль, что тг съедает половину качества фоток
custom 521338977529314488028custom 518860407307871225313custom 520403743246650172612
немножк старые фотки, но ладно
custom 521338977529314488032custom 520403743246650172615custom 518860407307871225310
🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦🪦
custom 518860407307871225340custom 521338977529314488029custom 520403743246650172623
лебеди
custom 535492369231907444448custom 535276540253335648924custom 535525732967359014320custom 538665695510635381810
🤩
custom 535492369231907444447custom 535276540253335648931custom 535525732967359014322custom 538665695510635381817
😛
custom 535492369231907444450custom 535276540253335648936custom 535525732967359014325custom 538665695510635381815
фууу пикми
custom 535492369231907444453custom 535276540253335648928custom 538665695510635381822custom 535525732967359014312
снуд имба
custom 531238132828761292640custom 526252280100004322026custom 535276540253335648921custom 52762067128339850618custom 53552042352878817084custom 53575859106176263004custom 53638390823529004463
❤️
custom 527620671283398506135custom 526252280100004322029custom 547466753085539868317custom 53549975142169537396custom 53123813282876129265custom 53552573296735901435custom 54630286977642160515
🥛
custom 526252280100004322034custom 547466753085539868322custom 527620671283398506116custom 53123813282876129266custom 53552573296735901436custom 53800496461376638155custom 54630286977642160515
Showing the 10 most recent of 10 posts we hold for @katoqq. 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.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“трупная яма” (@katoqq), 55 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/katoqq.
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.