Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝆹𝅥 𝆭 yasuragi ˗ ˏˋ🍸ˎˊ ˗

Channel

𝆹𝅥 𝆭 yasuragi ˗ ˏˋ🍸ˎˊ ˗

@uponiin

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

200subscribers

-5 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002627272519
TypeChannel
Username@uponiin
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live22 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/uponiin

Growth

200205202.57 August 2026 — 205 subscribers8 August 2026 — 204 subscribers8 August 2026 — 204 subscribers15 August 2026 — 203 subscribers22 August 2026 — 200 subscribers7 August 202622 August 2026
5 measurements spanning 15 days, net -5. 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 199–206 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 07:27200-3
15 Aug 2026, 10:57203-1
8 Aug 2026, 11:18204no change
8 Aug 2026, 04:25204-1
7 Aug 2026, 16:12205first reading

Engagement

8 posts held, back to 12 November 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 8 posts for this entry, the most recent from 3 December 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

320 reactions across 8 posts, in 24 distinct kinds. The most used accounts for 9.38% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5213173648243847389309.38%
custom 5310127166241924193226.88%
custom 5377637244611873840206.25%
custom 5242503636310851533185.63%
custom 5190475188466110080175.31%
custom 5379971318819093905175.31%
custom 5460648040341733638165.00%
custom 5208661707789978236154.69%
custom 5217518299721521401154.69%
custom 5310230911176956722154.69%
custom 5312164531223416348134.06%
custom 5246930106915504535123.75%
custom 5382000733816127017123.75%
custom 5449454900301829996123.75%
custom 5204330886107003291103.13%
custom 5312528649960839491103.13%
custom 5332738313629490372103.13%
custom 5380089018102870886103.13%
custom 520208960037325743392.81%
custom 539544616759095069692.81%
4 further kinds288.75%

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

Measured over the 8 most recent posts we hold, published 12 November 2025 to 3 December 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.

Recent posts

3 Dec 2025, 15:57 UTC515 views63 reactionsread 8 August 2026
Photo

⋆ мы всегда можем начать всё заново — 📸📚 выбрать новый стиль、убрать ненужные знакомства и привычки、простить себя за ошибки、начать изучать новые языки、завести хобби

custom 521317364824384738930custom 524250363631085153318custom 531023091117695672215

1 Dec 2025, 17:03 UTC496 views44 reactionsread 8 August 2026
Photo

🤍🧦 прощаюсь с осенью и приветствую зиму ꩜ уже предвкушаю как буду идти по улице и "хрустеть" снежными хлопьями, как буду украшать ёлку и дом к рождеству, перебирать теплые свитера, лепить снеговика, а когда замёрзну прибегу домой греться горячим какао

custom 531012716624192419322custom 544945490030182999612custom 531252864996083949110

29 Nov 2025, 18:28 UTC554 views36 reactionsread 8 August 2026
Photo

ᬊ my 9 reasons to live 🍵🤍 друзья семья музыка и хобби животные поездки заграницу разговоры по душам с подругой фотографии где я по-настоящему счастлива чай с мятой духи с ароматом чистоты

custom 537763724461187384020custom 53010287289969121458custom 54700547918140854008

25 Nov 2025, 16:27 UTC415 views35 reactionsread 8 August 2026
Photo

ㅤ✶ и вот наступают те деньки когда полностью все окутывается туманом, хочется поскорее укутаться в плед, заварить крепкий чай и сидеть дома пересматривая детские фотографии🤩🤎

custom 546064804034173363816custom 520433088610700329110custom 52020896003732574339

22 Nov 2025, 09:28 UTC361 views34 reactionsread 8 August 2026
Photo

˗ˏˋ🤩🤩ˎˊ˗ Фуросики [風呂敷] — буквально переводится как «банный коврик» 🤩🤩 квадратный кусок ткани、который использовался для заворачивания и переноски предметов любых форм и размеров。

custom 521751829972152140115custom 533273831362949037210custom 53954461675909506969

19 Nov 2025, 07:34 UTC391 views42 reactionsread 8 August 2026
Photo

˗ˏˋ надеюсь когда ты смотришь на лилии、читаешь японские книги、кормишь оленей и смотришь ведьмину службу доставки то ты вспоминаешь меня 🥢🤩 ˎˊ˗

custom 519047518846611008017custom 531216453122341634813custom 524693010691550453512

15 Nov 2025, 16:28 UTC401 views39 reactionsread 8 August 2026
Photo

🤩⛩️перед входом в японский храм расположен павильон для омовения тэмидзуя、где посетители дꪮлжны очистить тело и разум、что бы почувствовать спокойствие ࿐

custom 537997131881909390517custom 538200073381612701712custom 538008901810287088610

12 Nov 2025, 17:23 UTC439 views27 reactionsread 8 August 2026
Photo

🤩🤩🪷 настоящий glow up это когда перестаешь опираться на чужие стандарты, заботишься о своем здоровье, не подстраиваешься под других, живёшь своей жизнью и наслаждаешься каждым моментом

custom 520866170778997823615custom 54696354784519412817custom 52942886153444565915

Showing the 8 most recent of 8 posts we hold for @uponiin. 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 — 973,276 of 1,584,420entries 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.

Mentions

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

Named by

Channels on the register whose posts name this channel's handle.

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

“𝆹𝅥 𝆭 yasuragi ˗ ˏˋ🍸ˎˊ ˗” (@uponiin), 200 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/uponiin.

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.