Telegram RegisterThe public register of Telegram
Telegram profile photo for KazuyooSourcesCh.

Channel

KazuyooSourcesCh.

@KzyoCh

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

7,890subscribers

+385 since we began measuring on 7 August 2026

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

Register entry

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

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 92% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. They sit inside a group of 5 channels that share the same post bodies with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (3 of the pairs behind the counts below)
Posted firstThenOverlapGap
@RiOpSo/623121 Jul 2026, 13:39 UTC@KzyoCh/1971 · this entry21 Jul 2026, 15:33 UTC1.001.9 hours
@RiOpSo/624125 Jul 2026, 12:39 UTC@KzyoCh/1975 · this entry25 Jul 2026, 20:59 UTC1.008.3 hours
@RiOpSo/624528 Jul 2026, 04:22 UTC@KzyoCh/1978 · this entry28 Jul 2026, 05:36 UTC1.0074 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@RiOpSo7 (7/7 hand-verifiable sample passed)1.001.9 hours@RiOpSo (4–3)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 3 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 17 comparable posts for this entry, running 4 July 2026 to 3 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 5, the earliest publisher we hold is @ChermodzsModule. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 8 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 4 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

7,5037,8907,696.57 August 2026 — 7,505 subscribers7 August 2026 — 7,503 subscribers10 August 2026 — 7,535 subscribers14 August 2026 — 7,584 subscribers17 August 2026 — 7,624 subscribers24 August 2026 — 7,650 subscribers27 August 2026 — 7,668 subscribers30 August 2026 — 7,697 subscribers2 September 2026 — 7,722 subscribers6 September 2026 — 7,750 subscribers10 September 2026 — 7,814 subscribers14 September 2026 — 7,868 subscribers18 September 2026 — 7,890 subscribers7 August 202618 September 2026
13 measurements spanning 42 days, net +385. 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 7,445–7,948 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 20:357,890+22
14 Sept 2026, 05:597,868+54
10 Sept 2026, 21:407,814+64
6 Sept 2026, 04:197,750+28
2 Sept 2026, 00:557,722+25
30 Aug 2026, 01:067,697+29
27 Aug 2026, 07:067,668+18
24 Aug 2026, 15:087,650+26
17 Aug 2026, 16:247,624+40
14 Aug 2026, 12:467,584+49
10 Aug 2026, 20:237,535+32
7 Aug 2026, 17:407,503-2
7 Aug 2026, 14:037,505first reading

Engagement

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

Reaction mix

384 reactions across 35 posts, in 7 distinct kinds. The most used accounts for 59.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤡23059.9%
🔥5714.8%
❤‍🔥328.33%
👍318.07%
🗿205.21%
🍾112.86%
🕊30.781%

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

Measured over the 39 most recent posts we hold, published 3 July 2026 to 27 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

27 Aug 2026, 20:03 UTC591 views38 reactionsread 28 August 2026
Photo

gebrakan emote baduf

🤡27👍6🔥3🕊2

Signed Kazuyoo

25 Aug 2026, 08:30 UTC≈4,600 views6 reactionsread 28 August 2026
Photo

𝗚𝗔𝗠𝗘-𝗔𝗦𝗦𝗘𝗧-𝗣𝗥𝗘𝗙𝗘𝗧𝗖𝗛𝗘𝗥 | 𝗨𝗣𝗗𝗔𝗧𝗘 𝟭.𝟲 Game Asset Prefetcher (GAP) is designed to preload and lock critical game assets directly into RAM, reducing load times and storage read overhead during gameplay. 📧 𝗖𝗵𝗮𝗻𝗴𝗲𝗹𝗼𝗴𝘀 : • Detailed release. 📋 𝗡𝗼𝘁𝗲𝘀 : • Downloads | Screenshot • kazuyoo-stuff.github.io • Information & Credits # Thanks For Using, Support My Project.

❤‍🔥3🔥3

Signed Kazuyoo

24 Aug 2026, 02:36 UTC≈1,310 viewsread 28 August 2026
Forwarded from @DemoniicaPhoto

