Channel
@kivishinfo
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
8subscribers
+0 since we began measuring on 6 October 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003629469916 |
|---|---|
| Type | Channel |
| Username | @kivishinfo |
| Created | 26 December 2025 — measured — dated from the channel’s first post |
| First recorded | 6 October 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 2 |
| On Telegram | t.me/kivishinfo |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Oct 2026, 10:22 | 8 | no change |
| 6 Oct 2026, 09:47 | 8 | first reading |
9 posts held, back to 26 December 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 page of 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 9 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 6 October 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.
117 reactions across 7 posts, in 14 distinct kinds. The most used accounts for 16.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5451650693741970909 | 19 | 16.2% | |
| custom 5390978804602674378 | 16 | 13.7% | |
| custom 5399826828074453970 | 16 | 13.7% | |
| custom 5406833487397290105 | 11 | 9.40% | |
| custom 5397905599008620365 | 8 | 6.84% | |
| custom 5406626448498783404 | 7 | 5.98% | |
| custom 5454420913288138797 | 7 | 5.98% | |
| custom 5847929922936378742 | 7 | 5.98% | |
| custom 5406776007849969078 | 5 | 4.27% | |
| custom 5406777399419372650 | 5 | 4.27% | |
| custom 5449413629961078121 | 5 | 4.27% | |
| 💘 | 5 | 4.27% | |
| 💩 | 4 | 3.42% | |
| ❤ | 2 | 1.71% |
Custom emoji. 11 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 are Telegram’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 7 of the 9 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 117 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 26 December 2025 to 12 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.
𑁍ࠜೄ ･ﾟˊˎ Your opinion of me! Очевидный хейт/засирание и спам будут удаляться (:˘∧˘:) Принимается и мнение о моей работе! ︵︵︵︵︵︵︵︵︵︵︵︵︵︵︵︵︵
custom 53909788046026743786custom 54516506937419709094💘2custom 53998268280744539702custom 54068334873972901052
☆҉ Where I work? ° ❁۪۪ ཻུ ♡ ͎ . ｡ ˚ ︵︵︵︵︵︵︵︵︵︵︵︵︵︵︵︵︵ @n25confession — owner @kanadecf — owner @mizukanadailycf — owner @leoneedcf — daily & mp admin @dlywxs — daily admin @pinkribbon_mizucf — daily admin @mmjdaily — daily admin Хотите нанять меня на админа по тейкам/дейли ? — пишите в лс! @kivishhh там будет подробнее про опыт и т. п (в приоритете секай/геншин тема) ꒰ ⸝⸝ˊ ᗜ ˋ⸝⸝ ꒱ ᐢ ♡ ︵︵︵︵︵︵︵︵︵︵︵︵︵︵︵︵︵ Cr on bann…
custom 53998268280744539706custom 54516506937419709094custom 53909788046026743782custom 54068334873972901052
♡LOVE list : ・゜♡・。。♡ @ bustishka🖤🖤 for my 🖤🖤 @ mikan ❌❌for my 🪻🪻 @ kora 🤍🤍for my🤍🤍 @ phantom 🤩🤩 for my 🤩🤩 @ my admins and subscribers ♡♡ !порядок не имеет значения ︵︵︵︵︵︵︵︵︵︵︵︵︵︵︵︵︵ Cr on banner: MIJE__001 on x
custom 53909788046026743785custom 54068334873972901054custom 53998268280744539702💘1custom 54516506937419709091
>>> ♡ Info ! 🤩🤩 :: kivish 🏁; 🏳️🌈 ; 29:07 :: kinns 🌟 🤩 🌟 🤩🤩 DM ; ANON DNI — do not interact : 🥹гомофобы ; —филия ; сексизм ; фаны мизитиллов ︵︵︵︵︵︵︵︵︵︵︵︵︵︵︵︵ • • .❛ ✿ ❜. • • Немного обо мне ₊˚•.🥹 𝕗andoms ★Favorite: Project sekai colourful stage ; genshin impact ; vocaloids ; alien stage ⋆ ˚｡⋆ ❦Others: адский босс, отель хазбин, млп, дом совы, дроны убийцы, человек бензопила, адский рай, стар …
custom 54516506937419709096custom 53909788046026743783custom 54068334873972901053💘2custom 53998268280744539702
Хочу поменять оформление, но старое удалять не буду !! Так что сейчас будет переоформа инфо 🤩
★кто вы для меня? 🤩
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
custom 54066264484987834045custom 54516506937419709093custom 54544209132881387973custom 53998268280744539702custom 54067760078499690782custom 54067773994193726502custom 54494136299610781212custom 58479299229363787422
Этот пост не является кинн листом!
custom 53979055990086203656custom 54494136299610781213custom 58479299229363787423custom 53998268280744539702custom 54067760078499690782custom 54544209132881387972
>>>info ! 💅💅 HI, мое имя: kivish (кивиш) 🏁 др: 29.07 kinns: 🌟 🌟 🤩🤩 🌸🌸🌸🌸🌸🌸 Немного обо мне: · Фандомы (не во всех могу состоять) 🤩 геншин, секай, вокалоиды, адский босс, отель хазбин, млп,дом совы, дроны убийцы, алиен стейдж, человек бензопила , адский рай, стар против сил зла, психоняшки, как стать волшебницей, моя любовь снова потеряла свои очки,первородный грех такопи, крд, осд, уцц, милграм, бс 🤩 · Любимые пев…
💩4custom 54067773994193726503❤2custom 54066264484987834042custom 54544209132881387972custom 58479299229363787422custom 53979055990086203651custom 54067760078499690781
Channel created
Showing the 9 most recent of 9 posts we hold for @kivishinfo. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
★кто вы для меня? 🤩
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 9 most recent posts we hold, published 26 December 2025 to 12 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“κɪνɪઽⲏ” (@kivishinfo), 8 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/kivishinfo.
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.