✨Витраж🌿 Вот такая необычная работа у меня получилась
🔥16❤9😍6custom 54543362895475111043🍓1🤩1custom 54539308746995429061custom 54542387723150573741

Channel
@arina_cat18
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
216subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002127864681 |
|---|---|
| Type | Channel |
| Username | @arina_cat18 |
| Description | Я Рина. :) Здесь вы можете найти: Моих оригинальных персонажей и ОС (Как в традишке, так и в диджитале) И мой комикс. И ещё https://t.me/boost/arina_cat18 Проголосуйте пожалуйста 👉👈 |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/arina_cat18 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 10:47 | 216 | no change |
| 7 Aug 2026, 14:08 | 216 | first reading |
19 posts held, back to 16 July 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 6 August 2026 |
|---|---|
| Posts held | 19 (16 July 2026 – 6 August 2026) |
| Views total | 2,040 |
| Reactions total | 520 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 10:47 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.
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
520 reactions across 19 posts, in 20 distinct kinds. The most used accounts for 23.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 122 | 23.5% | |
| 🔥 | 67 | 12.9% | |
| custom 5453930874699542906 | 65 | 12.5% | |
| custom 5454367264851650535 | 55 | 10.6% | |
| custom 5454238772315057374 | 43 | 8.27% | |
| 🍓 | 39 | 7.50% | |
| 🕊 | 25 | 4.81% | |
| 💔 | 22 | 4.23% | |
| 🥰 | 16 | 3.08% | |
| custom 5454336289547511104 | 15 | 2.88% | |
| 😢 | 14 | 2.69% | |
| ⚡ | 11 | 2.12% | |
| 💋 | 8 | 1.54% | |
| ❤🔥 | 6 | 1.15% | |
| 😍 | 6 | 1.15% | |
| 👏 | 2 | 0.385% | |
| 🎉 | 1 | 0.192% | |
| 💘 | 1 | 0.192% | |
| 😱 | 1 | 0.192% | |
| 🤩 | 1 | 0.192% |
Custom emoji. 4 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 19 of the 19 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 520reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 16 July 2026 to 6 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.
✨Витраж🌿 Вот такая необычная работа у меня получилась
🔥16❤9😍6custom 54543362895475111043🍓1🤩1custom 54539308746995429061custom 54542387723150573741
🪵Начало положено📦 Начинаю рисовать работу и хочу еë сделать в витражном стиле. Зачем и почему — вы скоро узнаете 😋
🔥13custom 545423877231505737411custom 54539308746995429067❤5🍓1
Posted without readable text
❤3
Немного цвета решила добавить 👀
custom 545393087469954290616❤11custom 54542387723150573745🔥2🍓1custom 54543672648516505351
📷Зарисовочка🥾 Решила за часик что-то почиркать в альбоме и вот что вышло в итоге 🐰 #НебесноеОко
❤14custom 54543672648516505359🥰6custom 54539308746995429064❤🔥1🍓1🔥1custom 54542387723150573741
Немного спойлеров Доступные главы можете почитать здесь 👀
custom 545436726485165053511🥰10custom 54539308746995429068❤3🍓1🔥1😱1custom 54543362895475111041
Короче говоря мангалиб меня послал на три весëлых буквы и откланил тайтл (я будто бы и не удивлена) Ну зато у меня есть селфманга и я рада :_)
😢14💔9🕊6🍓3
https://vt.tiktok.com/ZSXWRRCrT/
🍓6❤4custom 54539308746995429063custom 54543672648516505352custom 54542387723150573741
🌱Аниматик🌱 Идею взяла у прекрасного художника (постик) У меня, как и у автора идеи показан один и тот же персонаж, а именно Олежа, но в совершено в разных вселеных. Наш — счастливый и задорный подросток, что живëт хорошую жизнь. Другой — несчастный юноша, что на своëм не малом веку познал боль и страдания
❤11💋8🔥8custom 54543672648516505354🍓1custom 54539308746995429061custom 54542387723150573741
🍃Обещаный спойлер🍃 Вы видела кота у Олежи, вы знаете что у Ари есть пëс и теперь я официально заявляю, что у Ангелины тоже есть свой питомчик. Это Шиш, еë ручной кролик 🐇 который не много появится в главе
🕊10🍓8❤7custom 54539308746995429063custom 54543672648516505352🔥1
— Рина обещала спойлер за фанарт. Я чёт ультанул и закончил за день... В общем, с Ангелиной теперь пьём чай из цветочных чашек и ждём 🪷🪷 tgs: #арт
custom 54543362895475111045❤4🍓2custom 54539308746995429062custom 54542387723150573742💘1custom 54543672648516505351
Скину ещё спойлеры если меня порадуете фанартиком 🥰 /да я мелкий вымагатель, знаю, каюсь, но мне нужна подпитка
❤13custom 54542387723150573744🍓3custom 54539308746995429061custom 54543672648516505351
Showing the 12 most recent of 19 posts we hold for @arina_cat18. 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 — 865,720 of 1,350,102entries 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
“🐈Artist от Рин🎨” (@arina_cat18), 216 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/arina_cat18.
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.