SOSO 搜搜 把 Telegram 搜索和发现放在一个入口。 想继续找频道、群组、帖子或贴纸,直接输入关键词。 也可以从发现页继续浏览同类入口。 🔗 本频道专属邀请链接 https://t.me/sososo?start=autopromo_-1001968344875_6267105255_soso_ef0f897d
🎉14🔥12👍8❤4
Signed SOSO搜搜

Channel
@qihangbtc1
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
10,076subscribers
-470 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001968344875 |
|---|---|
| Type | Channel |
| Username | @qihangbtc1 |
| Description | 主流币BTC/ETH!具体入场时机、点位,免费分享! 24小时提示信号,带你抓住时机、锁定收益! 拒绝无效喊单✨ 用数据+逻辑为每一笔交易注入确定性✨ 双向机器人: @qihangbtcBOT VIP咨询: @btcqihang |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 November 2026 |
| Measurements held | 63 |
| Confirmed unchanged | 1 time, most recently 13 November 2026 |
| On Telegram | t.me/qihangbtc1 |
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @btcyouliang/527229 Jul 2026, 12:01 UTC | @qihangbtc1/2333 · this entry29 Jul 2026, 12:04 UTC | 1.00 | 4 minutes |
| @btcyouliang/53938 Oct 2026, 14:11 UTC | @qihangbtc1/2475 · this entry8 Oct 2026, 14:29 UTC | 1.00 | 17 minutes |
| @btcyouliang/53988 Oct 2026, 14:18 UTC | @qihangbtc1/2480 · this entry8 Oct 2026, 14:29 UTC | 1.00 | 11 minutes |
| @btcyouliang/54039 Oct 2026, 10:33 UTC | @qihangbtc1/2487 · this entry9 Oct 2026, 10:34 UTC | 1.00 | 72 seconds |
| @btcyouliang/541628 Oct 2026, 18:57 UTC | @qihangbtc1/2501 · this entry28 Oct 2026, 19:00 UTC | 1.00 | 3 minutes |
| @btcyouliang/541728 Oct 2026, 19:00 UTC | @qihangbtc1/2502 · this entry28 Oct 2026, 19:00 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @btcyouliang | 14 (7/8 hand-verifiable sample passed) | 1.00 | 4 minutes | @btcyouliang (14–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 11 of the 14 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 18 comparable posts for this entry, running 20 July 2026 to 12 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Of the group of 2 channels, the one whose matching posts we hold earliest is @btcyouliang. That is a statement about our reading window, not a claim of authorship.
192,000 average views per post against 10,078 subscribers — an engagement rate of 1909.6%. Across the 2,085 registered channels in the same cohort — 10,003–31,622 subscribers, posting mainly in Chinese — the middle half sit between 1.76% and 11.0%, with a median of 4.89%.
| Window | 30 days (6 October 2026 – 5 November 2026) |
|---|---|
| Posts measured | 18 of 18 published in the window (0 exact, 18 rounded by Telegram) |
| Views totalled | 3,464,100 |
| Mature posts only | 1909.6% over 18 posts read at least 24h after publication |
| Subscribers | 10,078 measured 4 November 2026 |
| Cohort | b10000:zho · 2,085 channels · p10 0.495% · p25 1.76% · p50 4.89% · p75 11.0% · p90 24.0% |
| Position in cohort | 100.000th percentile · 390.3× the cohort median |
| Uncertainty | ±0.288% of the figure, from Telegram’s rounding |
| Post language | Chinese · 100.0% of the window’s posts |
When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the keys clone_copy · err_high, last confirmed 13 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Nov 2026, 17:07 | 10,076 | +9 |
| 10 Nov 2026, 23:47 | 10,067 | -9 |
| 9 Nov 2026, 09:49 | 10,076 | -5 |
| 7 Nov 2026, 23:54 | 10,081 | +3 |
| 6 Nov 2026, 18:27 | 10,078 | -2 |
| 5 Nov 2026, 14:55 | 10,080 | +2 |
| 4 Nov 2026, 16:51 | 10,078 | +5 |
| 3 Nov 2026, 14:00 | 10,073 | -4 |
| 2 Nov 2026, 14:05 | 10,077 | +3 |
| 1 Nov 2026, 11:36 | 10,074 | -14 |
| 31 Oct 2026, 13:56 | 10,088 | -1 |
| 30 Oct 2026, 13:01 | 10,089 | -11 |
| 29 Oct 2026, 09:59 | 10,100 | -12 |
| 28 Oct 2026, 05:07 | 10,112 | -1 |
| 27 Oct 2026, 02:51 | 10,113 | -10 |
| 26 Oct 2026, 00:37 | 10,123 | -2 |
| 25 Oct 2026, 00:25 | 10,125 | -13 |
| 24 Oct 2026, 02:57 | 10,138 | -8 |
| 23 Oct 2026, 02:39 | 10,146 | -16 |
| 21 Oct 2026, 23:40 | 10,162 | first reading |
87 posts held, back to 14 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 65 pages of 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.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 87 (14 July 2026 – 16 November 2026) |
| Views total | 1,052,010 |
| Reactions total | 500 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Nov 2026, 11:58 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 16 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.
3,795 reactions across 86 posts, in 8 distinct kinds. The most used accounts for 26.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1,002 | 26.4% | |
| 🎉 | 961 | 25.3% | |
| 👍 | 928 | 24.5% | |
| 🔥 | 889 | 23.4% | |
| 🐳 | 7 | 0.184% | |
| 😇 | 6 | 0.158% | |
| 🤗 | 1 | 0.026% | |
| 🫡 | 1 | 0.026% |
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 86 of the 87 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 3,795 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 87 most recent posts we hold, published 14 July 2026 to 16 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.
Telegram’s own ‘edited’ marker: 0 of 11 posts held from the last 30 days (0%) 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).
SOSO 搜搜 把 Telegram 搜索和发现放在一个入口。 想继续找频道、群组、帖子或贴纸,直接输入关键词。 也可以从发现页继续浏览同类入口。 🔗 本频道专属邀请链接 https://t.me/sososo?start=autopromo_-1001968344875_6267105255_soso_ef0f897d
🎉14🔥12👍8❤4
Signed SOSO搜搜
现货上的规则,之前与大家讲过,周期标记的底部基本就是中期选举之后的时间点,这次如果真的有深度回撤,想现货抄底的就不要犹豫了 现在虽然说加息周期从预防式变为周期式,黄仁勋出事,选举也没提加密什么事情,但行情的低点基本都是在冰点中产生,个人看法现在即使不是冰点也无限接近了 如果要现货抄底,68000以下就开始分批定投吧,AI,半导体,存储,电力,稳定币,纳指,只要是头部的,买就行了,前提是能接受20%以上的现货亏损并且能长期持有的,不会错!
🔥16👍15🎉11❤6
Signed Crypto 启航
大洗确实来了,这里属于日线级别破位,千万不要头铁去抄底,如果反弹收不回来74500以上,那日线级的下跌空间就会打开 这里还有一个点,从上周开始行情的下探都是属于阴跌破位,并没有出现明显的极速下跌,要深度洗盘还差一轮插针 如果要操作,现在的阶段只高空,见图74500-75000,只要给机会,降低杠杆只做反弹空,止损76500以上,目标70000-67000
👍14❤13🎉10🔥7
Signed Crypto 启航
先说两个本人已经进场抄底的机会,SNDk以及MU,存储版块跌到目前这种地步就代表AI泡沫溢价已经差不多出清了,剩余的价值就是股票本身的价值了 本次抄底的是现货位置,不作为合约的抄底意见。长期持有的位置,MU位置是700-650,止损550以下;SNDK位置840-800,止损660。止盈目标空间见图🌟
❤19🔥14👍9🎉4
Signed Crypto 启航
这波到目前已经跌了一万多点,思路基本上是兑现了,近期也没有更新,主要原因是行情确实没有什么可讲的且已经说明思路了,先恭喜相信本社区的小伙伴们🚀
🎉13❤11👍8🔥7
Signed Crypto 启航
11月10日的美国CPI,是今天市场关注的重点。数据公布前后,美元、美债收益率以及加密市场都可能出现明显波动。 如果通胀高于预期,市场对美联储继续加息的担忧可能升温,ETH仍有继续承压的可能; 如果通胀明显降温,才有机会为风险资产争取一轮喘息时间。 资金面也没有明显改善。Farside数据显示,美国现货以太坊ETF在11月9日净流出约1.846亿美元 说明当前承接资金依然偏弱,但ETF数据只是观察市场资金的一项指标,不能单独决定价格方向。
❤13👍12🎉11🔥11
Signed Crypto 启航
结构上还是在4小时的下行通道,现在的消息还没全部落地,做单的空间比较小 因为要关注两个价格区,82000是本周的阻力区,但是已经测试过一次;84000是这个下行阶段的阻力区。 要入场可以取个均价83000左右挂限价进场,止损84800。做多的话目前没有建议,资费偏高,追车的人太多,缺一波大洗❗️
🔥16❤12🎉11👍8
Signed Crypto 启航
市场定价12 月加息概率从一周前的76%升到86%左右,10 年期美债站上5%以上,2年期也在涨。措辞偏鹰,市场反应却很平静,属于没超出预期吧,已经被提前定价了一部分 之后真正的考验是12月。如果11月CPi继续走高,2027年加 3 次的担心可能会变成现实。
👍13🎉11❤10🔥8
Signed Crypto 启航
利率落地维持不变,维持在 3.75%–4%,符合预期,实际要比预期更鹰! 投票:10 比 2。 理事库克和克利夫兰联储主席哈马克投了反对票主张现在就加息。9 月那次加息是 12 比 0 全票通过,这次开始出现分歧,而且分歧是往鹰派方向走。 声明措辞从经济增长从稳健上调为强劲,通胀依然偏高。原来政策有助于通胀回到 2%那句话删了,换成需要更多信息来决定立场。就是把乐观的立场删了
👍15🔥12🎉10❤8
Signed Crypto 启航
最近更新没有那么频繁,波动太小,操作也不会有空间,宏观上来说下今天晚上的利率决议吧,目前会还没有开完,说下目前已知的信息
❤15🎉11👍10🔥9
Signed Crypto 启航
市价8.2W,干了,兄弟们🌟
👍21❤13🎉13🔥9🐳3
Signed Crypto 启航
最低79700,差了一点; 现在反弹,下跌趋势没有改变,市价82000左右就可以直接进,止损83200上方,前低还是目标🌟
🎉17❤12👍8🔥8
Signed Crypto 启航
Showing the 12 most recent of 87 posts we hold for @qihangbtc1. 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 13 November 2026 — this entry's latest reading, not the date you are reading this.
“启航比特币币圈策略分析🚀” (@qihangbtc1), 10,076 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/qihangbtc1.
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.