🥺
💅41custom 528501041653825748423custom 528308729768683641310🙏2custom 52852798956713134912custom 52852233739016958241custom 54088383008216554061

Channel
@Catavi1234
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
756subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002886510275 |
|---|---|
| Type | Channel |
| Username | @Catavi1234 |
| Created | 14 August 2025 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 8 August 2026 |
| On Telegram | t.me/Catavi1234 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 16:17 | 756 | -2 |
| 8 Aug 2026, 01:50 | 758 | no change |
| 7 Aug 2026, 17:25 | 758 | first reading |
11 posts held, back to 14 August 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 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 1 August 2026 |
|---|---|
| Posts held | 11 (14 August 2025 – 1 August 2026) |
| Views total | 7,177 |
| Reactions total | 602 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 01:50 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.
602 reactions across 10 posts, in 8 distinct kinds. The most used accounts for 28.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5283087297686836413 | 174 | 28.9% | |
| 🙏 | 141 | 23.4% | |
| custom 5285010416538257484 | 122 | 20.3% | |
| 💅 | 53 | 8.80% | |
| custom 5408838300821655406 | 46 | 7.64% | |
| custom 5285223373901695824 | 34 | 5.65% | |
| custom 5285279895671313491 | 20 | 3.32% | |
| custom 5285212683728097633 | 12 | 1.99% |
Custom emoji. 6 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 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 11 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 602reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 14 August 2025 to 1 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.
🥺
💅41custom 528501041653825748423custom 528308729768683641310🙏2custom 52852798956713134912custom 52852233739016958241custom 54088383008216554061
кипяу, я смог за 5 часов сделать только это🥹
🙏33custom 528308729768683641317💅4custom 52850104165382574841custom 52852233739016958241custom 54088383008216554061
лучше неферпиту пойду делать изначально хотел сделать цветной, но слишком привык к чб
custom 528308729768683641334🙏10custom 54088383008216554065
вроде... норм? тг все же зажопил штриховку 🥺
🙏47custom 528522337390169582410custom 52830872976868364138custom 54088383008216554061
так и не понял, ну ладно... предположи вы хотите Неферпиту ivatac начал артик готовить, наверное, круто, поддержим юного автора
custom 540883830082165540631custom 528501041653825748416🙏5💅2custom 52852233739016958241
короче в иксе под Некоарк пишут что она на Неферпиту(см рис 1) из hxh похожа... ну короче если хотите чтобы я её сделал, то дайте знать...😛
custom 528501041653825748427🙏9custom 52830872976868364138
ну вот все, осталась хайп анимация незаметное введение: с прошлой модели я начал использовать свет как маску для смешения нескольких текстур(чтобы вместо одной текстуры делать несколько🤩) на следующей модельке получше с этим поработаю
custom 528308729768683641366🙏17custom 52852126837280976339custom 52852233739016958242custom 54088383008216554061
вайбы хайтейла хз🤩 и это... чуть-чуть не то что я хотел а еще она сделана на процентов 80
custom 528501041653825748455custom 528308729768683641326🙏15custom 52852126837280976333custom 52852233739016958242custom 54088383008216554061
чзх, на архив не надо подписываться 😭
custom 528522337390169582417💅6custom 54088383008216554063🙏1
канал под реновациями я такое придумал там лучше показать чем рассказывать так что подождите немножечко 🤩 предыдущие посты(архив) 😛 https://t.me/archiv228catavi картинка просто смешная
custom 528527989567131349118custom 52830872976868364135🙏2custom 54088383008216554062
Channel created
Showing the 11 most recent of 11 posts we hold for @Catavi1234. 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.
Citation-graph rank — 49,594 of 1,480,688entries 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.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“cat[ca]avi” (@Catavi1234), 756 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Catavi1234.
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.