Channel
@btcaptain_new
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
71subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001539155428 |
|---|---|
| Type | Channel |
| Username | @btcaptain_new |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 9 October 2026 |
| On Telegram | t.me/btcaptain_new |
Other / unclassifiable — 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 28 September 2026 and assigned it the closest of 31 fixed categories, at 62% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Oct 2026, 00:59 | 71 | -1 |
| 14 Sept 2026, 19:18 | 72 | -1 |
| 15 Aug 2026, 11:28 | 73 | -1 |
| 9 Aug 2026, 22:01 | 74 | no change |
| 7 Aug 2026, 15:46 | 74 | first reading |
19 posts held, back to 8 August 2023 — 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 19 posts for this entry, the most recent from 24 March 2026. An engagement rate over an empty window would be a number about nothing.
33 reactions across 11 posts, in 3 distinct kinds. The most used accounts for 57.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 19 | 57.6% | |
| ❤ | 13 | 39.4% | |
| 🥰 | 1 | 3.03% |
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 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 33 reactions 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 8 August 2023 to 24 March 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.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 29 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
https://www.youtube.com/watch?v=COGkWR82yT4
👍9
#ordi作为铭文系列的龙头，尽管因为开发者的不认可，出现的短时间的回落，但是也不影响它目前的价值；尽管说下个版本修复漏洞，但是因为区块链的不可篡改性，所以现有的铭文并不会删除掉，若漏洞被修复掉，#ordi反倒会成为稀缺品，所以可以找机会再次入场。
#eth与#btc走势类似，目前顶部位置2398认为是中期三浪，但是从大周期来看，以太已经突破了2129位置较强的压力位，也未出现反包结构，目前下跌的位置反倒成为了一个支撑位，所有以太的四浪回踩预计不会太深，预计在0.786-0.5位置，也就是2218-2157区间。五浪位置则预计在大周期支撑位2500附近。特别注意，若本周周线未能收上去，需要考虑清仓锁住利润。
场内稳定币水平回到2021年10月20附近的位置，对应时间的BTC价格范围在61K～67K，是一个杠杆水平相当高的状态。目前牛市情绪并没有完全被点燃，或者杠杆没有被拉满。 牛初的二级行情选择较为强势的币去布局，洗盘太久或者无序震荡的不要去考虑，毕竟时间紧任务重。
👍1
#SPX 标普500周线级别还是比较强势，再冲哥三五个点就能破前高。美股没有回调，加密大回调，通常是风险资产与科技股资产之间互相时间上有滞后效应。SPX能继续维持稳步上涨，BTC一月的更高五浪顶指日可待。
#BTC 连续涨了十周，44K认为是中级别三浪，四浪回踩预计在0.786～1的位置，38K附近找入场点。 聪斐波那契扩展看，1.618对应44K附近也是阶段三浪顶，非常完美的技术走势。 预计1月构建最终五浪，五浪预计48K以上。2、3月注意abc回调风险。
❤3
先止盈一部分吧，不能太贪心
👍3
稳扎稳打，低倍合约。
❤2
最近比较忙没怎么更新，昨天开了两单，有空会发一下最近对市场的看法。10月以空为主，逢高空。11月以多为主，逢低多。12月以空为主。细节推论过到时候出视频。
❤2🥰1
#DXY 美元指数通道见顶，103.5是比较关键的位置，突破回踩则获得更多流动性，市场资金回流美元。如果受阻回落，则美元有一定几率又会流向美股等风险资产。世界上所有资产都是有非常强相关性的，目前的位置也非常重要，无论大盘是走暴力反弹的剧本，还是走美元强势突破的剧本，唯一需要做的就是跟随趋势关注趋势。
❤2
想要抄底的同学，25k～25.5k附近有非常高的盈亏比，跌破25k就止损，买不了吃亏买不了上当，反弹空间27k～28.5k之间，如果在9月份之前没突破28.4k的话，则整体行情继续延续空头结构。目前认为介入现货也只是抢反弹，盈亏比合适就介入而不是无脑多。如果点位拿捏不太准的，可以每天分批定投，这批货的目标位就放在向上10%左右的空间。
❤4
Showing the 12 most recent of 19 posts we hold for @btcaptain_new. 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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“比特船长-交易笔记” (@btcaptain_new), 71 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/btcaptain_new.
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.