Channel
@YoiGuaruu
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
288subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001796001537 |
|---|---|
| Type | Channel |
| Username | @YoiGuaruu |
| Created | Between 1 January 2022 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/YoiGuaruu |
Personal blog — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 23 September 2026 and assigned it the closest of 31 fixed categories, at 73% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 20:16 | 288 | -2 |
| 10 Sept 2026, 15:21 | 290 | +3 |
| 1 Sept 2026, 08:36 | 287 | -2 |
| 17 Aug 2026, 13:03 | 289 | +1 |
| 10 Aug 2026, 09:04 | 288 | no change |
| 9 Aug 2026, 20:47 | 288 | first reading |
13 posts held, back to 17 June 2026 — 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 13 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
175 reactions across 13 posts, in 8 distinct kinds. The most used accounts for 25.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5386641252705912984 | 44 | 25.1% | |
| custom 5355015007618753075 | 33 | 18.9% | |
| custom 5334835627764493719 | 26 | 14.9% | |
| custom 5314648353760364968 | 23 | 13.1% | |
| 💩 | 17 | 9.71% | |
| custom 5357413733968661216 | 16 | 9.14% | |
| custom 5389056265571814282 | 11 | 6.29% | |
| custom 5355148838799694591 | 5 | 2.86% |
Custom emoji. 7 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 13 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 175 reactions 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 17 June 2026 to 1 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.
привет 🤩 🥹мекап кривой пушта мне хотелось сделать пробник ,но было супергигаультрамега лень . я исправлюсь обещаю 🥹 #щэпэ
custom 53550150076187530759custom 53146483537603649682custom 53551488387996945911custom 53890562655718142821
Signed r!chr/i 【バラ】
Posted without readable text
custom 53866412527059129846💩4custom 53890562655718142823custom 53550150076187530752
Signed r!chr/i 【バラ】
Posted without readable text
💩6custom 53146483537603649682
Signed r!chr/i 【バラ】
я снова начинаю маяться чем то полезным вместо херни как обычно , на кого это не скажу :3 #щэпэ
custom 53574137339686612164💩2
Signed r!chr/i 【バラ】
🟢быстра проскочу по причине ,что я ахуела после мобиус ниче не делаю 😒 🍏я сижу ищу и фигачу выкройки НА 2 КОСТЮМА СРАЗУ , оченн сильно загорелась идейками ,МОЖЕТ БЫТЬ буду кидать спойлеры какие та , нооо те кто меня тут уже хорошо знают я ОЧЕНЬ ПРЯМ ЛЮБЛЮ не говорить о том ,что вас ждет и дропать вкуснятину (если мои работы правда хороши🌟) 🌿из фестов если успею хоть что то дошить — хотела бы податься на кицу пока что…
custom 53866412527059129848💩2custom 53348356277644937192custom 53574137339686612162custom 53146483537603649681
Signed r!chr/i 【バラ】
🔤🔤🔤🔤🔤 🔤🔤🔤🔤🔤🔤 ⭐️⭐️ ⭐️⭐️⭐️He was the only son in ⭐️⭐️⭐️⭐️⭐️ his family. From ⭐️⭐️⭐️⭐️⭐️a young age, ⭐️⭐️⭐️⭐️⭐️Edgar was interested in creativity, and he showed his exceptional talent to everyone he knew. ph: https://t.me/dadllla7ph #cosplay #edgarvalden рт/реакции!!🐰🐰
custom 53890562655718142825custom 53866412527059129842
Signed r!chr/i 【バラ】
🌿я хотела ещё давно написать об этом я очень сильно не перестаю восхищаться Пуэр потому , что этот фотограф РЕАЛЬНО ЧУВСТВУЕТ. Смотря на свои фотки , и на фотографии других людей кто берет услуги у этого фотографа, это просто шедевр . Я искренне очен рада, что нашла такого крутого фотографа ,который мне очень подходит и я в будущем буду переодически в потоке каких-нибудь скачков «о я хочу мегакрутойсупер фотос» выби…
custom 53348356277644937196💩3custom 53146483537603649683custom 53866412527059129841
Signed r!chr/i 【バラ】
⭐️🌸🤍🤍🌟🤍🤍🌸 🤍 🤍ph: Puer🍃 🤍 #КосплеЛизобаг
custom 535501500761875307518custom 535741373396866121610custom 53348356277644937198custom 53146483537603649682custom 53551488387996945911custom 53866412527059129841custom 53890562655718142821
Signed r!chr/i 【バラ】
ну кабута косплан ребята … 🥰я поздновато, но как вам вообще зомбистейдж ??? я вахуи честно
custom 53146483537603649685
Signed r!chr/i 【バラ】
МНЕ ОЧЕН ХИХИШНА И СТЫДНА ЗА ЭТУ ДЕФИЛЕШКУ 🤩но я вам ее так и не показала 🥶🥶 (пс песня не вяжется никак с сюжетом , припев только , тк опиралась на русский кавер) смеяться можно я очень сильно проебалась #КосплеЛизобаг
custom 53866412527059129847custom 53550150076187530754custom 53551488387996945913custom 53890562655718142821
Signed r!chr/i 【バラ】
ого скока вас пришло , приветтддддл
custom 53146483537603649685
Signed r!chr/i 【バラ】
ОТАКОТ СЕГОДНЯ #щпшко
custom 533483562776449371910custom 53866412527059129844
Signed r!chr/i 【バラ】
Showing the 12 most recent of 13 posts we hold for @YoiGuaruu. 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.
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.
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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“L!z0bAg?i” (@YoiGuaruu), 288 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/YoiGuaruu.
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.