Telegram RegisterThe public register of Telegram
Telegram profile photo for 强大的红牛社区.china 🇨🇳📈

Channel

强大的红牛社区.china 🇨🇳📈

@ChinaPump

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

12,531subscribers

+6,304 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-1001311645737
TypeChannel
Username@ChinaPump
Description我们是一个大型红牛社区,始终将客户信任放在首位 这里的所有项目都是研究,总是在投资之前学习 成长壮大 📈🔥 管理 @kingdout888 https://x.com/ChinaPumpCN
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live4 November 2026
Measurements held42
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/ChinaPump

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 91% 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 the other topics.

Growth

5,95712,8119,3847 August 2026 — 6,227 subscribers7 August 2026 — 6,222 subscribers10 August 2026 — 6,146 subscribers13 August 2026 — 6,103 subscribers16 August 2026 — 6,062 subscribers20 August 2026 — 5,957 subscribers23 August 2026 — 8,490 subscribers26 August 2026 — 8,465 subscribers29 August 2026 — 8,454 subscribers1 September 2026 — 8,402 subscribers4 September 2026 — 8,390 subscribers10 September 2026 — 12,811 subscribers12 September 2026 — 12,796 subscribers13 September 2026 — 12,789 subscribers15 September 2026 — 12,782 subscribers17 September 2026 — 12,771 subscribers25 September 2026 — 12,753 subscribers4 October 2026 — 12,701 subscribers8 October 2026 — 12,659 subscribers13 October 2026 — 12,642 subscribers14 October 2026 — 12,637 subscribers15 October 2026 — 12,629 subscribers16 October 2026 — 12,623 subscribers17 October 2026 — 12,619 subscribers18 October 2026 — 12,614 subscribers19 October 2026 — 12,615 subscribers20 October 2026 — 12,609 subscribers21 October 2026 — 12,602 subscribers22 October 2026 — 12,595 subscribers24 October 2026 — 12,591 subscribers25 October 2026 — 12,587 subscribers26 October 2026 — 12,584 subscribers27 October 2026 — 12,580 subscribers28 October 2026 — 12,577 subscribers29 October 2026 — 12,567 subscribers30 October 2026 — 12,562 subscribers31 October 2026 — 12,559 subscribers1 November 2026 — 12,550 subscribers1 November 2026 — 12,546 subscribers2 November 2026 — 12,539 subscribers3 November 2026 — 12,538 subscribers4 November 2026 — 12,531 subscribers12,5317 August 20264 November 2026
42 measurements spanning 90 days, net +6,304. 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 4,929–13,839 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 42
Measured (UTC)SubscribersChange
4 Nov 2026, 21:1712,531-7
3 Nov 2026, 23:0112,538-1
2 Nov 2026, 21:3912,539-7
1 Nov 2026, 23:4712,546-4
1 Nov 2026, 01:3812,550-9
31 Oct 2026, 02:5112,559-3
30 Oct 2026, 03:4912,562-5
29 Oct 2026, 05:5112,567-10
28 Oct 2026, 01:3712,577-3
27 Oct 2026, 01:5512,580-4
26 Oct 2026, 01:3612,584-3
25 Oct 2026, 04:1012,587-4
24 Oct 2026, 01:0012,591-4
22 Oct 2026, 22:2812,595-7
21 Oct 2026, 18:0112,602-7
20 Oct 2026, 11:3112,609-6
19 Oct 2026, 09:5612,615+1
18 Oct 2026, 11:5912,614-5
17 Oct 2026, 13:2812,619-4
16 Oct 2026, 09:5412,623first reading

Engagement

81 posts held, back to 3 August 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 20 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.54%
avg views ÷ 12,531 subscribers
Avg views / post
193
12 posts measured
Reaction rate
3.24%
reactions ÷ views · ER floor
Posts in window
22
of 81 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 4 of 12 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 5 November 2026
Posts held81 (3 August 2026 – 5 November 2026)
Views total2,316
Reactions total74
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Nov 2026, 06:49 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.

What this channel posts

Photos
≈3,040
Videos
≈84
Links
≈1,990

Lifetime counters from Telegram’s own channel header, read 5 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

147 reactions across 31 posts, in 12 distinct kinds. The most used accounts for 23.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🎉3423.1%
❤2517.0%
💯2315.6%
🏆1912.9%
🔥1912.9%
👍85.44%
👏74.76%
🤩42.72%
👾32.04%
🌚21.36%
🦄21.36%
👀10.68%

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

Measured over the 81 most recent posts we hold, published 3 August 2026 to 5 November 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

