Telegram RegisterThe public register of Telegram
Telegram profile photo for ini adalah Kai

Channel

ini adalah Kai

@kaiviey

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

3subscribers

+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-1001514418479
TypeChannel
Username@kaiviey
Created13 June 2023measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live19 September 2026
Measurements held3
Confirmed unchanged5 times, most recently 19 September 2026
On Telegramt.me/kaiviey

Growth

232.57 August 2026 — 2 subscribers14 August 2026 — 2 subscribers16 August 2026 — 3 subscribers7 August 202616 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 2–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 03:293+1
14 Aug 2026, 05:172no change
7 Aug 2026, 16:122first reading

Engagement

14 posts held, back to 13 June 2023the 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 14 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
7s
Average length
7s

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.

Recent posts

6 Aug 2026, 12:53 UTC9 viewsread 14 August 2026
Forwarded from @StudentCommitteeHSCPhoto

ㅤㅤ 𝐂𝐎𝐍𝐆𝐑𝐀𝐓𝐔𝐋𝐀𝐓𝐈𝐎𝐍 𝐅𝐎𝐑 𝐂𝐇𝐎𝐒𝐄𝐍 𝐒𝐓𝐔𝐃𝐄𝐍𝐓 𝐂𝐎𝐌𝐌𝐈𝐓𝐓𝐄𝐄 ₊˚. 🔍 This certificate recognizes to [KAIVIEY LYAN MARVEZ] For outstanding performance as an "Creative" Through persistent inquiry and brilliant deduction.ᐟ  ㅤㅤ﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌ ྀ࿐

30 Jul 2026, 07:24 UTC14 viewsread 14 August 2026
Forwarded from @HSCRAVENCLAWPhoto

👻😇🥰😘🌟💩✍️🍡🎈 ─── ⚫️ Beyond the gilded gates and beneath the crystal lit heavens, the Princesses and Princes have gracefully gathered within the grandeur of the castle. Here, where marble halls echo with gentle laughter and chandeliers cradle the glow of countless dreams, peace blossoms like an eternal spring. May every shared conversation become a cherished memory, every smile adorn the halls like precious jewel

29 Jul 2026, 19:47 UTC14 viewsread 14 August 2026
Forwarded from @CordeliapalaisPhoto

When you believe in a thing, believe in it all the way, implicitly and unquestionable. - Walt Disney Sejalan banget sama mbah kung Walt, soalnya untuk urusan anak pendiam Ravenclaw emang kalah, tapi urusan menang Ravenclaw gak pernah diam, chann💜 Special tag anak-anak buwung riweuh: @kratingrt @RambuAnarki @yhint @pristwine @soullyoonseol @siBarbbie @catspie @kaimarvez @supherficial @Joongrachenz @wishperly @Lumire

27 Jul 2026, 11:09 UTC53 viewsread 14 August 2026
Photo

Tim Ravenclaw🫵🏻😏 Special tag : @Kai @Anne @Aev @Kiri

Showing the 12 most recent of 14 posts we hold for @kaiviey. 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.

Forward network

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.

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

“ini adalah Kai” (@kaiviey), 3 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/kaiviey.

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.