Telegram RegisterThe public register of Telegram

Channel

Yumeno!

@YugiCosplay

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

323subscribers

+1 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-1002107042369
TypeChannel
Username@YugiCosplay
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live7 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/YugiCosplay

Growth

322323322.56 Aug 2026, 23:03 — 322 subscribers7 Aug 2026, 17:11 — 323 subscribers6 Aug 2026, 23:037 Aug 2026, 17:11
2 measurements taken within a single day, 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 322–323 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 17:11323+1
6 Aug 2026, 23:03322first reading

Engagement

13 posts held, back to 27 July 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
51.1%
avg views ÷ 323 subscribers
Avg views / post
165
12 posts measured
Reaction rate
17.7%
reactions ÷ views · ER floor
Posts in window
13
of 13 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 6 August 2026
Posts held13 (27 July 20266 August 2026)
Views total1,980
Reactions total351
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 23:03 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

351 reactions across 12 posts, in 10 distinct kinds. The most used accounts for 26.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53283037427164998439226.2%
custom 53303606326193263947721.9%
❤‍🔥4813.7%
308.55%
custom 5442949571036605784257.12%
custom 5458526223418274076257.12%
🍓205.70%
164.56%
🔥133.70%
💘51.42%

Custom emoji. 4 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 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 12 of the 13 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 351reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 27 July 2026 to 6 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.

Recent posts

6 Aug 2026, 18:58 UTC44 views18 reactionsread 6 August 2026
Photo

примерка! на фото рампо без плаща, а дзено без второго ремня🐱🐱🐱

4custom 53283037427164998434custom 53303606326193263944custom 54585262234182740764🍓2

4 Aug 2026, 19:05 UTC136 views56 reactionsread 6 August 2026
Photo

🍒🍒🍒🤩🍒🤩🤩🤩🍒🍒🍒🤩 ➿➿➿➿➿➿➿➿➿➿➿➿ — 𐌗ꤣӄꤌрγ! પተ꤀ ᤋተ꤀ ꤒખ𐌻꤀?🌟 — ϶ᴛи духи ᴏхᴏᴛяᴛᴄя ɜᴀ ᴛᴏбᴏй иɜ-ɜᴀ ᴏдинᴏчᴇᴄᴛʙᴀ.. иʍᴇннᴏ ᴨᴏ϶ᴛᴏʍу ᴄʍᴏᴛᴩи ᴛᴏᴧьᴋᴏ нᴀ ʍᴇня! ᴛᴏᴧьᴋᴏ я ʍᴏᴦу ɜᴀ ᴛᴇбя цᴇᴨᴧяᴛьᴄя.. 🌟 ᴨᴩᴏᴄᴧᴇжу чᴛᴏбы ᴇᴦᴏ нᴇ ᴏᴛᴏбᴩᴀᴧи.. 🌟 ➿➿➿➿➿➿➿➿➿➿➿➿ hikaru yoshiki ph/rt #hikaruindo

custom 533036063261932639419custom 532830374271649984318🔥12🍓2custom 544294957103660578421💘1custom 54585262234182740761

4 Aug 2026, 12:00 UTC85 views20 reactionsread 6 August 2026
Forwarded from @myaskoooiiPhoto

я и некая диша кор ❤️❤️❤️❤️

9custom 53283037427164998435custom 533036063261932639451

3 Aug 2026, 19:14 UTC115 views24 reactionsread 6 August 2026
Video

фан факт от меня в ближайшее время как вы могли заметить будет много бсд (дзено, чуя, рампо и ещё кое кто) #chuuyanakahara

❤‍🔥10custom 54585262234182740766custom 53283037427164998434custom 53303606326193263943🍓1

2 Aug 2026, 21:00 UTC255 views32 reactionsread 6 August 2026
Photo

➿➿➿➿➿➿➿➿➿➿➿➿ 📜📜📜➿➿➿📜📜📜📜📜📜 ➿➿➿➿➿➿➿➿➿➿➿➿ — Ты ɜʙᴏниᴧ ᴨᴏᴛᴏʍу чᴛᴏ ᴛᴇбᴇ ᴄᴨᴀᴛь нᴇᴦдᴇ.<...> Не хᴏди ʙᴏᴋᴩуᴦ дᴀ ᴏᴋᴏᴧᴏ, ᴀ ᴄᴨᴩᴏᴄи🌟 ➿➿➿➿➿➿➿➿➿➿ — Вᴏᴏу, чᴛᴏ ᴛы.. <...> А ϶ᴛᴏ нᴇ ᴄᴧиɯᴋᴏʍ ᴄᴧᴏжнᴏ?🌹 chuuya: yumeno shirase: рюша плюша #chuuyanakahara ртт

❤‍🔥12custom 53283037427164998438custom 53303606326193263945💘2custom 5458526223418274076211🍓1

1 Aug 2026, 17:58 UTC127 views22 reactionsread 6 August 2026
Photo

немного лайфа я переставила все фигурки и теперь их можно разглядеть без усилий раньше они лежали все в стопку и их не получалось рассмотреть, не отодвигая иногда стоит вам напоминать что я очень люблю шинсоукоку это чуть меньше половины всего того, что у меня есть с шинсоукоку, а в особенности с акутагавой #lifepost

8custom 53283037427164998436custom 53303606326193263944custom 544294957103660578421🍓1

1 Aug 2026, 13:34 UTC143 views29 reactionsread 6 August 2026
Photo

🤩🤩 #chuuyanakahara

custom 533036063261932639412custom 54429495710366057847custom 53283037427164998436❤‍🔥31

31 Jul 2026, 08:46 UTC158 views19 reactionsread 6 August 2026
Photo

🔠🔠🔠🔠🔠 🔠🔠 🔠🔠🔠🔠🔠 йохаа, 17 августа будет два фотоса, возьму немного сигн первая будет с фулл составом ВДА, где я буду за эдогаву ранпо соло сигны - 1/2 цена: 50 рублей  вторая будет в дзено соло сигна - 0/2 цена: 50 рублей заказать можно до 16 августа включительно! в ближайшее время будет примерка дзено, а ранпо ещё едет😒 писать @CosYugi #сигны

custom 533036063261932639410custom 53283037427164998435custom 54429495710366057843🔥1

30 Jul 2026, 23:19 UTC147 views26 reactionsread 6 August 2026
Video

скину кусочек🏷️ #hatsunemiku #дефиле

10custom 532830374271649984384custom 54429495710366057842custom 53303606326193263941custom 54585262234182740761

30 Jul 2026, 09:52 UTC155 views36 reactionsread 6 August 2026
Photo

💥💥💥 #mikantsumiki

❤‍🔥12custom 53283037427164998439custom 54585262234182740769🍓2💘21custom 53303606326193263941

28 Jul 2026, 01:11 UTC193 views41 reactionsread 6 August 2026

Posted without readable text

custom 533036063261932639411custom 532830374271649984310🍓8❤‍🔥6custom 54429495710366057843custom 545852622341827407621

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

Citation-graph rank

Citation-graph rank — 50,707 of 1,169,250entries 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

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

“Yumeno!” (@YugiCosplay), 323 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/YugiCosplay.

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.