Telegram’s own ‘edited’ marker: 1 of 22 posts held from the last 30 days (4.55%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

5 Nov 2026, 06:48 UTC1 viewsread 5 November 2026
Photo

🏦 TODAY: Chainlink 将参与伦敦以太坊机构论坛 随着传统金融机构持续探索区块链基础设施,@chainlink $LINK 将于 11 月 12 日前往伦敦,参加以太坊 (@ethereum) $ETH 机构论坛。 目前,Swift、Euroclear、Mastercard、Fidelity 和 UBS 等大型机构已经在使用 Chainlink 的技术。 此前,Apex Group (@ApexGlobalGroup) 刚刚展示了与 ERC-3643 生态合作的链上债券方案,而 Chainlink 则通过 CCIP、ACE 和 Data Streams 提供底层基础设施支持。 随着机构不断探索区块链应用,为连接传统金融与链上市场的基础设施提供商创造了更多发展空间。

5 Nov 2026, 05:49 UTC1 viewsread 5 November 2026
Photo

$PUMP 它已经四次触及同, 条下降趋势线了。 现在,我们即将如愿以偿。@Pumpfun CA: pumpCmXqMfrsAkQ5r49WcJnRayYRqmXz6ae8H7H9Dfn 价格将强劲上涨。 卖方迟早会明白,我们不会轻易放弃。 敬请期待。https://pump.fun/

5 Nov 2026, 05:03 UTC1 viewsread 5 November 2026
Photo

📊 WATCH:BlackRock 的 BUIDL 基金在 BNB Chain 上规模达到 2.7233 亿美元 管理着 15.5 万亿美元资产的 BlackRock,目前已有 2.7233 亿美元的 BUIDL 基金部署在 BNB Chain 上,过去 7 天增长了 60.15%。 这规模占整个基金总价值的 13% 以上,凸显了 BNB Chain 在代币化现实世界资产领域不断提升的地位。 这也释放出个重要信号:机构资本正持续深入链上基础设施。 @BNBCHAIN

5 Nov 2026, 03:55 UTC1 viewsread 5 November 2026
Photo

⚡ BREAKING:ApeChain 转向 Chainlink CCIP,升级跨链基础设施 @Apecoin 正在从 @LayerZero_Core 迁移至 @Chainlink CCIP,为整个 @yugalabs 生态提供跨链基础设施。 此次迁移涵盖 ApeChain、Bored Ape Yacht Club 以及 APE 代币。包括 $APE 和 $USDC 在内的资产也将升级为 Chainlink Cross-Chain Tokens(CCT)。 此举旨在提升安全性与去中心化程度,并为整个生态中的 dApp、社区和数字资产提供更加顺畅的跨链互操作体验。 这标志着 Chainlink CCIP 将进步深入 Yuga Labs 生态。

4 Nov 2026, 13:11 UTC5 viewsread 5 November 2026
Photo

$HOOKR 正在拓展其在链上金融基础设施中的角色,目前是 Books 平台的基础交易对。🫡 通过与 oxsimplefarmer 和 StonkBrokers 的合作, 该生态系统正在通过 ETH 和 HOOKR 连接 PairToken 市场,支持在两个平台上的发行以及代币化收益。 更宏大的愿景是构建开放、可编程的资本市场,使金融工具和现金流能够转化为可交易的链上资产。0x18e674231a58c239dc7daedcffe15ec3a24cff5c HOOKR 正朝着更加互联的金融生态系统迈进。🚀

4 Nov 2026, 06:01 UTC6 viewsread 5 November 2026
Photo

$ANSEM 拥有 Solana 模因生态系统中最令人瞩目的发行故事之, 其市值在短短时间内从 35 万美元飙升至约 4 亿美元,令人瞠目结舌。🤯 CA: 9cRCn9rGT8V2imeM2BaKs13yhMEais3ruM3rPvTGpump 但它的发展历程也表明,代币的持久价值很大程度上取决于持续的领导力和社区参与。 近期的批评主要集中在项目最初的目标与其持续沟通之间的差距,些持有者仍在寻求开发团队更清晰的指导。 与此同时,钱包活动恢复以及关于补偿方案的讨论让 ANSEM 再次成为关注焦点。 该项目仍然拥有个耳熟能详的名字和成熟的社区,但重建信任需要的不仅仅是最初的成功。持续的沟通、透明的执行以及构建个有意义的生态系统至关重要。 对于 ANSEM 而言,下个阶段的关键在于证明其最初的愿景能够得到长期承诺的支持。🚀

3 Nov 2026, 03:52 UTC8 viewsread 5 November 2026
Photo

$CLAUDIA 的发展方向已超越了最初的 AI 内容创作, 它拥有更大的雄心:构建原创 AI IP,供其他创作者贡献和拓展。🤖 想象, 下,就像乐高积木, 样:每, 个新角色、每, 个创意、每, 次社区贡献,都可以成为不断增长的内容生态系统的, 部分。 CLAUDIA 的目标并非仅仅依赖于爆款或与名人的互动,而是创一个持续的创作和互动循环。 该项目正在通过投票争取社区支持,以期获得潜在的“登月计划”上市资格。与此同时,其故事仍在围绕着 280 万美元的市值不断展开。 2j5SaS7xy776qCBpyPQbZjyQSAtKiFgrwjfErthnW2ZM 在经历了之前的关注浪潮之后,CLAUDIA 的动态有所减少,但其 IP 构建方向为社区指明了清晰的发展方向。 下个里程碑是将这创意愿景转化为持续的内容、创作者的参与以及长久的投入。👀🔥

Showing the 12 most recent of 81 posts we hold for @ChinaPump. 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 1 registered channel — 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 4 November 2026 — this entry's latest reading, not the date you are reading this.

“强大的红牛社区.china 🇨🇳📈” (@ChinaPump), 12,531 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/ChinaPump.

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.