Telegram RegisterThe public register of Telegram

Channel

YuKineda ✧

@yukineda

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

670subscribers

+26 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002257572332
TypeChannel
Username@yukineda
CreatedBetween 1 October 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/yukineda

Growth

6446706576 August 2026 — 644 subscribers6 August 2026 — 656 subscribers6 August 2026 — 656 subscribers13 August 2026 — 670 subscribers6 August 202613 August 2026
4 measurements spanning 7 days, net +26. 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 640–674 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 18:27670+14
6 Aug 2026, 17:18656no change
6 Aug 2026, 17:10656+12
6 Aug 2026, 09:36644first reading

Engagement

11 posts held, back to 7 May 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.

ERR · 30 days
54.2%
avg views ÷ 670 subscribers
Avg views / post
363
4 posts measured
Reaction rate
16.3%
reactions ÷ views · ER floor
Posts in window
4
of 11 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 5 August 2026
Posts held11 (7 May 20265 August 2026)
Views total1,453
Reactions total237
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 17:18 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

1,297 reactions across 11 posts, in 26 distinct kinds. The most used accounts for 15.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 537543093709178389620615.9%
custom 528085837286896831113810.6%
custom 54451587776596181341007.71%
custom 5384490702451275619937.17%
custom 5258166286822709397927.09%
custom 5195398049916016304705.40%
custom 5258138275046005869675.17%
custom 5402400466967491145584.47%
custom 5278554612540919225564.32%
custom 5222062332171019205493.78%
custom 5192806634153333882473.62%
custom 5357522667224193098423.24%
custom 5375157648322739592403.08%
custom 5445111846551973652372.85%
custom 5292025111744911070322.47%
custom 5375247035182101458302.31%
custom 5372980078428832431292.24%
custom 5411240703663561222262.00%
custom 5262687835118389710211.62%
custom 5373045284622320690201.54%
6 further kinds443.39%

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 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 11 of the 11 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,297reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 7 May 2026 to 5 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.

Telegram Stars

Stars received
60
across the posts below
Posts paid on
9
of 11 we hold a reading for · 82%
Most on one post
15
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @yukineda. 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 11 most recent posts we hold for this entry, published 7 May 2026 to 5 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.

Recent posts

5 Aug 2026, 19:27 UTC309 views102 reactions3 Starsread 6 August 2026
Photo

wip и скетчи

custom 540240046696749114558custom 519280663415333388223custom 522206233217101920518custom 51953980499160163043

5 Aug 2026, 11:00 UTC203 views4 reactionsread 6 August 2026
Forwarded from @shzhivinciPhoto

👱‍♀️😤💜🅰️🅰️🅰️🅰️🅰️🅰️🅰️🅰️ 😡👺🫸 ≈ 22,3к общейаудитории 😯👩‍🦲👨‍🦳 ⚔️ ⚔️🅰️🅰️🅰️🅰️🅰️🅰️🅰️ ⚔️ ⬅️Репост в тгк который пиарите 👤Подписка на: Инфер Нум Франц Нясимен Ригби Винчи 💬Скинуть до 4 артов и юз канала 05.08.2026 - 06.08.2026

custom 53731027856444770944

5 Aug 2026, 08:02 UTC264 views11 reactionsread 6 August 2026
Forwarded from @corpselllPhoto

🔤🔤🔤🔤🔤🔤🔤🔤 Аудитория 9к+🤩 ⛓️⛓️⛓️⛓️⛓️⛓️⛓️⛓️⛓️ УСЛОВИЯ: Подписка на авторов по желанию🤩 @onionchess @kosiposhenkaa @corpselll @alexgaimo2 • репост этого поста к себе в тгк • скинуть пруф репоста в комментарии и свои работы с ссылкой на канал через @  ищите мью, крутых художников, репостить будем подборками, ии слоп и срисовки не принимаются 🤩

custom 53731027856444770948custom 52220623321710192052custom 51928066341533338821

2 Aug 2026, 14:07 UTC677 views120 reactions6 Starsread 6 August 2026

Posted without readable text

custom 519539804991601630467custom 522206233217101920529custom 519280663415333388220custom 53731027856444770944

13 Jul 2026, 21:04 UTC≈3,930 views109 reactions5 Starsread 6 August 2026
Photo

🤩#PortfolioDay 🙂🙂🙂🙂🙂🙂

custom 527855461254091922553custom 525813827504600586934custom 525816628682270939719custom 51928066341533338823

8 Jul 2026, 14:53 UTC≈1,140 views129 reactions15 Starsread 6 August 2026
Photo

🌟🌟🌟🌟🌟🌟🌟🌟 🌟моя работа на палитру

custom 525816628682270939773custom 525813827504600586933custom 537304528462232069020custom 52785546125409192253

23 Jun 2026, 18:20 UTC≈1,440 views187 reactions10 Starsread 6 August 2026
Photo

🥀🥀⭐⭐⭐⭐⭐⭐⭐⭐ 🥀🥀🙂🙂🙂🙂🙂🙂🙂🙂 🥀🥀🌟🌟🌟🌟🌟🌟🌟🤩

custom 5445158777659618134100custom 528085837286896831148custom 544511184655197365237custom 54453077743700826152

17 Jun 2026, 13:23 UTC≈1,340 views174 reactions7 Starsread 6 August 2026
Photo

🌟🌟🌟🌟🌟

custom 538449070245127561993custom 537543093709178389645custom 529202511174491107032custom 53844197281167076944

4 Jun 2026, 18:57 UTC≈1,860 views165 reactions11 Starsread 6 August 2026
Photo

🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 🤩🤩🤩🤩🤩🤩🤩🤩🤩 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟

custom 528085837286896831190custom 537515764832273959240custom 537524703518210145830custom 52042371484457654595

23 May 2026, 10:41 UTC≈1,630 views122 reactions2 Starsread 6 August 2026
Photo

🔠🔠🔠 и скетчи из щп 🖤

custom 537543093709178389668custom 541124070366356122226custom 526268783511838971021custom 53731737814538796455custom 53575226672241930981custom 53728911124762613511

7 May 2026, 18:15 UTC≈2,030 views174 reactions1 Starread 6 August 2026
Photo

🌟🌟🌟🌟 быстрый стадик 🌟🌸🌸🌸🌸🌸 🌟🌟🌟🌟🌟🌟

custom 537543093709178389693custom 535752266722419309841custom 537298007842883243129custom 53731737814538796457custom 53728911124762613514

Showing the 11 most recent of 11 posts we hold for @yukineda. 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 — 380,958 of 1,480,688entries 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

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.

Mentions

Named by 7 registered channels — 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.

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

“YuKineda ✧” (@yukineda), 670 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/yukineda.

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.