Telegram RegisterThe public register of Telegram
Telegram profile photo for 币圈合约交流社区

Channel

币圈合约交流社区

@zh_cn_zhcnusb_666

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Cite this entry

196subscribers

-27 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003667085366
TypeChannel
Username@zh_cn_zhcnusb_666
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 November 2026
Measurements held12
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/zh_cn_zhcnusb_666

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 24 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.

Observations

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.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also sits inside a group of 7 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@SSPEncryptedContract/130887 Aug 2026, 04:31 UTC@zh_cn_zhcnusb_666/1554 · this entry7 Aug 2026, 04:31 UTC1.00under a minute
@SSPEncryptedContract/130957 Aug 2026, 08:28 UTC@zh_cn_zhcnusb_666/1561 · this entry7 Aug 2026, 08:28 UTC1.00under a minute
@SSPEncryptedContract/130967 Aug 2026, 12:28 UTC@zh_cn_zhcnusb_666/1562 · this entry7 Aug 2026, 12:29 UTC1.00under a minute
@SSPEncryptedContract/131007 Aug 2026, 15:32 UTC@zh_cn_zhcnusb_666/1566 · this entry7 Aug 2026, 15:32 UTC1.00under a minute
@SSPEncryptedContract/131068 Aug 2026, 06:34 UTC@zh_cn_zhcnusb_666/1571 · this entry8 Aug 2026, 06:34 UTC1.00under a minute
@SSPEncryptedContract/131038 Aug 2026, 04:41 UTC@zh_cn_zhcnusb_666/1568 · this entry8 Aug 2026, 04:41 UTC0.91under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@SSPEncryptedContract7 (6/7 hand-verifiable sample passed)0.99under a minute@SSPEncryptedContract (7–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. 7 of the 7 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 8 comparable posts for this entry, running 7 August 2026 to 8 August 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 7 channels, the one whose matching posts we hold earliest is @xingchenshequ798. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 11 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.

Channels linked by matching posts

This channel is in a group of 7 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. 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.

1 more channel is in this same group but not listed individually here.

Growth

196223209.57 August 2026 — 223 subscribers8 August 2026 — 223 subscribers14 August 2026 — 220 subscribers22 August 2026 — 217 subscribers30 August 2026 — 213 subscribers7 September 2026 — 214 subscribers27 September 2026 — 207 subscribers8 October 2026 — 203 subscribers22 October 2026 — 204 subscribers29 October 2026 — 199 subscribers5 November 2026 — 198 subscribers15 November 2026 — 196 subscribers7 August 202615 November 2026
12 measurements spanning 100 days, net -27. 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 192–227 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Nov 2026, 09:57196-2
5 Nov 2026, 15:36198-1
29 Oct 2026, 17:09199-5
22 Oct 2026, 13:39204+1
8 Oct 2026, 09:37203-4
27 Sept 2026, 12:39207-7
7 Sept 2026, 20:00214+1
30 Aug 2026, 17:36213-4
22 Aug 2026, 16:34217-3
14 Aug 2026, 22:29220-3
8 Aug 2026, 10:31223no change
7 Aug 2026, 18:07223first reading

Engagement

13 posts held, back to 7 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 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 13 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

8 Aug 2026, 09:05 UTC2 viewsread 8 August 2026
Photo

晚上教学预告: 大山老师专注于裸K交易体系,擅长通过市场结构、交易区间、突破、测试与反转等核心逻辑解析行情,不依赖复杂指标,帮助交易者建立真正理解市场行为的能力。课程结合大量实战案例拆解,重点培养盘面判断能力、交易思维和执行纪律,让学员学会独立分析,而不是盲目跟单。 山猫老师以「十二金K」教学体系为核心,从目标规划、知识体系、学习方法到交易思维全面构建系统化认知。课程内容循序渐进,帮助新手建立完整的交易框架,也帮助有经验的交易者完善自己的交易体系,实现从“会交易”到“懂交易”的提升。 今晚直播,欢迎准时进入直播间,一起学习、一起成长,让交易从凭感觉变成有逻辑、有体系。 咨询助理:@hyqzzz 领取会议号即可。 交流群链接:https://t.me/+qjUYbX9ffsQyYmIx

Signed 助理乔治 进内部群私信我 主动私信皆为骗子。无资金往来。

8 Aug 2026, 06:34 UTC3 viewsread 8 August 2026
Photo

今日午间消息整体呈现“AI投资升温、加密监管承压”的格局。 特朗普媒体集团终止与Crypto.com的代币及预测市场合作,叠加美国加密监管法案再度延期,《CLARITY Act》甚至可能拖至中期选举前博弈,短期或影响行业信心与资金情绪。 整体来看,AI与关键资源投资继续释放积极信号,但加密监管进程反复、合作项目终止带来一定压力。市场短期或维持震荡分化,重点关注监管进展、机构资金流向及地缘局势变化。

Signed 助理乔治 进内部群私信我 主动私信皆为骗子。无资金往来。

8 Aug 2026, 05:08 UTC5 viewsread 8 August 2026
Photo

零贰老师开播啦 擅长:日内短线—- SMC订单流—中长线布局 #腾讯会议:901-588-1279 想到内部群学习跟上节奏咨询助理:@hyqzzz

Signed 助理乔治 进内部群私信我 主动私信皆为骗子。无资金往来。

8 Aug 2026, 04:41 UTC5 viewsread 8 August 2026
Photo

BTC整体趋势依然由多头主导,价格成功站稳65000附近后,多头仍占据主动。不过MACD红柱缩短、KDJ高位钝化,意味着短线继续追高的性价比已经下降,更可能进入高位震荡消化阶段。 操作思路依旧以回踩低多为主,不建议在65000上方盲目追高。若后续放量突破65350并有效站稳,则有望进一步挑战65700-66000区域;若65350附近持续承压,同时MACD红柱继续缩短并形成死叉,则需警惕短线回踩64850甚至64550附近完成修正后,再重新寻找顺势做多机会。整体来看,中期上涨结构保持完好,但短线已经进入突破后的震荡整理阶段。 交流群链接:https://t.me/+qjUYbX9ffsQyYmIx

Signed 助理乔治 进内部群私信我 主动私信皆为骗子。无资金往来。

8 Aug 2026, 01:04 UTC5 viewsread 8 August 2026
Photo

坚持交易的人都知道。 赚钱的时候,没人会羡慕你熬过多少夜。 亏钱的时候,却只有你自己承担所有压力。 所以,比赚钱更重要的是活下来。 欢迎来到汇盈社区,和一群还在认真做交易的人一起交流。 进群助理:@hyqzzz

Signed 助理乔治 进内部群私信我 主动私信皆为骗子。无资金往来。

7 Aug 2026, 15:32 UTC10 viewsread 8 August 2026
Photo

🔥汇盈社区阿伦老师|加密夜盘直播今晚开炸! ⏰今晚12点 全程陪跑,不玩虚的、不扯废话! ✅ 大饼二饼方向直给,多空信号不墨迹 ✅ 主流山寨币轮动机会,精准筛能涨的标的 ✅ 实盘带单+思路拆解,新手也能轻松跟车 12点锁定会议室,阿伦老师带你吃透夜盘红利,一起收米 咨询助理:@hyqzzz 直播间免费。

Signed 助理乔治 进内部群私信我 主动私信皆为骗子。无资金往来。

7 Aug 2026, 14:30 UTC9 viewsread 8 August 2026
Photo

相信这个震荡行情,大家都不好做单。不是被扫就是在扛。不如加入社区多一个选择。还可以完善自己的交易体系。 进群助理:@hyqzzz 交流群链接:https://t.me/+qjUYbX9ffsQyYmIx

Signed 助理乔治 进内部群私信我 主动私信皆为骗子。无资金往来。

7 Aug 2026, 12:29 UTC8 viewsread 8 August 2026
Photo

ETH与BTC目前整体保持偏强走势,但都已进入关键压力区域,短线追高风险开始上升。 ETH运行于1919附近,4小时级别自1854止跌后持续反弹,目前再次测试1920—1927压力区。MACD多头动能回暖,RSI升至67附近,KDJ高位金叉,行情具备突破条件,但指标已接近超买。若放量站稳1927,有望继续上探1950—1975;若突破失败,则关注1900—1890支撑,失守后可能回踩1870—1860。 BTC运行于65049附近,1小时级别快速拉升至65213后进入高位整理。当前多头结构仍在,但MACD动能减弱,RSI达到72附近,KDJ处于高位,短线存在回踩消化需求。若突破并站稳65200—65400,可进一步关注65600—66000;若持续受压,则留意64800—64600支撑,失守后关注64200—64000区域。 当前行情看似强势,真正难点却在于突破真假难辨:追高容易遇到回调,过早做空又可能被继续拉升。想及时掌…

Signed 助理乔治 进内部群私信我 主动私信皆为骗子。无资金往来。

7 Aug 2026, 08:28 UTC6 viewsread 8 August 2026
Photo

ETH目前运行于1905附近,4小时级别在突破1900关口后进入高位横盘整理。此前价格自1827附近启动反弹,快速拉升至1927.19附近受阻,随后连续多个4小时K线围绕1900-1915区间震荡,说明多空双方正在重新积累力量。从K线结构来看,虽然高点未能继续刷新,但低点始终维持在1895附近,整体仍属于上涨后的强势整理,而非趋势转空。 内部群正在布局中,欢迎你加入 进群助理:@hyqzzz

Signed 助理乔治 进内部群私信我 主动私信皆为骗子。无资金往来。

7 Aug 2026, 08:01 UTC7 viewsread 8 August 2026
Photo

利润都是慢慢积攒起来的。本金也是慢慢滚起来的。 交易不是看谁盯盘时间最长,吃的最多,而是看谁的方法更正确,活的更久。 内部群不仅聊行情,更注重交易纪律和思路。 进群助理:@hyqzzz

Signed 助理乔治 进内部群私信我 主动私信皆为骗子。无资金往来。

7 Aug 2026, 06:16 UTC5 viewsread 8 August 2026
Photo

今日午间消息整体呈现“监管进程受阻、机构布局持续”的格局。 市场情绪方面,Coinbase比特币溢价指数已连续80天为负,反映美国市场现货买盘相对不足,短期资金态度仍偏谨慎。 整体来看,RWA和机构配置继续提供长期支撑,但监管延期、稳定币准入限制及美国买盘不足可能压制短期表现,市场预计延续震荡分化。

Signed 助理乔治 进内部群私信我 主动私信皆为骗子。无资金往来。

7 Aug 2026, 05:10 UTC7 viewsread 8 August 2026
Photo

启明老师开播啦 擅长:波段交易—量化策略—短线捕捉 #腾讯会议:901-588-1279 想到内部群学习跟上节奏咨询助理:@hyqzzz 交流群链接:https://t.me/+qjUYbX9ffsQyYmIx

Signed 助理乔治 进内部群私信我 主动私信皆为骗子。无资金往来。

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

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

“币圈合约交流社区” (@zh_cn_zhcnusb_666), 196 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/zh_cn_zhcnusb_666.

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.