Channel
@pufferfish_sekai
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
42subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002121500725 |
|---|---|
| Type | Channel |
| Username | @pufferfish_sekai |
| Description | Буль-буль 🫧🐡 |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/pufferfish_sekai |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 17:31 | 42 | no change |
| 7 Aug 2026, 12:24 | 42 | first reading |
20 posts held, back to 17 July 2025 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 1 September 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
196 reactions across 20 posts, in 15 distinct kinds. The most used accounts for 31.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5348416391663861805 | 62 | 31.6% | |
| 💘 | 36 | 18.4% | |
| ❤ | 35 | 17.9% | |
| 😭 | 25 | 12.8% | |
| 🔥 | 12 | 6.12% | |
| 💔 | 9 | 4.59% | |
| ❤🔥 | 3 | 1.53% | |
| 🕊 | 3 | 1.53% | |
| 😨 | 3 | 1.53% | |
| 😢 | 2 | 1.02% | |
| 🥰 | 2 | 1.02% | |
| ⚡ | 1 | 0.51% | |
| 🍌 | 1 | 0.51% | |
| 🍓 | 1 | 0.51% | |
| 🎉 | 1 | 0.51% |
Custom emoji. One row above is a 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 count beside it isTelegram’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 20 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 196reactions 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 17 July 2025 to 1 September 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
▶️Буль-буль, на связи администрация!! На этот раз мы к вам с немного грустными новостями: 👇👇👇 !!! Сетка pufferfish sekai закрыта !!! 🟡🟡🟡 Это было хорошо обдуманное и необходимое для нас решение. Спасибо вам всем, что были с нами, до новых встреч!! ⏩Любите иглобрюхов 👋🌟
😭14custom 534841639166386180510❤5😨3💘1🔥1🕊1
❌▸ #LEAVE ༊*·˚ Саки Тенма покидает нашу сетку, заявки на этого персонажа снова принимаются ●・○・●・○・●
😭10💔5❤2🕊1custom 53484163916638618051
🌊▸ #РЕСТ ༊*·˚ Канал Vivid Bad Squad Мейко уходит в рест на неделю, просьба отнестись с пониманием и не беспокоить саппорта ▸@Meiko_VBS_pf □•■•□•■•□•■•□•■•□
custom 53484163916638618053❤2💘2
✨▸#СДР ༊*·˚ Сегодня празднует день рождения наш саппорт Саки!! Поздравляем Яххи с праздником и желаем всего самого лучшего!! ✩⋆✩⋆✩⋆✩⋆✩⋆✩⋆✩⋆✩⋆✩
💘3custom 53484163916638618053❤2🔥1
☀️ ▸ #Ивент ༊*·˚ Секай – место созданное вашими чувствами и мечтами!! Уже последний месяц лета. Несмотря на то, что вечная жара уже надоедает, как же хочется иногда простого – беззаботно понежиться на солнышке Как хорошо, что у ребят появилось именно такое место, где они смогут отдохнуть на берегу моря, забыв о всех проблемах!! ◇ • ◇ • ◇ • ◇
custom 53484163916638618055💘3🔥3⚡1❤1🍌1🍓1
✨▸#СДР ༊*·˚ Сегодня празднует день рождения наш саппорт Араты и Акито!! Поздравляем Саню с праздником и желаем всего самого лучшего!! ✩⋆✩⋆✩⋆✩⋆✩⋆✩⋆✩⋆✩⋆✩
custom 53484163916638618056💘5❤4❤🔥1🔥1
🌊▸ #РЕСТ ༊*·˚ Канал Тоно Арата уходит в рест на две недели, просьба отнестись с пониманием и не беспокоить саппорта ▸@TonoArata_pf □•■•□•■•□•■•□•■•□
custom 53484163916638618054❤1💘1🔥1😢1
🌊▸ #РЕСТ ༊*·˚ Канал Акито Шинономе уходит в рест на две недели, просьба отнестись с пониманием и не беспокоить саппорта ▸@akito_pf □•■•□•■•□•■•□•■•□
❤2💘1😢1custom 53484163916638618051
🌊▸ #РЕСТ ༊*·˚ Канал Wonderland × Showtime Кайто уходит в рест на неделю, просьба отнестись с пониманием и не беспокоить саппорта ▸@wxskaito_pf □•■•□•■•□•■•□•■•□
custom 53484163916638618052❤1💘1
❌▸ #LEAVE ༊*·˚ Минори Ханасато покидает нашу сетку, заявки на этого персонажа снова принимаются ●・○・●・○・●
custom 53484163916638618052❤1💘1
🌊▸ #РЕСТ ༊*·˚ Канал Niigo Лен уходит в рест на неопределённый срок, просьба отнестись с пониманием и не беспокоить саппорта ▸@niiLen_pf □•■•□•■•□•■•□•■•□
custom 53484163916638618053❤1💘1
🌊▸ #РЕСТ ༊*·˚ Канал Хиномори Шихо уходит в рест на две недели, просьба отнестись с пониманием и не беспокоить саппорта ▸@ShihoBlog_pf □•■•□•■•□•■•□•■•□
💘3❤2🔥2custom 53484163916638618051
Showing the 12 most recent of 20 posts we hold for @pufferfish_sekai. 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 — 149,680 of 1,478,351entries 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 5 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.
@pufferfish_sekai named 4 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“[ЗАКРЫТО] Pufferfish sekai” (@pufferfish_sekai), 42 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/pufferfish_sekai.
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.