Telegram RegisterThe public register of Telegram
Telegram profile photo for архив ! ⌒⌒ ‎ׁ ოׄiyuta's café 🎐🍡 ⋋_⋌

Channel

архив ! ⌒⌒ ‎ׁ ოׄiyuta's café 🎐🍡 ⋋_⋌

@yumemizukihugger

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

46subscribers

-4 since we began measuring on 9 August 2026

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

Register entry

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

Growth

4650489 August 2026 — 50 subscribers10 August 2026 — 50 subscribers16 August 2026 — 48 subscribers30 August 2026 — 47 subscribers15 September 2026 — 46 subscribers9 August 202615 September 2026
5 measurements spanning 37 days, net -4. 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 45–51 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 16:0046-1
30 Aug 2026, 09:2947-1
16 Aug 2026, 17:0348-2
10 Aug 2026, 12:0050no change
9 Aug 2026, 10:5450first reading

Engagement

20 posts held, back to 4 October 2025 — 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 20 posts for this entry, the most recent from 1 January 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
16s
Average length
16s

Measured directly from 1 video 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

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52288676262471519738020.2%
custom 52288898312280742527218.2%
custom 53256695490795557825914.9%
custom 53301543754048782915814.6%
👾276.82%
custom 5330122438028067002256.31%
🍓256.31%
custom 5325601619876805801184.55%
💘174.29%
custom 5327933619614809217133.28%
custom 522906090836541251610.253%
custom 533024309224934892510.253%

Custom emoji. 9 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 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 10 of the 20 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 396 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 4 October 2025 to 1 January 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

1 Jan 2026, 22:16 UTC342 views33 reactionsread 10 August 2026

ребят ну мой лив с сшкм еще можнл проигнорировать , но проигнорить годовщину это как то совсем обидно idk, ty что ли 🤩

custom 533015437540487829113👾10custom 52288676262471519736custom 53256695490795557823custom 52288898312280742521

31 Dec 2025, 21:35 UTCviews —

Channel name was changed to «архив ! ⌒⌒ ‎ׁ ოׄiyuta's café 🎐🍡 ⋋_⋌»

31 Dec 2025, 21:01 UTC356 views43 reactionsread 10 August 2026

⌒꯭⌒ это не все ࣭ ࣭ ୨ৎ ── я давно думала об этом и я приняла решение покинуть сшкм 😢 . в последнее время я не сижу в различных кфшках и существую только в пределах своего канала и каналов мьюшек . 😢 . да и на первое сил у меня нет , да и если честно , не чувствую отдачи . ( это мои тараканы в голове , ввы не виноваты ) этот чаннел я оставляю архивником и изредка буду заливать суда какие либо посты…

custom 522886762624715197313custom 532566954907955578213custom 522888983122807425212👾2🍓1💘1custom 53301543754048782911

31 Dec 2025, 21:00 UTC308 views83 reactionsread 10 August 2026
Photo

ㇻ ; 🌟 ࣪ HAPPY NEW YEAR › ‌‹ 𝅄 . . and 1 year together ! ♡゙‌ ׅ ᧓︵︵   ♡ ‌ ◝ всех сразу же поздравляю с праздником , с уже наступившим счастливым новым годом ! 🌟. для меня этот день еще более необычный , ведь именно 1 января я впервые увидела сливы с наизамечательной мидзуки и без раздумий влюбилась в ее нежнейший образ :з . именно первое января я считаю нашей с ней годовщиной и я бесконечно рада , что…

custom 522888983122807425224custom 522886762624715197322custom 532566954907955578222custom 53301543754048782917👾4💘3🍓1

27 Dec 2025, 14:49 UTC246 views25 reactionsread 10 August 2026
Video

ㇻ ; 🌟 ࣪ ྀིnew sweetness › ‌‹ 𝅄 #miyumizu ♡゙‌ ׅ ᧓︵︵︵   ♡ ‌ ◝ я думала , что до нового года не будет постов , но мицуки решила иначе ^q^ ྀི𓈒 ׄ ׅ ꒰ ニャー ꒱ ᜔ ׄ 🍡 ᨴ ПОСМОТРИТЕ КАКОЕ НЕЖНОЕ ВИДЕО СДЕЛАЛА ЛИНЕТТ КИССЕРША . я ей руки целовала , это нереально мило , как мягкое данго ! 🌟 ՞߹ - ߹՞ . ice - cream #edit

custom 53256016198768058019custom 53256695490795557827custom 53301543754048782916👾1💘1custom 52288898312280742521

6 Dec 2025, 19:00 UTC301 views36 reactionsread 10 August 2026
Photo

ㇻ ; 🌟 ࣪ ྀིnew sweetness › ‌‹ 𝅄 #miyumizu ♡゙‌ ׅ ᧓︵︵︵   ♡ ‌ ◝ 🌟 . достаточно похож на тебя ? ? или больше на я - тяна ? ? ྀི𓈒 ♡ ‌ ◝ 🌟 . hmm . . смотря кого из нас ты пыталась слепить ! ྀི𓈒 ׄ ׅ ꒰ ニャー ꒱ ᜔ ׄ 🍡 ᨴ с небольшой задержкой , поздравляю вас с наступлением не только наихолодного , но и наиволшебным времени года ! совсем скоро наступит новый…

custom 52288898312280742529custom 53256016198768058019custom 52288676262471519738🍓4custom 53301543754048782913👾1custom 52290609083654125161custom 53256695490795557821

22 Nov 2025, 17:19 UTC272 views9 reactionsread 10 August 2026
Forwarded from @selfsplovePhoto

私の美しい娘たちと妻たち、マルちゃん、ハナビちゃん、ミユタちゃん まさかの、夢見月美月 ⸝⸝ㅤׁ @Sshiplcm_bot 𔓕 #тейк

👾5🍓4

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

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

“архив ! ⌒⌒ ‎ׁ ოׄiyuta's café 🎐🍡 ⋋_⋌” (@yumemizukihugger), 46 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/yumemizukihugger.

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.