Telegram RegisterThe public register of Telegram
Telegram profile photo for KK集团-(高频电棍⚡️打新版)

Channel

KK集团-(高频电棍⚡️打新版)

@Kclub737226

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

11,356subscribers

+414 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-1002003227078
TypeChannel
Username@Kclub737226
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 live19 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/Kclub737226

Topic

Crypto & trading — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 82% 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

10,88711,41611,151.57 August 2026 — 10,942 subscribers7 August 2026 — 10,942 subscribers8 August 2026 — 10,941 subscribers9 August 2026 — 10,936 subscribers10 August 2026 — 10,931 subscribers11 August 2026 — 10,958 subscribers12 August 2026 — 10,955 subscribers13 August 2026 — 10,944 subscribers14 August 2026 — 10,934 subscribers16 August 2026 — 10,938 subscribers17 August 2026 — 10,925 subscribers18 August 2026 — 10,913 subscribers19 August 2026 — 11,008 subscribers20 August 2026 — 11,004 subscribers21 August 2026 — 10,982 subscribers22 August 2026 — 10,966 subscribers24 August 2026 — 10,957 subscribers25 August 2026 — 10,955 subscribers26 August 2026 — 10,963 subscribers27 August 2026 — 10,966 subscribers28 August 2026 — 10,957 subscribers29 August 2026 — 10,955 subscribers30 August 2026 — 10,950 subscribers31 August 2026 — 10,934 subscribers1 September 2026 — 10,914 subscribers2 September 2026 — 10,905 subscribers3 September 2026 — 10,887 subscribers5 September 2026 — 10,906 subscribers9 September 2026 — 11,416 subscribers11 September 2026 — 11,404 subscribers13 September 2026 — 11,376 subscribers15 September 2026 — 11,374 subscribers16 September 2026 — 11,366 subscribers19 September 2026 — 11,356 subscribers11,3567 August 202619 September 2026
34 measurements spanning 43 days, net +414. 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 10,808–11,495 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
19 Sept 2026, 08:5911,356-10
16 Sept 2026, 21:3611,366-8
15 Sept 2026, 00:5811,374-2
13 Sept 2026, 10:4111,376-28
11 Sept 2026, 15:1911,404-12
9 Sept 2026, 02:2211,416+510
5 Sept 2026, 17:1710,906+19
3 Sept 2026, 13:5410,887-18
2 Sept 2026, 05:3510,905-9
1 Sept 2026, 04:4910,914-20
31 Aug 2026, 03:1210,934-16
30 Aug 2026, 05:5410,950-5
29 Aug 2026, 05:2410,955-2
28 Aug 2026, 08:5310,957-9
27 Aug 2026, 09:2310,966+3
26 Aug 2026, 10:1810,963+8
25 Aug 2026, 11:1510,955-2
24 Aug 2026, 13:1210,957-9
22 Aug 2026, 22:2410,966-16
21 Aug 2026, 10:0510,982first reading

Engagement

534 posts held, back to 6 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 41 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.70%
avg views ÷ 11,356 subscribers
Avg views / post
647
202 posts measured
Reaction rate
0.387%
reactions ÷ views · ER floor
Posts in window
202
of 534 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 63 of 202 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 1 September 2026
Posts held534 (6 August 20261 September 2026)
Views total130,689
Reactions total147
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken1 Sept 2026, 19:52 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

469 reactions across 177 posts, in 8 distinct kinds. The most used accounts for 45.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
21445.6%
👍8417.9%
🤩439.17%
408.53%
👏388.10%
🔥337.04%
❤‍🔥112.35%
🎉61.28%

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

Measured over the 534 most recent posts we hold, published 6 August 2026 to 1 September 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

1 Sept 2026, 18:07 UTC180 views1 reactionsread 1 September 2026
Photo

GN 能感觉到BSC的狂牛即将袭来 明天继续带园区游龙BSC 暴击牛逼叙事 下机了

1

1 Sept 2026, 14:52 UTC529 views2 reactionsread 1 September 2026

了解背后的故事你会fomo并买入的

🤩2

1 Sept 2026, 14:50 UTC541 views1 reactionsread 1 September 2026

这个叙事我觉得和Cashcat 底层逻辑有点像 一样是一词双关概念 Cashcat 与 Robinhood 产生 Sirius 与 Elon与Vlad 互动产生

1

1 Sept 2026, 14:48 UTC545 views3 reactionsread 1 September 2026
Photo

这个Sirius 看起来洗的差不多了,490K买入了 Pons 缺个狗类大金Meme叙事 Elon 发文关于 Sirius的话题 Vlad 回复 Sirius为The Doge star Sirius CTO 团队还已经注册了一颗星星,并按 Vlad 的要求将其命名为 The Doge Star 0x3b4a0048a00787a644932cd648faa043410c163e

3

1 Sept 2026, 12:54 UTC626 views1 reactionsread 1 September 2026

买了点 TIM 很多AI大户都在车上,先看5M吧 应该是苹果底池龙头了 主要是以调侃库克CEO的梗 有什么比Ceo亲自背书的Meme更好上涨📈

1

1 Sept 2026, 11:32 UTC697 viewsread 1 September 2026
Photo

一个德国德累斯顿的独立开发者用vibe coding 做了一个“宝可梦GO”的APP,CatchCat 上线24小时炸翻全网

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

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

大宇投资频道
@BTCdayu2 · 30,094
Telegram ranks this channel #12 of 85 here — alongside 84 others — read 8 September 2026
BlockBeats
@theblockbeats · 37,492
Telegram ranks this channel #28 of 92 here — alongside 91 others — read 1 September 2026
PANews Web3丨加密货币丨区块链新闻频道
@ChannelPANews · 24,042
Telegram ranks this channel #29 of 96 here — alongside 95 others — read 17 September 2026
币安公告
@binance_cn · 34,158
Telegram ranks this channel #35 of 84 here — alongside 83 others — read 3 September 2026
方程式新闻 BWEnews
@BWEnews · 72,766
Telegram ranks this channel #41 of 90 here — alongside 89 others — read 19 August 2026
OUTA Announcement
@outa_announcement · 27,557
Telegram ranks this channel #53 of 81 here — alongside 80 others — read 10 September 2026
舒琴比特币行情资讯(其他均为仿冒)
@bitebishuqin · 40,412
Telegram ranks this channel #61 of 90 here — alongside 89 others — read 30 August 2026
Btok News
@BtokMedia · 288,827
Telegram ranks this channel #62 of 88 here — alongside 87 others — read 17 August 2026
DeJob—Web3招聘求职频道📮
@DeJob_official · 46,726
Telegram ranks this channel #80 of 94 here — alongside 93 others — read 27 August 2026

This channel appears in 9 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“KK集团-(高频电棍⚡️打新版)” (@Kclub737226), 11,356 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/Kclub737226.

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.