Kang 8.5 is Here お使いのデバイスのパフォーマンスと効率を最適化します。 Changelog: • Read Full Changelog here. 🌐 GitHub Repository 📦 Download Plugin 😋 Grup | Store 😘 Support me ⁉️ Reports

Signed Kazuyoo

23 Aug 2026, 14:02 UTC≈1,350 views9 reactionsread 28 August 2026
Forwarded from @Java_diksPhoto

JavaPro! Release:23/08/26 Version:3.0.5 Support:Root/Non Root Tools:Magisk/KSU/Shizuku/axmanager maybe try it Fix Bug -Bug loop login -Bug FPS -Bug setting not apply -Bug stuck login screen -update scurity patch What's new? -Update Fps for non rooted device Disclaimer:I'm not 100% sure this will work perfectly on some devices but I tested it myself on a device with Helio g95 chipset and it worked ⬇️:Download ⚡️:Chan…

🤡7🔥2

Signed Kazuyoo

22 Aug 2026, 14:27 UTC≈1,630 views4 reactionsread 28 August 2026
Photo

ak pilih archive tune dulu ah

❤‍🔥2👍1🤡1

Signed Kazuyoo

21 Aug 2026, 13:38 UTC≈1,480 views3 reactionsread 28 August 2026
Forwarded from @JaaGabuPhoto

Update Plugin AxVision | v1048-210826-S Build Date: 21-08-2026 Developer: @Reiieja Credit: @reljawa | @dcx400 | @HoyoSlave | @Kzuyoo Installation Support: AxManager Download Change Log: - Indonesia - English Note: Jika anda menemukan sebuah bug segera hubungi @Reiieja

🔥3

Signed Kazuyoo

20 Aug 2026, 09:50 UTC≈2,040 views42 reactionsread 28 August 2026

lama lama kuhapus y emote badut

🤡40👍2

Signed Kazuyoo

18 Aug 2026, 10:28 UTC≈2,720 views57 reactionsread 28 August 2026
File

test fix crash facebook & other

🤡38🗿13❤‍🔥3👍3

Signed Kazuyoo

17 Aug 2026, 04:11 UTC≈2,580 views2 reactionsread 28 August 2026
Forwarded from @RiOpSoPhoto

🇮🇩 Dirgahayu Republik Indonesia ke-81 Mari terus menjaga semangat kemerdekaan untuk Indonesia yang berdaulat, adil, dan makmur. Merdeka! Merdeka! Merdeka!

🗿2

Signed Kazuyoo

16 Aug 2026, 13:50 UTC≈2,760 views2 reactionsread 28 August 2026
Photo

Advanced Hosts Manager 3.5 is Here Advanced system-level hosts management with real-time ad blocking, privacy protection, and automatic updates from trusted sources. Changelog: • Full info Changelog. Note: • Screenshot. 🌐 GitHub Repository 📦 Download Module 😋 Channel | Store 😘 Support me ⁉️ Reports

🤡2

Signed Kazuyoo

15 Aug 2026, 08:29 UTC≈2,700 views5 reactionsread 28 August 2026

emote badutnya mohon di kondikiskan

🗿3🤡2

Signed Kazuyoo

15 Aug 2026, 05:34 UTC≈11,100 views101 reactionsread 28 August 2026
Photo

𝗖𝗘𝗟𝗘𝗦𝗧𝗜𝗔𝗟-𝗚𝗔𝗠𝗘-𝗢𝗣𝗧 | 𝗨𝗣𝗗𝗔𝗧𝗘 𝟯.𝟯 Celestial Game Opt for designed to enhance Android game performance while preserving system stability and responsiveness. 📧 𝗖𝗵𝗮𝗻𝗴𝗲𝗹𝗼𝗴𝘀 : • Detailed release. 📋 𝗡𝗼𝘁𝗲𝘀 : • Downloads | Screenshot • kazuyoo-stuff.github.io • Credits & Information. • Wait a few minutes after uninstall then reboot. # Thanks For Using, Support My Project.

🤡93👍3🔥2🍾1🕊1🗿1

Signed Kazuyoo

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

Mentions

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.

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.

“KazuyooSourcesCh.” (@KzyoCh), 7,890 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/KzyoCh.

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.