Telegram RegisterThe public register of Telegram
Telegram profile photo for Kiki Witch

Channel

Kiki Witch

@kiki_witch_owo

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

429subscribers

+1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002487592107
TypeChannel
Username@kiki_witch_owo
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/kiki_witch_owo

Growth

428429428.57 August 2026 — 428 subscribers8 August 2026 — 428 subscribers15 August 2026 — 429 subscribers7 August 202615 August 2026
3 measurements spanning 8 days, net +1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 428–429 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 20:26429+1
8 Aug 2026, 05:19428no change
7 Aug 2026, 18:02428first reading

Engagement

10 posts held, back to 16 March 2026the 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 30 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
12s
Average length
12s

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.

Reaction mix

1,163 reactions across 10 posts, in 9 distinct kinds. The most used accounts for 34.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 536183939282449975740034.4%
custom 524487837956336664020317.5%
🐳13912.0%
custom 52695662338328703221149.80%
custom 5244537505188949589816.96%
796.79%
custom 5321306832969422955605.16%
custom 5244831298131866287474.04%
custom 5242553367737154940403.44%

Custom emoji. 7 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 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 1,163reactions 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 16 March 2026 to 30 May 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.

Telegram Stars

Stars received
6
across the posts below
Posts paid on
1
of 10 we hold a reading for · 10%
Most on one post
6
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @kiki_witch_owo. 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 16 March 2026 to 30 May 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.

Recent posts

30 May 2026, 19:40 UTC≈2,300 views156 reactionsread 8 August 2026
Photo

Выложила в тт!!❕ #genshinimpact #chilumi

custom 526956623383287032279custom 524487837956336664037custom 536183939282449975729custom 532130683296942295510custom 52448312981318662871

7 May 2026, 12:30 UTC≈1,460 views104 reactionsread 8 August 2026
Photo

#Nagito_zine_wip 🍀

custom 536183939282449975753custom 524483129813186628726custom 524487837956336664022custom 52425533677371549403

7 May 2026, 12:26 UTC748 views19 reactionsread 8 August 2026

От меня брелочек со Слугой и цветная страничка 😉

custom 524487837956336664013custom 53618393928244997576

7 May 2026, 12:25 UTC688 views10 reactionsread 8 August 2026
Forwarded from @danganronpa_zinePhoto

✨✨✨ПРЕДЗАКАЗЫ NAGITO KOMAEDA ZINE ОТКРЫТЫ ✨✨✨ розыгрыш ЗИНА, ОРИГИНАЛЬНОЙ ФИГУРКИ И КУЧУ ПОДАРКОВ!!! Читать далее… ☆ Розыгрыш двух Зинов!!! В ВК и Тг (до 1-го июня) Что нужно сделать? Розыгрыш в Тг: Быть подписанным на наш Тг Написать поздравление для Нагито в честь дня рождения!/Написать что-то хорошее 🌟 Розыгрыш в ВК: https://vk.ru/wall-210886366_1645 ☆ О самом зине Более 80 страниц с фанфиками, скетчами и и

custom 53618393928244997577custom 52448783795633666403

4 May 2026, 17:05 UTC≈1,540 views170 reactionsread 8 August 2026
Photo

Зверята маленькие 🤩🤩🤩 #genshinimpact #chilumi

79custom 536183939282449975752custom 524255336773715494031custom 53213068329694229554custom 52448783795633666402custom 52695662338328703222

24 Apr 2026, 18:58 UTC824 views138 reactionsread 8 August 2026
Photo

Кстати, недавно у меня появился tomodachi life!! И там тоже чайлюмики 💞 (Отрывки из игры я показываю в своём щп)

🐳81custom 524487837956336664029custom 524483129813186628720custom 53618393928244997578

24 Apr 2026, 16:46 UTC≈2,480 views208 reactions6 Starsread 8 August 2026
Photo

Уже видели стрим?? 🥶 #genshinimpact #chilumi

custom 5361839392824499757118custom 524487837956336664053🐳28custom 53213068329694229557custom 52695662338328703222

7 Apr 2026, 11:21 UTC≈1,920 views167 reactionsread 8 August 2026
Photo

Снова кроссовер, сорри Теперь с Человеком Бензопилой ⛓ #genshinimpact #tartaglia

custom 536183939282449975787custom 524487837956336664043🐳30custom 52425533677371549406custom 53213068329694229551

1 Apr 2026, 04:48 UTC≈1,820 views149 reactionsread 8 August 2026
Video

Я больше не люблю чайлюми, теперь я шипперю- Выберите сами кого!! 👍 #genshinimpact #no_chilumi

custom 524453750518894958981custom 532130683296942295530custom 526956623383287032227custom 536183939282449975711

16 Mar 2026, 10:33 UTC≈1,060 views42 reactionsread 8 August 2026

Это мой первый адопт, поэтому я была бы очень рада вашим репостам!! Если здесь не получится, попробую походить по шопам 🍔 (А вот тут можно писать флуд)

custom 536183939282449975729custom 53213068329694229558custom 52695662338328703224custom 52448783795633666401

Showing the 10 most recent of 10 posts we hold for @kiki_witch_owo. 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

Citation-graph rank — 1,470,786 of 1,548,671entries 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.

Forward network

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.

Mentions

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.

Cite this entry

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 15 August 2026 — this entry's latest reading, not the date you are reading this.

“Kiki Witch” (@kiki_witch_owo), 429 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/kiki_witch_owo.

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.