Channel
@hizoki_pub
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
53subscribers
+0 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001822636924 |
|---|---|
| Type | Channel |
| Username | @hizoki_pub |
| Description | Пожалуй, я смогу закончить все за пару дней... При условии, что не буду спать. |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/hizoki_pub |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 09:46 | 53 | no change |
| 10 Aug 2026, 04:31 | 53 | first reading |
20 posts held, back to 1 May 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 July 2026. 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.
Measured directly from 3 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.
76 reactions across 16 posts, in 7 distinct kinds. The most used accounts for 48.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 37 | 48.7% | |
| 🦄 | 20 | 26.3% | |
| ❤🔥 | 10 | 13.2% | |
| 🔥 | 6 | 7.89% | |
| 🎉 | 1 | 1.32% | |
| 👀 | 1 | 1.32% | |
| 👍 | 1 | 1.32% |
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 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 76reactions 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 1 May 2025 to 1 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.
О май гарбл, кажется у этой чудесной женьщины сегодня днюшка! Очень много приятного было сегодня услышанно, аж до слезок TT Я очень постараюсь стать продуктивнее ребятки, обязуюсь - честно))) Любяшки вас всех, я пикми не извиняюсь
❤4❤🔥1🎉1
Моя маленькая сладкая мечта собрать проект по Диско Райвелсу, можем когда нибудь. Когда нибудь...
❤4🦄1
На съёмочной площадке происходит какая-то заруба, так же мы которых пнули и мы отснялись первыми:
❤3🦄3❤🔥2
Channel name was changed to «Пристанище Хизо»
Вообще на лето планируются на выход 2 женщины. Одна сядет на лицо, вторая сломает. Вот такие 2 стороны 1 монеты
Sticker, posted without a caption
Хехехе, ща будет лютая заправочка на ГикКоне. Парк заказан, костюм тоже, а вот кого. Ну персонаж лютый, такая женщина вышла, я в ахуе. С её реализации прошло дня 4, а я со всем готовееьким. К концу мая думаю уже все покажу
❤1
Она такая прелесть, я не могу
❤1🦄1
Video, posted without a caption
❤2🦄1
Это какой-то пранк. Наигрался я уже 50 часов в БГ3 и пошла по пути пубертатных девочек нетакусь, тобишь - романьсить пубертатную язву в виде Астариона... Но последовательница Шар решила по другому и какого-то хуя у меня сней самые лучшие отношения... Шадоухарт такая бусинка❤️
🦄5❤1
Теперь я самый настоящий Килджой мейнер)))
🔥4❤🔥2❤1🦄1
Мне нужна жёстко отъебать платину и апнуться на алмаз, что мой любимый муж вернулся в игру🫤 М-мотивация
❤4🦄1
Showing the 12 most recent of 20 posts we hold for @hizoki_pub. 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 — 1,209,340 of 1,345,403entries 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
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.
“Пристанище Хизо” (@hizoki_pub), 53 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/hizoki_pub.
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.