Telegram RegisterThe public register of Telegram
Telegram profile photo for K总日本同步代钓

Channel

K总日本同步代钓

@kzongtongbuyu

On this record: Topic · Growth · Engagement · Posts · Cite this entry

169subscribers

-4 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002905958511
TypeChannel
Username@kzongtongbuyu
CreatedBetween 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live12 October 2026
Measurements held4
Confirmed unchanged2 times, most recently 12 October 2026
On Telegramt.me/kzongtongbuyu

Topic

Hacking & security — 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 25 September 2026 and assigned it the closest of 31 fixed categories, at 63% 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

1691731717 August 2026 — 173 subscribers8 August 2026 — 173 subscribers9 September 2026 — 172 subscribers1 October 2026 — 169 subscribers7 August 20261 October 2026
4 measurements spanning 55 days, net -4. 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 168–174 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Oct 2026, 20:00169-3
9 Sept 2026, 01:00172-1
8 Aug 2026, 14:30173no change
7 Aug 2026, 19:08173first reading

Engagement

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

Recent posts

14 Jul 2026, 20:13 UTC153 viewsread 8 August 2026

混合 可指定钓任何源码 合作搞钱的来 钓鱼的话每天都能破百

27 May 2026, 17:53 UTC522 viewsread 8 August 2026

混合 100 visa 100 乐天 100 三井 100 jcb 130 运通 180 另外接亚马逊账户 一个码字70 寻求实力老板 来长期稳定的最好 只对接两个人 目前缺一个长期位置

25 May 2026, 11:25 UTC488 viewsread 8 August 2026

开工 还能对接一个人 来个长期稳定的老板 价格 不高 早上5点 晚上22点 要几天的别来

2 Mar 2026, 21:54 UTC753 viewsread 8 August 2026

amex接单。 来老板。随时钓 每天百+ 老老板

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

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

“K总日本同步代钓” (@kzongtongbuyu), 169 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/kzongtongbuyu.

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.