Telegram RegisterThe public register of Telegram
Telegram profile photo for 區塊鏈CoCo公開頻道

Channel

區塊鏈CoCo公開頻道

@BTCco_co

On this record: Growth · Engagement · Reactions · Posts · Polls · Cite this entry

1,944subscribers

+30 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002276478732
TypeChannel
Username@BTCco_co
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 live30 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/BTCco_co

Growth

1,9091,9441,926.57 August 2026 — 1,914 subscribers7 August 2026 — 1,914 subscribers8 August 2026 — 1,912 subscribers15 August 2026 — 1,909 subscribers18 August 2026 — 1,911 subscribers21 August 2026 — 1,923 subscribers25 August 2026 — 1,944 subscribers27 August 2026 — 1,941 subscribers30 August 2026 — 1,944 subscribers7 August 202630 August 2026
9 measurements spanning 23 days, net +30. 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 1,904–1,949 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 07:531,944+3
27 Aug 2026, 17:381,941-3
25 Aug 2026, 04:041,944+21
21 Aug 2026, 23:461,923+12
18 Aug 2026, 09:591,911+2
15 Aug 2026, 12:561,909-3
8 Aug 2026, 17:421,912-2
7 Aug 2026, 20:461,914no change
7 Aug 2026, 18:231,914first reading

Engagement

15 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
17.9%
avg views ÷ 1,944 subscribers
Avg views / post
349
15 posts measured
Reaction rate
1.59%
reactions ÷ views · ER floor
Posts in window
15
of 15 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 11 of 15 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 7 August 2026
Posts held15 (6 August 20267 August 2026)
Views total5,229
Reactions total63
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 20:46 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

63 reactions across 11 posts, in 4 distinct kinds. The most used accounts for 47.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3047.6%
👍2844.4%
👏34.76%
🙏23.17%

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

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

7 Aug 2026, 15:28 UTC198 views4 reactionsread 7 August 2026

投票多的话我们后期影片就加入❤️

4

7 Aug 2026, 15:26 UTC202 viewsread 7 August 2026
Poll

宝子们想让coco加入黄金走势分析吗

  1. 想听,最近有参与👏83%
  2. 不用,现在种类挺好17%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

7 Aug 2026, 11:15 UTC329 views2 reactionsread 7 August 2026

比特幣上攻6萬5大關非常關鍵!上車機會要來了?格外註意!BTC正在預謀一場大戲!裸k結構給出的信號是什麼?警報已經拉響!接下來.....以太幣不聽勸就是要被爆!最新比特幣以太坊行情分析! https://youtu.be/-_ZZ74FYLJU

2

7 Aug 2026, 08:48 UTC350 views9 reactionsread 7 August 2026

🎉🎉🎉从5000U到14000U,只用了3天! 在交易里,亏掉本金不是最可怕的,最可怕的是连信心一起亏掉。 这位宝子,之前亏损到连自己下单都不敢了,带着最后一点期望找到了Coco。感谢这份信任,幸好没有辜负。盈利多少其实不是最重要的,最珍贵的是——找回了重新开始的勇气。

👍72

7 Aug 2026, 06:45 UTC364 views10 reactionsread 7 August 2026
Photo

#以太币🪙8月7日下午3点交易思路 📊交易策略: 1.突破1930就接多。 2.跌破1900做空。 以太币交易思路会围绕着1930-1900运行,如果想要把握小区间就是这个位置来做高抛低吸,但是CoCo建议大家等待跌破1900或突破的信号后再去入场。

👍91

7 Aug 2026, 03:45 UTC372 views3 reactionsread 7 August 2026

信任不是要来的,是赢来的! 最近Coco高级会员持续增加,说明市场正在用脚投票。每一笔新策略,都是对我交易逻辑的一次实盘验证。我不追求所有人都看懂我的策略,但看懂的人都已经在车上了。 市场永远不缺机会,缺的是能稳定抓住机会的人。新宝子欢迎上车,老朋友们继续跟紧——这轮冲刺,我们还在半山腰✊

3

6 Aug 2026, 16:09 UTC384 views4 reactionsread 7 August 2026

对于eth 1930压力位前面影片也有多次提及!有关注影片的宝子应该都知道

👍31

6 Aug 2026, 16:06 UTC384 views8 reactionsread 7 August 2026

#BTC 上方压力65000 #ETH 上方压力1930 以上区间已经三次测试

👍71

6 Aug 2026, 15:32 UTC389 views3 reactionsread 7 August 2026

误区与事实:『黄金下跌,比特币就会上涨』 乍一看,这似乎很符合逻辑。这两种资产都被视为避险工具:黄金是传统避险资产,而比特币则是现代的等价物。因此,许多人认为如果投资者抛售黄金,资金就会流向 BTC,反之亦然。 但在实际操作中,情况要复杂得多。当黄金下跌时,并不意味着 BTC 就一定会拉升。市场受到众多因素的驱动:美联储政策、通胀、流动性、地缘政治以及整体的投资者情绪。 因此,如果黄金遭遇抛售,不应盲目去囤积 BTC 并期待它能大幅暴涨。BTC 完全有可能只是横盘震荡,甚至跟着黄金一起下跌。 BTC 和黄金并不总是呈现负相关。

3

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

7 Aug 2026, 15:26 UTCAnonymous Poll81 voters

宝子们想让coco加入黄金走势分析吗

  1. 想听,最近有参与👏83%
  2. 不用,现在种类挺好17%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 15 most recent posts we hold, published 6 August 2026 to 7 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

“區塊鏈CoCo公開頻道” (@BTCco_co), 1,944 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/BTCco_co.

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.