Video message, posted without a caption
custom 52808408665822528933custom 53755844392229422693custom 53057221275240545142

Channel
@kykyyyyyyyyyyu
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
62subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001518146415 |
|---|---|
| Type | Channel |
| Username | @kykyyyyyyyyyyu |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/kykyyyyyyyyyyu |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 04:01 | 62 | no change |
| 9 Aug 2026, 18:16 | 62 | first reading |
15 posts held, back to 14 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 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 15 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 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.
172 reactions across 14 posts, in 5 distinct kinds. The most used accounts for 25.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5375584439222942269 | 43 | 25.0% | |
| custom 5460742117305359123 | 41 | 23.8% | |
| custom 5305722127524054514 | 35 | 20.3% | |
| custom 5280840866582252893 | 27 | 15.7% | |
| custom 5274011327415730204 | 26 | 15.1% |
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 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 14 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 172 reactions 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 14 July 2026 to 9 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.
Video message, posted without a caption
custom 52808408665822528933custom 53755844392229422693custom 53057221275240545142
новая инфа: эвакуировали 420к человек
интересные истории: вчера мы должны были улетать в Шанхай , а оттуда в Моску ( сегодня мы уже должны были быть в мск), но , в Шанхае огромный тайфун , там уже эвакуировали около 100к человек и мы летели далеко не в Шанхай, а в другой город поблизости ( об этом мы узнали уже в аэропорту другого города) В итоге щас нас разместили в отели , покормили и сказали, что тайфун продлится до завтра , надеемся, что завтра будем…
custom 52740113274157302042custom 52808408665822528932custom 53057221275240545142
Posted without readable text
custom 53755844392229422695custom 52808408665822528934custom 54607421173053591234custom 52740113274157302041
потом в инсту закину все , щас так по вайбу
custom 52740113274157302045custom 53057221275240545144custom 53755844392229422694custom 54607421173053591233
Good morning, comrades🌟
custom 52740113274157302044custom 53755844392229422694custom 54607421173053591233
мы прибыли!!! Нячанг 😝
custom 53057221275240545146custom 52740113274157302044custom 54607421173053591234
Video message, posted without a caption
custom 52808408665822528936custom 53057221275240545146custom 54607421173053591236
все круто чуть не умерли от жары и нас почти развили на чай за 2300юаней
custom 53755844392229422698custom 54607421173053591234custom 53057221275240545143custom 52808408665822528932
щас пару суток тут гуляем по Шанхаю и едем дальше 🫡
custom 53755844392229422696custom 54607421173053591236custom 53057221275240545144
мы прилетели в китай , все кто в китае доброе утро, кто в мск доброй ночи 💤
custom 52808408665822528936custom 53755844392229422696custom 52740113274157302044
доброе утроу
custom 53057221275240545146custom 53755844392229422694custom 54607421173053591234
Showing the 12 most recent of 15 posts we hold for @kykyyyyyyyyyyu. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“lilasssssss” (@kykyyyyyyyyyyu), 62 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/kykyyyyyyyyyyu.
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.