Channel
@cctv8
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
84subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002263927834 |
|---|---|
| Type | Channel |
| Username | @cctv8 |
| Description | 内容为个人经验分享，非投资建议，也许会因为持币等因素而不够客观，请做好自己的研究。 |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/cctv8 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 17:16 | 84 | no change |
| 7 Aug 2026, 09:33 | 84 | first reading |
19 posts held, back to 1 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 1 pageof Telegram’s post history, 20 posts per page.
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 6 of 10 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 19 (1 July 2026 – 6 August 2026) |
| Views total | 2,572 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 17:16 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.
Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
5 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 80.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 💊 | 4 | 80.0% | |
| ❤ | 1 | 20.0% |
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 6 of the 19 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 5reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 1 July 2026 to 6 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.
比特币 方向：做多 入场：6.4万附近附近 信心度：中 倍数：10倍 仓位：10% 止盈：点位1：6.46附近（求稳） 点位2：6.52附近 点位3：6.66 止损：小幅跌破6.33一点。 理由：比特币支撑位是在6.4和6.34万，可以在支撑位上方一点做多吃反弹。 注：挂单不要挂整数位，难以成交。挂在支撑位上方一点更容易成交。现在由于假跌破和假突破很多，所以为了预防这种情况，咱们止损挂低一点，调低盈亏比，大幅增加胜率来做单。
比特币 方向：做空 入场：6.41-6.44万附近 信心度：中 倍数：10倍 仓位：10%每次 止盈：点位1：6.35附近（求稳） 点位2：6.3 点位3：6.23万 止损：小幅涨破6.47 理由：6.42万附近阻力还可以，可以在这里吃个回踩。 注：挂单不要挂整数位，难以成交。挂在阻力区下方一点更容易成交。现在由于假跌破和假突破很多，所以为了预防这种情况，咱们止损挂高一点，调低盈亏比，大幅增加胜率来做单。
❤1
BTC 方向：做多 入场：6.14-6.19附近 信心度：中 倍数：10倍 仓位：10% 止盈：点位1：6.3附近（求稳） 点位2：6.39附近 点位3：6.48 止损：小幅跌破6.09一点。 理由：比特币6.14附近支撑不错，可以在支撑位上方做个反弹。 注：挂单不要挂整数位，难以成交。挂在支撑位上方一点更容易成交。现在由于假跌破和假突破很多，所以为了预防这种情况，咱们止损挂低一点，调低盈亏比，大幅增加胜率来做单。
💊1
比特币跌完了？可以抄底了吗，谈谈当前两个重要交易机会！ 1. 先说比特币，没有丝毫意外，还在下跌盘整中。昨天有提到过，这次BTC的底部很可能是会在6.17万附近。那昨天比特币跌到了6.24，非常非常接近了，再来一点咱们就可以出手了！ 2. 那除了BTC，原油也来机会了！正向着咱们的预期入场价格90附近到来，今天凌晨已经到了88.3，在接近90附近我就会逢高布局空单。原油咱们非常的稳，之前90做空，80出头止盈，之后反弹了没有着急立刻冲进去，直到近期再临90附近咱们才考虑重新入场。 3. 其实比特币也一样，咱们上一波在6.3万做完反弹后就一直没急着重新入场，耐心等到了6.24万，再跌一点我就会出手。对于各个标地的支撑和阻力位是比较精确的，并且也有耐心，因为在高位入场风险更大、盈利还低。 4. 然后最近美光大家也非常关心，咱们第一波是在700附近支撑位入场的，吃了不小的反弹。第二次的话 我还是选择700附近这个强支撑，来了…
💊1
比特币 方向：做多 入场：6.33-6.38附近入场 信心度：中 倍数：10倍 仓位：10% 止盈：点位1：6.47附近（求稳） 点位2：6.56附近 点位3：6.67 止损：小幅跌破6.28一点。 理由：比特币6.35附近支撑不错，可以在这里做个反弹。 个人想法：挂单不要挂整数位，难以成交。挂在支撑位上方一点一点更容易成交。现在由于假跌破和假突破很多，所以为了预防这种情况，咱们止损挂低一点，调低盈亏比，大幅增加胜率来做单。
💊1
比特币 方向：做多 入场：6.47附近入场，6.37附近补仓 信心度：中 倍数：10倍 仓位：10% 止盈：点位1：6.56附近（求稳） 点位2：6.67附近 点位3：6.75 止损：小幅跌破6.32一点。 理由：比特币6.47和6.36支撑位都不错，可以在支撑位上方挂单做个反弹。 个人想法：挂单不要挂整数位，难以成交。挂在支撑位上方一点一点更容易成交。现在由于假跌破和假突破很多，所以为了预防这种情况，咱们止损挂低一点，调低盈亏比，大幅增加胜率来做单。
💊1
以太坊 方向：做空 入场：2040附近入场，2060补仓 信心度：中高 倍数：10倍 仓位：10%每次 止盈：点位1：2000附近（求稳） 点位2：1960附近 点位3：1860 止损：小幅涨破2075一点 理由：以太坊2050-2060大阻力区，可以在阻力区的上下沿分2次入场，胜算不错。 注：挂单不要挂整数位，难以成交。挂在阻力区下方一点更容易成交。现在由于假跌破和假突破很多，所以为了预防这种情况，咱们止损挂高一点，调低盈亏比，大幅增加胜率来做单。
这单来了还可以再做一次。第二次仓位小一点做。 BTC 方向：做空 入场：6.68-6.73附近 信心度：中 倍数：10倍 仓位：10% 止盈：点位1：6.56附近（求稳） 点位2：6.48附近 点位3：6.37 止损：小幅涨破6.8一点 理由：6.73附近阻力还可以，可以在这里吃个回踩。 注：挂单不要挂整数位，难以成交。挂在阻力区下方一点更容易成交。现在由于假跌破和假突破很多，所以为了预防这种情况，咱们止损挂高一点，调低盈亏比，大幅增加胜率来做单。
比特币可能突破了，ETH不知道会不会被拉着往上，所以ETH这单1940的用小仓位来做吧，平一半。 比特币咱们会在6.7万空，ETH1950突破的话，就是2050空
ETH 方向：做空 入场：1935-1945附近 信心度：中 倍数：10倍 仓位：10% 止盈：点位1：1905附近（求稳） 点位2：1880附近 点位3：1860 止损：小幅涨破1958一点 理由：1945附近阻力还可以，可以在这里吃个回踩。 注：挂单不要挂整数位，难以成交。挂在阻力区下方一点更容易成交。现在由于假跌破和假突破很多，所以为了预防这种情况，咱们止损挂高一点，调低盈亏比，大幅增加胜率来做单。
Sol 方向：做多 入场：72-73附近 信心度：中 倍数：5倍 仓位：10% 止盈：点位1：76附近（求稳） 点位2：80附近 点位：83 止损：小幅跌破前70一点。 理由：Sol 72附近强支撑，可以做多一手。 注：挂单不要挂整数位，难以成交。挂在支撑位上方一点更容易成交。现在由于假跌破和假突破很多，所以为了预防这种情况，咱们止损挂低一点，调低盈亏比，大幅增加胜率来做单。
以太坊这单第三次做了，只能小仓位，现货更好。 ETH 方向：做多 入场：1720-1730附近入场 信心度：中 倍数：10倍 仓位：10% 止盈：点位1：1765附近（求稳） 点位2：1790附近 点位3：1820 止损：小幅跌破1700一点。 个人想法：挂单不要挂整数位，难以成交。挂在支撑位上方一点一点更容易成交。现在由于假跌破和假突破很多，所以为了预防这种情况，咱们止损挂低一点，调低盈亏比，大幅增加胜率来做单。
Showing the 12 most recent of 19 posts we hold for @cctv8. 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.
Citation-graph rank — 557,432 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 4 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.
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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“币圈交易日记💸” (@cctv8), 84 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/cctv8.
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.