Telegram RegisterThe public register of Telegram

Channel

MOVE & REDEBUT.

@yeoniversee

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry

113subscribers

+0 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1002614820095
TypeChannel
Username@yeoniversee
DescriptionWelcome to 𝓨eoniverse a soft space where hearts feel lighter and words bloom quieter. archive: @yeoniversearchive bot : @yeoniverseebot we're since 26/07/25 👱🏻‍♀️🩷
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
On Telegramt.me/yeoniversee

Growth

11312 Aug 2026, 09:31 — 113 subscribers12 Aug 2026, 09:45 — 113 subscribers12 Aug 2026, 09:3112 Aug 2026, 09:45
2 measurements taken within a single day. 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 112–114 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 09:45113no change
12 Aug 2026, 09:31113first reading

Engagement

16 posts held, back to 8 August 2025the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 16 posts for this entry, the most recent from 8 October 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
20
Videos
4
Links
11

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
1m 29s
Average length
30s

Measured directly from 3 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.

Reaction mix

151 reactions across 5 posts, in 5 distinct kinds. The most used accounts for 26.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53057151610871107794026.5%
custom 52851841565553067453825.2%
custom 52740028792150677373321.9%
custom 52585004009185872413221.2%
custom 544073914034790772285.30%

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

Measured over the 16 most recent posts we hold, published 8 August 2025 to 8 October 2025, 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
4
across the posts below
Posts paid on
3
of 16 we hold a reading for · 19%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @yeoniversee. 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 16 most recent posts we hold for this entry, published 8 August 2025 to 8 October 2025. 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

8 Oct 2025, 11:53 UTC670 viewsread 12 August 2026

hello everyone! we’d like to share an important announcement. starting today, we’ll be moving to a new channel. this means this one will no longer be in use. there are a few reasons behind this move that we can’t fully explain, but along with it, we’ll also be redebuting. all yeoniverse members have already left or unsubscribed your channel, so we’ll be doing an sfs reset on our new one. for those who’d still like

Signed Meidiana.

3 Oct 2025, 13:42 UTC675 viewsread 12 August 2026
Forwarded from @SushiUniverse

Hey, Sushibee! We’re opening a little space in Yeoniverse for Yeonju Protayers who shine in pink hues and gentle sparkles. If you’re the type who loves soft chats, sprinkles of laughter, and cozy friendships that feel like a magazine cover moment, you’ll blend perfectly with us ✌️🏻🩷 Let's join our chapter, and paint these pages in shades of pink together <,33

27 Sept 2025, 04:23 UTC587 viewsread 12 August 2026

[ Yeoniverse Update ] we’ll be holding SFS for a while. apologies to those who’ve already reached our bot — we haven’t been able to process it due to some members being busy or inactive lately. thank you for your patience & understanding, we’ll get back to you soon 💌

26 Sept 2025, 14:17 UTC635 viewsread 12 August 2026
Photo

CHAPTER II — EVER AFTER BLOOM. time keeps moving, but my heart stays gentle with you

22 Sept 2025, 14:51 UTC570 viewsread 12 August 2026

Hello, beautiful souls! We’d like to let you know that our bot has officially moved from @yeoniverseebot to @yeoniverserobot. We sincerely apologize for any messages left unanswered on the previous bot — we truly appreciate every single reach you’ve made, and we’re so sorry if it couldn’t be replied properly before. From now on, kindly send all your lovely words, stories, and confessions to our new bot. We’ll make s

25 Aug 2025, 18:44 UTC≈1,130 views29 reactions1 Starread 12 August 2026
Video

CHAPTER I — STILL ADORE YOU. this is how Yeoniverse began. and here i am, still saying it: i adore you, every piece of you.

custom 530571516108711077912custom 52740028792150677378custom 52585004009185872416custom 52851841565553067453

25 Aug 2025, 17:00 UTC575 views16 reactions1 Starread 12 August 2026

HAPPY MENSIVE YEONIVERSE

custom 52851841565553067456custom 53057151610871107794custom 52585004009185872413custom 52740028792150677373

10 Aug 2025, 12:45 UTC≈1,410 views40 reactionsread 12 August 2026
Photo

From the first drop to the last beat, 18 of us are here to own the scene. Bigger, louder, bolder—this is Yeoniverse.

custom 528518415655530674515custom 525850040091858724110custom 52740028792150677378custom 53057151610871107797

Showing the 12 most recent of 16 posts we hold for @yeoniversee. 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 — 1,426,631 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

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 3 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.

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.

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

“MOVE & REDEBUT.” (@yeoniversee), 113 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/yeoniversee.

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.