Telegram RegisterThe public register of Telegram
Telegram profile photo for Yoko no Hanashi

Channel

Yoko no Hanashi

@yokonohanashi

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

2,209subscribers

+115 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002132357893
TypeChannel
Username@yokonohanashi
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live30 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/yokonohanashi

Growth

2,0872,2092,1487 August 2026 — 2,094 subscribers7 August 2026 — 2,094 subscribers8 August 2026 — 2,095 subscribers11 August 2026 — 2,087 subscribers15 August 2026 — 2,089 subscribers18 August 2026 — 2,112 subscribers20 August 2026 — 2,159 subscribers24 August 2026 — 2,180 subscribers27 August 2026 — 2,200 subscribers30 August 2026 — 2,209 subscribers7 August 202630 August 2026
10 measurements spanning 22 days, net +115. 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 2,069–2,227 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 00:382,209+9
27 Aug 2026, 04:062,200+20
24 Aug 2026, 09:142,180+21
20 Aug 2026, 22:112,159+47
18 Aug 2026, 07:222,112+23
15 Aug 2026, 02:162,089+2
11 Aug 2026, 16:312,087-8
8 Aug 2026, 07:222,095+1
7 Aug 2026, 20:322,094no change
7 Aug 2026, 18:152,094first reading

Engagement

16 posts held, back to 1 April 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 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 16 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
31s
Average length
16s

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.

Reaction mix

1,660 reactions across 16 posts, in 5 distinct kinds. The most used accounts for 63.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1,05763.7%
🔥24514.8%
🥰19611.8%
👍1599.58%
👎30.181%

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 16 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 1,660 reactions 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 1 April 2026 to 31 July 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.

Telegram Stars

Stars received
58
across the posts below
Posts paid on
8
of 16 we hold a reading for · 50%
Most on one post
33
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @yokonohanashi. 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 1 April 2026 to 31 July 2026. 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

31 Jul 2026, 19:22 UTC≈1,220 views168 reactions1 Starread 7 August 2026
Photo

😊Игра на рекордной скидке в 60%! Ссылка на страницу стим

🥰11433🔥21

10 Jul 2026, 17:59 UTC≈3,910 views87 reactions1 Starread 7 August 2026

Листик (один из создателей Yoko no Hanashi, сценарист, автор всех персонажей бла бла бла) стримит на твиче! Заходите! Можно задавать вопросики по игре. https://www.twitch.tv/listtravki

70🔥17

5 Jul 2026, 13:13 UTC≈4,650 views335 reactions15 Starsread 7 August 2026
Photo

Уже 5000 человек купили игру в Steam! Спасибо за поддержку!

282🥰28🔥24👍1

30 Jun 2026, 12:25 UTC≈4,710 views123 reactions1 Starread 7 August 2026
Photo

День 2. Ну и конечно же Йоко!

109🔥14

29 Jun 2026, 21:22 UTC≈4,160 views72 reactionsread 7 August 2026

Саундтрек вышел на площадки! https://band.link/uzTww

57🔥15

29 Jun 2026, 13:04 UTC≈3,620 views108 reactions5 Starsread 7 August 2026
Photo

😊Если вы помните, мы устраивали конкурс творчества в честь выхода игры в стим.😊 Прольем свет на истину, секретным призом для победителя был физический мини артбук. И теперь, спустя время, мы бы хотели поделиться с вами некоторыми страницами оттуда. День 1. Йото

👍6732🔥8🥰1

25 Jun 2026, 17:02 UTC≈3,480 views61 reactionsread 7 August 2026
Photo

☀️ ЛЕТНЯЯ РАСПРОДАЖА В СТИМ НАЧАЛАСЬ ☀️ В честь этого на протяжении всей распродажи на игру действует скидка 55%!!! 😊 ССЫЛКА НА СТРАНИЦУ ИГРЫ 😊 (Распродажа длится 14 дней, с 25 июня по 9 июля)

53🔥8

24 Jun 2026, 14:17 UTC≈3,150 views100 reactionsread 7 August 2026
Photo

#новость Актер озвучки Йото играет с Йото! Трансляция уже идет!

🔥6919🥰7👍5

22 Jun 2026, 23:15 UTC≈3,330 views64 reactions1 Starread 7 August 2026
Photo

#новость Новый патч 2.1.1 Изменения и исправления: - Исправлен баг, когда концовка Йото под номером 2, могла не сохранится - Исправлен баг, когда загрузка сохраненных настроек могло привести к некорректной работе игры - Изменено управление на геймпаде во время открытой панели с телефоном Йото Совсем скоро, а именно 25 июня начнется летняя распродажа в steam! И естественно игра в ней участвует. Более точную инфо

🔥4017👍7

11 Jun 2026, 20:07 UTC≈3,410 views61 reactions33 Starsread 7 August 2026
Photo

#новость Новый патч 2.1.0 Изменения и исправления: - Игрок может погладить яндере и задобрить их. Погладить их можно, если они находятся в состоянии после атаки или в состоянии оглушения - Яндере могут отреагировать на попытку игрока спрятаться в шкафу во время погони, а начиная с уровня сложности "Нормальный", есть шанс, что они начнут считать до 5, а после считалочки смогут убить вас в течение нескольких секунд

49👍6🥰6

31 May 2026, 23:15 UTC≈3,520 views72 reactions1 Starread 7 August 2026
Video

#разработка С первым днём лета!😎 Прошло столько времени с прошлого патча, что уже наступило лето... Следующий патч выйдет в июне. За продолжительное ожидание держите Йоко. Всем у кого наступили каникулы желаем хорошего отдыха! А у кого начинаются или уже начались экзамены и сессия, желаем только успеха!

52👍13🥰7

25 May 2026, 20:21 UTC≈3,580 views121 reactionsread 7 August 2026
Photo

#разработка 🥰

👍6042🥰18🔥1

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

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

“Yoko no Hanashi” (@yokonohanashi), 2,209 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/yokonohanashi.

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.