▪️▪️▪️▪️🤍 🌟🌟🌟 ▪️▪️▪️▪️🤍 🌟🌟🌟🤩 ▪️▪️▪️▪️🤍 🤩🤩🤩🤩 ▪️▪️▪️▪️🤍 🤩🤩🤩🤩 🤩🤩🤩🤩 Условия: рк на пост , пост
Signed may

Channel
@luv_yukii
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
404subscribers
+4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002007252582 |
|---|---|
| Type | Channel |
| Username | @luv_yukii |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/luv_yukii |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 22 September 2026 and assigned it the closest of 31 fixed categories, at 80% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 18:18 | 404 | -7 |
| 5 Sept 2026, 17:55 | 411 | +2 |
| 28 Aug 2026, 01:57 | 409 | -1 |
| 21 Aug 2026, 12:55 | 410 | +8 |
| 14 Aug 2026, 22:38 | 402 | +2 |
| 8 Aug 2026, 05:48 | 400 | no change |
| 7 Aug 2026, 18:45 | 400 | first reading |
12 posts held, back to 29 June 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 12 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 9 videos 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.
204 reactions across 6 posts, in 9 distinct kinds. The most used accounts for 14.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5420332638328088602 | 30 | 14.7% | |
| custom 5231305247820892417 | 28 | 13.7% | |
| custom 5188612229221615485 | 27 | 13.2% | |
| custom 5190502792220937032 | 25 | 12.3% | |
| custom 5366122729349080506 | 25 | 12.3% | |
| custom 5393364332518074395 | 24 | 11.8% | |
| custom 5391324828642856793 | 21 | 10.3% | |
| custom 5332631042526302561 | 20 | 9.80% | |
| custom 5188704729932246346 | 4 | 1.96% |
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 6 of the 12 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 204 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 29 June 2026 to 7 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @luv_yukii. 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 12 most recent posts we hold for this entry, published 29 June 2026 to 7 August 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.
▪️▪️▪️▪️🤍 🌟🌟🌟 ▪️▪️▪️▪️🤍 🌟🌟🌟🤩 ▪️▪️▪️▪️🤍 🤩🤩🤩🤩 ▪️▪️▪️▪️🤍 🤩🤩🤩🤩 🤩🤩🤩🤩 Условия: рк на пост , пост
Signed may
Коллаб с брадком 🤩 @ownerslabyy
Signed 𓆩282 УК РФ𓆪
𝔁𝓷𝓵𝔂 & 𝓴𝓸𝓽𝓮𝓲𝓴𝓪 🙌🏻
Signed 𝐱𝐧𝐥𝐲¿
Мои крохи чучи ❤️ https://vt.tiktok.com/ZS44g1Bja/
Signed BALALAIKA
люблю и не могу отпустить😭 тт kroxa_boshhh
Signed кроха
ну я🤩 фон юны
custom 54203326383280886027custom 52313052478208924174custom 53661227293490805064custom 51905027922209370323custom 53933643325180743952custom 51886122292216154851custom 53913248286428567931
Signed yuki
адм, читайте правила, там написано продажи запрещены, я скоро буду снимать за нарушение правил.
Signed yuki
🧛♀ фон юны
custom 51886122292216154859custom 51905027922209370326custom 53933643325180743956custom 53326310425263025614custom 52313052478208924172custom 53661227293490805061custom 53913248286428567931custom 54203326383280886021
Signed yuki
факты 🌟 фон юны
custom 51886122292216154856custom 51905027922209370325custom 53326310425263025615custom 53913248286428567933custom 53661227293490805062custom 54203326383280886022custom 52313052478208924171custom 53933643325180743951
Signed yuki
с днём рождения меня получает☺️
custom 52313052478208924176custom 53933643325180743956custom 53913248286428567935custom 53661227293490805063custom 51905027922209370322custom 51886122292216154851custom 53326310425263025611custom 54203326383280886021
Signed yuki
🤗 фон юны
custom 523130524782089241710custom 53661227293490805068custom 54203326383280886027custom 53326310425263025615custom 51886122292216154854custom 51887047299322463464custom 51905027922209370324custom 53933643325180743953
Signed yuki
вайбик присутствует
custom 542033263832808860212custom 53913248286428567939custom 53661227293490805067custom 51886122292216154856custom 53933643325180743956custom 51905027922209370325custom 52313052478208924175custom 53326310425263025615
Signed yuki
Showing the 12 most recent of 12 posts we hold for @luv_yukii. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“yuᴋi luv yuᴩi” (@luv_yukii), 404 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/luv_yukii.
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.