🌟 Медиа-менеджеры «Васаби» и болельщик команды угадывают наших игроков!
⚡8🔥5❤4custom 52246927419417896264

Channel
@heywasabimedia
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
334subscribers
+1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001981395341 |
|---|---|
| Type | Channel |
| Username | @heywasabimedia |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 30 August 2026 |
| On Telegram | t.me/heywasabimedia |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 16:56 | 334 | +2 |
| 15 Aug 2026, 18:28 | 332 | -1 |
| 6 Aug 2026, 21:46 | 333 | no change |
| 6 Aug 2026, 11:17 | 333 | first reading |
12 posts held, back to 15 July 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 4 August 2026 |
|---|---|
| Posts held | 12 (15 July 2026 – 4 August 2026) |
| Views total | 483 |
| Reactions total | 92 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 21:46 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.
328 reactions across 12 posts, in 16 distinct kinds. The most used accounts for 32.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 107 | 32.6% | |
| 🔥 | 50 | 15.2% | |
| ❤🔥 | 40 | 12.2% | |
| custom 5224692741941789626 | 24 | 7.32% | |
| ⚡ | 15 | 4.57% | |
| custom 5222027074784496089 | 14 | 4.27% | |
| 😍 | 14 | 4.27% | |
| custom 5224458953986966418 | 13 | 3.96% | |
| custom 5224289075145509338 | 12 | 3.66% | |
| custom 5224301723824195959 | 11 | 3.35% | |
| custom 5222063173984619695 | 8 | 2.44% | |
| 😢 | 8 | 2.44% | |
| 💔 | 5 | 1.52% | |
| custom 5215331027496500584 | 3 | 0.915% | |
| custom 5224545527642753541 | 3 | 0.915% | |
| custom 5224710574646002573 | 1 | 0.305% |
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 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 12 of the 12 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 328reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 15 July 2026 to 4 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.
🌟 Медиа-менеджеры «Васаби» и болельщик команды угадывают наших игроков!
⚡8🔥5❤4custom 52246927419417896264
🌟 ВАСАБИ 🌟🌟🌟 ГРОЙТЕР 🌟 Непростой матч для нашей команды, в котором было все. Забили первыми, пропустили три, отыгрались, итог - боевая ничья. Важный эмоциональный подъем после поражения в кубке. Готовимся к следующему туру! 🌟 🌟🌟🌟 от команды Васаби - Константин Тимиров
🔥9❤🔥2😍2custom 52242890751455093382⚡1❤1custom 52153310274965005841custom 52243017238241959591
🌟 ВАСАБИ х ГРОЙТЕР 🌟 Возвращаемся на поле на второй круг чемпионата! Мы готовимся к новой игре и хотим показать, на что мы способны. Поддержим в комментариях наших игроков и пожелаем им удачи на завтрашней игре! 🌟 02.08.2026 🌟 18:00 🌟 Стадион MFL 🌟 +30° С 🌟 Трансляция матча
🔥7❤🔥5❤4custom 52153310274965005842custom 52243017238241959592custom 52244589539869664182
🌟 Ваня, с днём рождения! Сегодня мы хотим поздравить человека, без кого мы уже не видим нашу команду. Друг, болельщик и просто самая главная поддержка для нас. Ваня приезжает на все игры, реагирует на все посты. 🌟 Поздравляем и благодарим тебя за все, что ты для нас делаешь! С твоим днём!
❤13🔥8😍4custom 52220270747844960892custom 52220631739846196951custom 52247105746460025731
Яркие моменты с прошедшего матча 🌟
custom 52242890751455093389custom 52243017238241959598custom 52244589539869664185🔥3❤2❤🔥2custom 52245455276427535411custom 52246927419417896261
Первый матч в составе команды и уже 🌟🌟🌟! Поздравляем нового игрока! Добро пожаловать, Андрей! 🌟
❤🔥13❤10custom 52220270747844960898⚡1
🌟 С днём рождения, Ярик! Поздравляем сегодня с днём рождения одного из наших лучших игроков! За то время, что Ярик играет в составе нашей команды, он успел стать MVP «Лиги М» от Васаби, лучшим по ассистам за игру в 2026* году, а также принести команде множество побед. 🌟 Желаем тебе оставаться таким же позитивным и уверенным игроком, который дает мотивацию для всех остальных участников. 🌟 С твоим днём!
❤15custom 52246927419417896268custom 52244589539869664186🔥3
🌟 ВАСАБИ 🌟🌟🌟 КРАНКЕ БАСТАРД 🌟 🌟 Неприятное поражение потерпела наша команда на стадии 1/8, на этом наше выступление в «Кубке АФЛ»закончено. Не унываем, а готовимся и настраиваемся на второй круг чемпионата. 🌟🌟🌟 от команды Васаби — Андрей Косарев
❤10😢8❤🔥7💔3🔥2
🌟 ВАСАБИ х КРАНКЕ БАСТАРД 🌟 Уже завтра возвращаемся после летнего перерыва игрой с командой «Кранке Бастард», чтобы начать путь в «Кубке АФЛ». Поддержим наших игроков и пожелаем им успехов в предстоящей игре! 🌟 26.06.2026 🌟 18:00 🌟 Стадион «MFL», Солнцево 🌟 +20 С°
❤13🔥6⚡5💔2
🌟 Финишная прямая! Наши прогнозы в этот раз таковы… А все видео выходят раньше в нашем Тиктоке!
❤10😍6❤🔥5custom 52246927419417896262custom 52220631739846196951custom 52242890751455093381
🌟 С днём рождения, Егор! Сегодня поздравляем с праздником одного из наших игроков! Хотим пожелать счастья, здоровья и успехов в новых начинаниях! Спасибо тебе за твою игру, силу и умения на поле! Поздравим в комментариях!
❤15custom 52220631739846196956custom 52246927419417896266❤🔥2custom 52220270747844960892
🌟 Эксперты ошиблись… На кого ставим сегодня? Больше в нашем ТикТоке 🌟
❤10🔥7❤🔥4custom 52246927419417896263😍2custom 52220270747844960892custom 52245455276427535411
Showing the 12 most recent of 12 posts we hold for @heywasabimedia. 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 — 385,306 of 1,627,445entries 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.
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.
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.
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.
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.
“Васаби” (@heywasabimedia), 334 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/heywasabimedia.
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.