Telegram RegisterThe public register of Telegram
Telegram profile photo for KazusaLeaks

Channel

KazusaLeaks

@KazusaLeaks

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

17,281subscribers

-90 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002449112972
TypeChannel
Username@KazusaLeaks
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/KazusaLeaks

Topic

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.

Growth

17,28117,48117,3817 August 2026 — 17,371 subscribers7 August 2026 — 17,371 subscribers8 August 2026 — 17,364 subscribers9 August 2026 — 17,357 subscribers10 August 2026 — 17,350 subscribers11 August 2026 — 17,340 subscribers13 August 2026 — 17,334 subscribers14 August 2026 — 17,336 subscribers15 August 2026 — 17,399 subscribers17 August 2026 — 17,415 subscribers18 August 2026 — 17,449 subscribers19 August 2026 — 17,458 subscribers20 August 2026 — 17,471 subscribers21 August 2026 — 17,473 subscribers23 August 2026 — 17,472 subscribers24 August 2026 — 17,481 subscribers25 August 2026 — 17,478 subscribers26 August 2026 — 17,470 subscribers27 August 2026 — 17,473 subscribers28 August 2026 — 17,469 subscribers29 August 2026 — 17,466 subscribers30 August 2026 — 17,460 subscribers31 August 2026 — 17,454 subscribers1 September 2026 — 17,446 subscribers2 September 2026 — 17,439 subscribers3 September 2026 — 17,423 subscribers5 September 2026 — 17,405 subscribers8 September 2026 — 17,381 subscribers11 September 2026 — 17,361 subscribers13 September 2026 — 17,335 subscribers14 September 2026 — 17,322 subscribers16 September 2026 — 17,301 subscribers18 September 2026 — 17,281 subscribers7 August 202618 September 2026
33 measurements spanning 42 days, net -90. 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 17,251–17,511 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
18 Sept 2026, 22:5717,281-20
16 Sept 2026, 15:0117,301-21
14 Sept 2026, 16:2117,322-13
13 Sept 2026, 06:1717,335-26
11 Sept 2026, 09:3717,361-20
8 Sept 2026, 14:3817,381-24
5 Sept 2026, 11:2017,405-18
3 Sept 2026, 16:0017,423-16
2 Sept 2026, 11:4217,439-7
1 Sept 2026, 10:1417,446-8
31 Aug 2026, 09:5717,454-6
30 Aug 2026, 10:5617,460-6
29 Aug 2026, 11:2617,466-3
28 Aug 2026, 13:0617,469-4
27 Aug 2026, 14:2517,473+3
26 Aug 2026, 14:0617,470-8
25 Aug 2026, 17:2317,478-3
24 Aug 2026, 20:3217,481+9
23 Aug 2026, 03:1817,472-1
21 Aug 2026, 12:5917,473first reading

Engagement

21 posts held, back to 1 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 52 pages 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 21 posts for this entry, the most recent from 17 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
23m 42s
Average length
2m 38s

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

Reaction mix

1,500 reactions across 21 posts, in 28 distinct kinds. The most used accounts for 63.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
95763.8%
🤔1087.20%
🤬1016.73%
🔥644.27%
😐432.87%
🫡372.47%
😁322.13%
😭322.13%
🥰181.20%
👏151.00%
❤‍🔥130.867%
👀110.733%
🤨110.733%
🤯110.733%
💘60.4%
🗿60.4%
👻50.333%
😍50.333%
😢50.333%
👍40.267%
8 further kinds161.07%

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 21 of the 21 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 1,500 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 21 most recent posts we hold, published 1 July 2026 to 17 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

17 Aug 2026, 17:53 UTC≈17,900 views52 reactionsread 3 September 2026

7.6 测试 【分解重构】 触发关闭按钮 7.6 测试 【分解重构】 触发T键交互开始QTE 7.6 测试 【分解重构】 触发T键交互开始QTE 判过 hoyo what are you doing...

🤔484

17 Aug 2026, 17:41 UTC≈18,600 views51 reactionsread 3 September 2026

Hoyo made a mistake and left in v1 a data entry hinting about a world quest in an upcoming area for 7.2. This entry was now removed in v2. 让树灵能够用冲锋冲进窗子 7.2 木屋守卫战 树灵入窗逻辑 In English: Allowing the tree spirit to charge through the window 7.2 Wooden House Defense Battle: Tree Spirit Enters Through the Window - Logic

🤔46🔥32

14 Aug 2026, 09:30 UTC≈18,600 views133 reactionsread 3 September 2026
Photo

Additionally, there will be an anniversary event tied to UGC. Later we will send a more finished version of it.

🤬9024🤔9🥰4🤪2😭2🔥1🤨1

14 Aug 2026, 09:29 UTC≈17,800 views38 reactionsread 3 September 2026
Photo

GI 7.1 - New events overview The first event is VERY unfinished and theres one more that is missing its entire UI. Obviously, the name Weapon: Sword is also a placeholder

32🔥5🍓1

14 Aug 2026, 08:24 UTC≈15,300 views73 reactionsread 3 September 2026
Photo

GI 7.1 - New beta poses

64🤔5🔥3😍1

14 Aug 2026, 07:59 UTC≈14,300 views77 reactionsread 3 September 2026
Photo

GI 7.1 - New quest-related scenes

53👀11❤‍🔥6🔥3👍2💋2

12 Aug 2026, 19:25 UTC≈7,750 views62 reactionsread 3 September 2026
Video

GI 7.1 - Vodyanitsa and Vesna Gacha Animations

46😐14❤‍🔥1🍓1

12 Jul 2026, 21:12 UTC≈32,100 views87 reactionsread 3 September 2026
Video

GI 7.0 - Train mechanic demonstration

79😍4❤‍🔥2🔥2

9 Jul 2026, 17:24 UTC≈14,400 views49 reactionsread 17 August 2026

. (Sorry for the notification btw) The channel is not hacked, and its not a simple ad Kuroo is in trouble. Kazusa help. If you arent interested in helping Kuroo, please ignore

46😁3

9 Jul 2026, 17:23 UTC≈12,000 views129 reactionsread 17 August 2026
Forwarded from @kurooleaksPhoto

Hello guys!! My friend Alicezation is making emergency commissions so that she can pay her rent since she got kicked out of her house by her bipolar mom... https://vgen.co/Alicezation https://x.com/Alicezationn All prices are 20-30% off the original values, just dm her on vgen or on Twitter, please help her she's a cool person that does'nt deserve anything of what she's going through right now :c

62🫡24😐13🤬11😭7🗿4🔥3😢3

9 Jul 2026, 17:23 UTC≈8,600 views39 reactionsread 13 August 2026

[NOT A LEAK] Kazusa's dear friend (Kuroo) is in trouble and needs help We usually don't post such things on the channel, but this is an emergency, so if you can help, please do

29🤨10

5 Jul 2026, 02:00 UTC≈53,200 views95 reactionsread 13 August 2026
Video

GI 7.0 - Snezhnaya map exploration Please note: most of the stuff on the map are very unfinished and may not represent the final product. Some props are a bit broken. Additionally we could not record 100% of the map due to it's ridiculous size. The video is HEAVILY compressed and split to 4 parts for the ease of streaming.

76👏10😭7❤‍🔥1🥰1

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

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.

Mentions

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.

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

“KazusaLeaks” (@KazusaLeaks), 17,281 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/KazusaLeaks.

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.