Telegram RegisterThe public register of Telegram
Telegram profile photo for 🔒0908.Kazu하 ♡₊˚

Channel

🔒0908.Kazu하 ♡₊˚

@forkazu

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

40subscribers

-6 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1003928615757
TypeChannel
Username@forkazu
CreatedBetween 1 April 2026 and 17 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live12 September 2026
Measurements held4
Confirmed unchanged2 times, most recently 12 September 2026
On Telegramt.me/forkazu

Growth

40464310 August 2026 — 46 subscribers11 August 2026 — 46 subscribers18 August 2026 — 42 subscribers2 September 2026 — 40 subscribers10 August 20262 September 2026
4 measurements spanning 23 days, net -6. 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 39–47 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 21:5840-2
18 Aug 2026, 23:1642-4
11 Aug 2026, 03:4646no change
10 Aug 2026, 16:3146first reading

Engagement

12 posts held, back to 17 June 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 12 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
19s
Average length
19s

Measured directly from 1 video 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.

Reaction mix

202 reactions across 8 posts, in 4 distinct kinds. The most used accounts for 28.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53056674482954300945828.7%
custom 54541434369260032075326.2%
custom 54677637789489940845024.8%
custom 54678553605366512864120.3%

Custom emoji. Every 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 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 8 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 202 reactions 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 17 June 2026 to 8 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

30 Jul 2026, 14:04 UTC34 viewsread 10 August 2026

мой полу - информ по карине из эспа

20 Jun 2026, 15:25 UTC171 views23 reactionsread 10 August 2026

всё-таки информ км не мое 🥹 очень благодарна вам за то, что были подписаны и следили! возможно вернусь позже. любите фиммис и казуху

custom 545414343692600320713custom 53056674482954300946custom 54677637789489940844

19 Jun 2026, 15:27 UTC196 views26 reactionsread 10 August 2026
Photo

🤩 ‧₊ 𑁍ࠬ 로맨틱 데이트 ZUHAZANA UPDATE 𓍢 ݁˖ _ 260619

custom 53056674482954300948custom 54541434369260032076custom 54677637789489940846custom 54678553605366512866

19 Jun 2026, 15:27 UTC168 views16 reactionsread 10 August 2026
File

. ꕤ 。˚⋆ Kazu하 `s #노래선택

custom 53056674482954300945custom 54677637789489940845custom 54678553605366512864custom 54541434369260032072

18 Jun 2026, 10:32 UTC139 views27 reactionsread 10 August 2026
Photo

🤩 𓂃𑁍˖ Казу하 посетила шоу рэй – чан из айв « following rei »

custom 530566744829543009410custom 54677637789489940847custom 54678553605366512867custom 54541434369260032073

18 Jun 2026, 10:27 UTC128 views24 reactionsread 10 August 2026

чэчэ вернется на следующей неделе!

custom 53056674482954300947custom 54541434369260032077custom 54677637789489940846custom 54678553605366512864

17 Jun 2026, 13:48 UTC142 views29 reactionsread 10 August 2026
Video

YJ IS ICONIC BY MISTAKE 🙂

custom 54677637789489940848custom 53056674482954300947custom 54541434369260032077custom 54678553605366512867

17 Jun 2026, 12:23 UTC110 views32 reactionsread 10 August 2026
Photo

🤩 𓇢 𓆸 백조 KAZU하 `s messages in weversé #葉DM ,17날 06월 * 𝗞. « доброе утро » 𝗞. « файтин и сегодня тоже »

custom 53056674482954300949custom 54541434369260032078custom 54677637789489940848custom 54678553605366512867

17 Jun 2026, 12:20 UTC87 views25 reactionsread 10 August 2026
Photo

« you're beautiful, you're wonderful incredible, I love you so you're beautiful, each moment spent with you is simple wonderful this love I have for you, girl, it's incredible » _ or whatever michael jackson said 🤩

custom 54541434369260032077custom 53056674482954300946custom 54677637789489940846custom 54678553605366512866

Showing the 12 most recent of 12 posts we hold for @forkazu. 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.

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.

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

“🔒0908.Kazu하 ♡₊˚” (@forkazu), 40 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/forkazu.

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.