Telegram RegisterThe public register of Telegram

Channel

YAMAZAKI🎐

@sb_yamazaki

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

429subscribers

+3 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001762998271
TypeChannel
Username@sb_yamazaki
Created4 August 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live15 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/sb_yamazaki

Growth

4254294276 August 2026 — 426 subscribers6 August 2026 — 426 subscribers7 August 2026 — 425 subscribers15 August 2026 — 429 subscribers6 August 202615 August 2026
4 measurements spanning 9 days, net +3. 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 424–430 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 02:45429+4
7 Aug 2026, 09:03425-1
6 Aug 2026, 19:30426no change
6 Aug 2026, 10:48426first reading

Engagement

20 posts held, back to 25 July 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
47.2%
avg views ÷ 429 subscribers
Avg views / post
203
20 posts measured
Reaction rate
8.10%
reactions ÷ views · ER floor
Posts in window
20
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 19 of 20 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 5 August 2026
Posts held20 (25 July 20265 August 2026)
Views total4,053
Reactions total306
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 19:30 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

306 reactions across 19 posts, in 11 distinct kinds. The most used accounts for 20.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🍓6220.3%
custom 52224507475384329315919.3%
💋3912.7%
custom 52426499143070225203411.1%
🙏268.50%
custom 5242431339126362759247.84%
💘227.19%
custom 5239940107770824450216.86%
custom 527609293056039470082.61%
custom 524033010798117202272.29%
😈41.31%

Custom emoji. 6 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 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 19 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 306reactions 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 25 July 2026 to 5 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.

Recent posts

5 Aug 2026, 17:30 UTC127 views7 reactionsread 6 August 2026

Буду судьей на батлах в пятницу, приходите танцевать 🙂‍↕️

custom 52224507475384329317

5 Aug 2026, 17:29 UTC119 views5 reactionsread 6 August 2026
Forwarded from @realdanceproject_nnPhoto

Напомним, что продолжается регистрация на бесплатные баттлы! 🔥 БАТТЛЫ ВОЗВРАЩАЮТСЯ! И на этот раз - участие абсолютно бесплатное! 7 августа команда ШКОЛЫ ТАНЦЕВ Real Dance Project вновь организует открытые городские танцевальные баттлы в рамках празднования Дня физкультурника в Советском районе Нижнего Новгорода. Для нас это не просто соревнования. Это возможность показать, что современная танцевальная культура -

custom 52426499143070225205

5 Aug 2026, 17:09 UTC134 views5 reactionsread 6 August 2026

Ещё ищем в проект двух участниц 🫰🏻🕺 или участников 🙂‍↕️✌🏻

🍓4💘1

5 Aug 2026, 17:09 UTC129 views6 reactionsread 6 August 2026
Forwarded from @realdanceproject_nnVideo

НАЧАЛИ ПРОЕКТ 🔥🔥🔥🔥 K-POP IDOL PROJECT BABYMONTER ЗАПИСАТЬСЯ В @realdanceproject И ВЫСТУПИМ НА АЗИЯ ЗОН 5 СЕНТЯБРЯ ПРОВЕДИ АВГУСТ С НАМИ 👏

custom 52399401077708244506

5 Aug 2026, 12:15 UTC144 views8 reactionsread 6 August 2026

Начинаем сегодня BABYMONSTER 🧎🏼‍♀️👼🏻 Для записи: @realdanceproject По всем вопросам: @sbyamazaki

🍓4🙏4

4 Aug 2026, 08:18 UTC165 views3 reactionsread 6 August 2026

Уже завтра в среду проект стартует!!! Кто ещё не успел присоединиться, пишите @realdanceproject По всем вопросам можете написать мне @sbyamazaki

custom 52224507475384329313

1 Aug 2026, 18:30 UTC215 views11 reactionsread 6 August 2026
Forwarded from @realdanceproject_nnVideo

НАБОР В K-POP IDOL PROJECT набираем желающих в проект , с которым 5.09.2026 выступим на АЗИЯ ЗОН ПОДРОБНОСТИ ТУТ НАСТАВНИК: YAMAZAKI РАСПИСАНИЕ: ПН/СР 18:00, ВС 13:00 (выходной день и время будут обсуждаться отдельно с набранным составом) запись в @realdanceproject ПРОЕКТ ВЫБРАН ⬇️ Проект: BABYMONSTER - Sugar honey ice tea https://youtu.be/SsuCimm5BIU?si=7TYYeO3iXR7BwHPv присоединяйся, пиши @realdanceproject

custom 52426499143070225209custom 52424313391263627592

1 Aug 2026, 08:32 UTC228 views11 reactionsread 6 August 2026

Холодный сладкий медовый чай 🧋🤫 по секрету Для записи - @realdanceproject

custom 52426499143070225207custom 52424313391263627594

30 Jul 2026, 16:10 UTC236 views11 reactionsread 6 August 2026
Forwarded from @realdanceproject_nnVideo

Мы запускаем K-POP IDOL PROJECT вместе с Дашей Кузнецовой - любимым педагогом Real Dance Project СТАРТ: 3 АВГУСТА донабор до 10 АВГУСТА, пока не закончились места в команде. Итак, внимание ‼️ Это не просто тренировки. Это мини-проект, где за месяц мы: ✨ выучим полноценную хореографию; ✨ прокачаем технику и синхрон; ✨ соберём настоящую команду; ✨ и уже 5 сентября выступим на фестивале «Азиа зон». 📅 В проект входит

custom 52224507475384329317🍓2custom 52399401077708244502

26 Jul 2026, 12:53 UTC242 views18 reactionsread 6 August 2026
Forwarded from @asiazonennPhoto

Photo, posted without a caption

🍓10custom 52224507475384329315💋3

26 Jul 2026, 11:29 UTC229 views18 reactionsread 6 August 2026
Forwarded from @asiazonennVideo message

Video message, posted without a caption

custom 52224507475384329319💋4🍓3💘2

26 Jul 2026, 08:44 UTC273 viewsread 6 August 2026

Сегодня в чико вечеринка 🥺 мои девочки выступают 🏋️

Showing the 12 most recent of 20 posts we hold for @sb_yamazaki. 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 — 955,610 of 1,350,102entries 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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

“YAMAZAKI🎐” (@sb_yamazaki), 429 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/sb_yamazaki.

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.