[Хамурибэ] Риндо Хайтани доступен! До 14 августа! #Япония 🇯🇵
custom 535290598110791188044custom 53530370935745560327🔥5

Channel
@TRPazuribe
On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
2,163subscribers
+41 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002043375599 |
|---|---|
| Type | Channel |
| Username | @TRPazuribe |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 2 times, most recently 16 September 2026 |
| On Telegram | t.me/TRPazuribe |
Gaming — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 12 Sept 2026, 08:58 | 2,163 | +8 |
| 7 Sept 2026, 20:58 | 2,155 | +3 |
| 2 Sept 2026, 17:53 | 2,152 | +6 |
| 30 Aug 2026, 10:16 | 2,146 | -1 |
| 27 Aug 2026, 18:15 | 2,147 | -3 |
| 24 Aug 2026, 18:55 | 2,150 | +7 |
| 21 Aug 2026, 06:15 | 2,143 | +6 |
| 18 Aug 2026, 05:12 | 2,137 | +16 |
| 14 Aug 2026, 19:47 | 2,121 | -1 |
| 14 Aug 2026, 03:02 | 2,122 | first reading |
19 posts held, back to 31 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 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 19 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.
906 reactions across 19 posts, in 5 distinct kinds. The most used accounts for 26.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5352566455353227930 | 239 | 26.4% | |
| 😍 | 200 | 22.1% | |
| custom 5352905981107911880 | 172 | 19.0% | |
| 🔥 | 172 | 19.0% | |
| custom 5353037093574556032 | 123 | 13.6% |
Custom emoji. 3 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 19 of the 19 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 906 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 31 July 2026 to 12 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @TRPazuribe. 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 19 most recent posts we hold for this entry, published 31 July 2026 to 12 August 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.
[Хамурибэ] Риндо Хайтани доступен! До 14 августа! #Япония 🇯🇵
custom 535290598110791188044custom 53530370935745560327🔥5
Стал доступен хомячок Какучё! Успей выбить его до 10.08.26 #япония
custom 535256645535322793044custom 535303709357455603211custom 53529059811079118806😍2🔥1
Сначала вторая стадия ивента, а вместе с ней и баннер Майки. Ивент продлится до 14.08.2026 #Япония
custom 535256645535322793033custom 53530370935745560328custom 53529059811079118806
🐹 Новый хомячок уже стал доступен! Успейте выбить этого милашку до 8.08.26 #япония
custom 535256645535322793041😍10🔥8custom 53529059811079118801custom 53530370935745560321
Новые лимитированные миссии уже доступны! Выполните их что б получить Такемичи хомячка! #Япония 🇯🇵
😍27🔥4custom 53530370935745560324custom 53529059811079118803custom 53525664553532279302
Пошаговая реран гача с Ханрибэ доступна! До 15 августа! #Япония 🇯🇵
😍29🔥3custom 53530370935745560323custom 53525664553532279302custom 53529059811079118802
Новые версии в Хамрибэ! #Япония 🇯🇵
😍36custom 53525664553532279309custom 53530370935745560329🔥3custom 53529059811079118802
Уже завтра! #Япония 🇯🇵
🔥33custom 535256645535322793019custom 53530370935745560323
✨🐹🐾6 августа анонс в линейке Хомяков🐾🌻✨ #Япония 🇯🇵
custom 535290598110791188030custom 53530370935745560329custom 53525664553532279307
[Декора] Хаккай Шиба! 💎 Первые 10 круток можно сделать бесплатно 💎 Следующие крутки можно делать только платными алмазами До 10 августа! #Япония 🇯🇵
custom 535290598110791188038custom 53530370935745560325😍3custom 53525664553532279301
👹Стал доступен новый ивент, а с ним и баннер Ханмы! Ивент продлится до 14.08.26 #Япония
😍49🔥10custom 53525664553532279309custom 53530370935745560323custom 53529059811079118801
1 августа — день рождение Шиничиро! Гача [День рождение III] Шиничиро Сано уже доступна ✨ Специальные этапы, где вы можете заработать билеты для гачи, предметы мебели, и карты поддержки также доступны! #Глобал 🌍
custom 535256645535322793028🔥5😍4custom 53529059811079118801custom 53530370935745560321
Showing the 12 most recent of 19 posts we hold for @TRPazuribe. 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.
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 1 registered channel — 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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“Tokyo Revengers Pazuribe” (@TRPazuribe), 2,163 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/TRPazuribe.
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.