аминь...🙂
custom 52154481899093673393custom 52155060560037419022

Channel
@qwakitty_0
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
13subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003369553570 |
|---|---|
| Type | Channel |
| Username | @qwakitty_0 |
| Description | ╭── ⋅ ⋅ ── ✩ ── ⋅ ⋅ ──╮ ᴋᴀнᴀᴧ ᴛоᴧьᴋо нᴀчᴀᴧ ᴩᴀзʙиᴛиᴇ. нᴀчᴀᴧо : 29.05.2026 ╰── ⋅ ⋅ ── ✩ ── ⋅ ⋅ ──╯ |
| Created | Between 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/qwakitty_0 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 03:46 | 13 | no change |
| 7 Aug 2026, 19:32 | 13 | first reading |
15 posts held, back to 29 May 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 15 posts for this entry, the most recent from 13 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
89 reactions across 10 posts, in 8 distinct kinds. The most used accounts for 19.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5386707197633796251 | 17 | 19.1% | |
| custom 5350361805690538576 | 16 | 18.0% | |
| custom 5215169094344538986 | 13 | 14.6% | |
| custom 5215448189909367339 | 13 | 14.6% | |
| custom 5215506056003741902 | 10 | 11.2% | |
| custom 5377396417205666725 | 8 | 8.99% | |
| custom 5348364899300966989 | 7 | 7.87% | |
| custom 5355292054484190534 | 5 | 5.62% |
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 15 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 89reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 29 May 2026 to 13 June 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.
аминь...🙂
custom 52154481899093673393custom 52155060560037419022
спойлеры...🌟
custom 52151690943445389862custom 52154481899093673392
кхе, перекид в более приятном виде...
custom 52151690943445389863custom 52154481899093673392custom 52155060560037419022
✅✅✅✅✅✅✅✅ Это место, где художники помогают художникам. Здесь Ты можешь самостоятельно показать свои работы, не дожидаясь очереди в основном канале. Никакой конкуренции - только взаимная поддержка и живые отклики! @ArtRise_prchat @ArtRise_prchat @ArtRise_prchat Перед входом прочитай правила, что бы ничего случайно не нарушить. Чат, где тебе всегда рады😛 Не забудь заглянуть в наш пиар-канал(8.8К)
☺️👍🙂👍 ☺️🙂☺️ Приветствую! 🐾 Это тот самый чат пиара от Сандры который вы возможно искали🥰 ❤️❤️❤️❤️❤️❤️❤️❤️❤️❤️ Здесь вы можете искать мью и репостить прочие посты со своего канала 🐈 Присоединяйтесь! 🥰 @sandra0piar @sandra0piar
➖➖➖➖➖➖➖для творчества 8,5к @piarchatartist Пиар разрешен для всего, бана нет Лучшая подборка для художника: ➡️Бесплатный пиар и арт коммьюнити 12к @piarhydozh ➡️Продвижение начинающих художников @artpiarr ➡️ Чаты самопиара ➡️Баттлы артов @otsenkaart ➡️Арт интерактивы, пиар ваших ивентов @artivent ➡️Арт коммьюнити и пиар для нсфв художников 18+ @kotenky АВТОР ОБЛОЖКИ @tattooaikaa
😀😀😀😀😀😀😀😀 😀😀😀😀😀😀😀😀 (Пиар чат) ↩️❤️❤️❤️❤️❤️❤️❤️❤️❤️❤️❤️↪️ ⭐️Здесь ты можешь делиться своими работами и находить подписчиков! @CreativeShowcase @CreativeShowcase @CreativeShowcase (Перед входом обязательно прочитай правила) А также не забудь подписаться на наш пиар канал Чат, где тебе всегда рады💃
🌟
custom 52155060560037419024custom 53503618056905385763custom 53867071976337962513
было ☑️ стало... это финальный вид маскота и финальный дизайн🐇
custom 53483648993009669893custom 53503618056905385762custom 53867071976337962512
...космо бойчик🫦
custom 52154481899093673394custom 53867071976337962514custom 53503618056905385763
что-то намечается...😊
custom 53552920544841905344custom 53773964172056667254custom 53483648993009669893custom 52151690943445389862custom 53503618056905385761
нарисовал все, только не персонажа..........
custom 53503618056905385764custom 53773964172056667253custom 53867071976337962512
Showing the 12 most recent of 15 posts we hold for @qwakitty_0. 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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“✧【 𝐒𝐩𝐚𝐬𝐞 𝐨𝐟 𝐀𝐬𝐭𝐫𝐚𝐥 】✧” (@qwakitty_0), 13 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/qwakitty_0.
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.