当前清算指数已飙升到21,这是极其明显的“猎杀高倍多单”节奏,伴随着持仓量同步锐减,大量杠杆多头正被无情收割离场。⚔️ 更严峻的是,价格现已逼近最后的生死关卡——正在死磕测试上轮牛市的高点支撑。这里是多头最后的防线,退无可退。🛡 如果在这个关键区域,盘面依然看不到任何有效的买盘反抗,那么很遗憾,比特币大概率将彻底破位,直奔新低。🧘♂️
❤22👍9🔥9

Channel
@btc18688
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry
29,675subscribers
+9,149 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001880448894 |
|---|---|
| Type | Channel |
| Username | @btc18688 |
| Description | 这是一个顶级财富密码频道 平时会公布一些看好的币种 主抓二级山寨热点龙头代币 👉想进会员群私信 @bdaiydaige 👉双向私信点击 @Daiydaige_bot |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 66 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/btc18688 |
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 3 other registered channels. This entry also sits inside a group of 3 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @eth77896bnb/68225 Aug 2026, 07:51 UTC | @btc18688/6863 · this entry5 Aug 2026, 07:51 UTC | 1.00 | under a minute |
| @eth77896bnb/684817 Aug 2026, 05:30 UTC | @btc18688/6882 · this entry17 Aug 2026, 05:30 UTC | 1.00 | under a minute |
| @eth77896bnb/703525 Oct 2026, 06:42 UTC | @btc18688/7067 · this entry25 Oct 2026, 06:43 UTC | 1.00 | under a minute |
| @eth77896bnb/703626 Oct 2026, 04:44 UTC | @btc18688/7068 · this entry26 Oct 2026, 04:44 UTC | 1.00 | under a minute |
| @btc18688/7085 · this entry4 Nov 2026, 08:19 UTC | @eth77896bnb/70544 Nov 2026, 08:20 UTC | 1.00 | under a minute |
| @btc18688/7095 · this entry10 Nov 2026, 15:17 UTC | @eth77896bnb/706410 Nov 2026, 15:17 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @eth77896bnb | 45 (7/8 hand-verifiable sample passed) | 1.00 | under a minute | @eth77896bnb (25–20) |
| @qqbtceth1688 | 49 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (37–12) |
| @SMBL168 | 5 (5/5 hand-verifiable sample passed) | 1.00 | 14 minutes | this entry (5–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. 32 of the 37 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 93 comparable posts for this entry, running 31 July 2026 to 13 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 3 channels, the one whose matching posts we hold earliest is @eth77896bnb. That is a statement about our reading window, not a claim of authorship.
84,900 average views per post against 29,282 subscribers — an engagement rate of 289.9%. 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 | 45 of 46 published in the window (0 exact, 45 rounded by Telegram) |
| Views totalled | 3,819,550 |
| Mature posts only | 307.0% over 42 posts read at least 24h after publication |
| Subscribers | 29,282 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 | 99.952th percentile · 59.2× the cohort median |
| Uncertainty | ±0.103% 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_mutual · clone_source · err_high, last confirmed 14 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 3 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Nov 2026, 12:46 | 29,675 | +123 |
| 10 Nov 2026, 12:57 | 29,552 | +99 |
| 9 Nov 2026, 02:09 | 29,453 | +70 |
| 7 Nov 2026, 19:52 | 29,383 | +55 |
| 6 Nov 2026, 21:31 | 29,328 | +41 |
| 5 Nov 2026, 19:25 | 29,287 | +5 |
| 4 Nov 2026, 20:38 | 29,282 | +25 |
| 3 Nov 2026, 16:51 | 29,257 | +8 |
| 2 Nov 2026, 15:40 | 29,249 | +37 |
| 1 Nov 2026, 18:08 | 29,212 | +29 |
| 31 Oct 2026, 19:18 | 29,183 | +66 |
| 30 Oct 2026, 19:19 | 29,117 | +103 |
| 29 Oct 2026, 16:08 | 29,014 | +120 |
| 28 Oct 2026, 16:49 | 28,894 | +94 |
| 27 Oct 2026, 17:40 | 28,800 | +102 |
| 26 Oct 2026, 17:39 | 28,698 | +108 |
| 25 Oct 2026, 20:44 | 28,590 | +136 |
| 24 Oct 2026, 23:54 | 28,454 | +92 |
| 23 Oct 2026, 21:21 | 28,362 | +130 |
| 22 Oct 2026, 23:00 | 28,232 | first reading |
125 posts held, back to 31 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 154 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 13 November 2026 |
|---|---|
| Posts held | 125 (31 July 2026 – 13 November 2026) |
| Views total | 3,113,800 |
| Reactions total | 1,062 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Nov 2026, 13:07 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 14 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.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
5,934 reactions across 122 posts, in 8 distinct kinds. The most used accounts for 39.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2,354 | 39.7% | |
| 👍 | 1,823 | 30.7% | |
| 🔥 | 1,675 | 28.2% | |
| 🥰 | 42 | 0.708% | |
| 💋 | 17 | 0.286% | |
| 💘 | 11 | 0.185% | |
| 💯 | 7 | 0.118% | |
| 🙏 | 5 | 0.084% |
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 122 of the 125 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 5,934 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 125 most recent posts we hold, published 31 July 2026 to 13 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 32 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).
当前清算指数已飙升到21,这是极其明显的“猎杀高倍多单”节奏,伴随着持仓量同步锐减,大量杠杆多头正被无情收割离场。⚔️ 更严峻的是,价格现已逼近最后的生死关卡——正在死磕测试上轮牛市的高点支撑。这里是多头最后的防线,退无可退。🛡 如果在这个关键区域,盘面依然看不到任何有效的买盘反抗,那么很遗憾,比特币大概率将彻底破位,直奔新低。🧘♂️
❤22👍9🔥9
暂时的亏损不可怕,可怕的是执念太深。 及时止损出局,调整心态,冷静审视盘面 等戴哥重新制定下一步的交易计划。 活下来,才能等来真正的反转!💪🧘♂️🚀
👍15🔥9❤2
今天BTC插针下探至70,000美元关口,但随后的反弹力度极其微弱,市场买盘需求表现一般,多头显得有心无力。🩸 宏观面上,受科技巨头“老黄”丑闻影响,美股科技板块遭遇剧烈的估值调整,引发了全球风险市场偏好的同步受挫。在流动性趋紧的背景下,加密市场自然无法独善其身,只能跟着遭殃。🌪 在当前的极端行情下,做多头无疑是非常痛苦且煎熬的。但请记住交易铁律:永远不要死扛单! 🛑 如果跌破了预设的止损线,请务必果断认错跑路。在这个市场里,留得青山在,不怕没柴烧
❤14👍6🔥5💘1
11月12日 比特币以太坊行情分析 当前BTC陷入极度割裂的局面:美股涨它不跟,ETF连续5天流出转投股票,稳定币30天锐减142亿,场内增量资金面临枯竭。🩸最危险的是,杠杆已高悬99百分位,但资金费率迟迟未转负,说明多头仍在死扛,价格只能在下降楔形内贴着73,700美元枢纽苦苦磨底。盘面底线极其明确:72,000美元(已多次插针验证)不容有失,上方76,000美元是真正的复苏门槛。⚔️ ETH方面:陷入2000上方弱平衡,ETF持续失血🩸,多头遭清算但费率仍未转负。 操作建议: 日內支撐位:72,000-72,500 分批做多 日內阻力位:75,500-76,000 区间做空 今日策略已出,欢迎加入会员群,实时跟上策略布局。💀 财富列车跟单咨询👁 Daiy戴哥 财富列车备用联系👁 Daiy戴哥 财富列车试单体验😐 免费试单群
❤13👍6🔥4
🎯【戴哥公开频道】精准伏击,拒绝画饼!🎯 BTC多单于73,500美元附近顺利入场,目前浮盈已近1,200点!💰🔥 真正的交易指导,从不靠“暴涨暴跌”的噱头忽悠人,而是只给最坚定、最清晰的分析与策略。🛡📊 不玩套路,只做实事。跟紧节奏,让利润说明一切!🚀💎 ㊙️㊙️㊙️需要更多财富趋势密钥㊙️㊙️㊙️ 欢迎私信戴哥:✈️ ✈️✈️ https://t.me/BDaiydaige
👍12❤11🔥7💋1
11月09日 比特币以太坊行情分析 比特币早盘探底73,333美元创8月新低,日线收出长下影阴线,表明下方存在资金承接。当前盘面本质是强平踩踏引发的清算下跌,而非趋势定调。但在ETF失血、现货买盘缺席的背景下,站不稳75,700美元成本区前,反弹力度与持续性均受限。🧱 以太坊表现更弱,已逼近重要支撑区。盘面多空极度撕裂:一边是ETF流出叠加聪明钱做空,另一边是巨鲸低位扫货、散户硬扛与费率转负。⚔️ 操作建议: 回调至73,500-71,000 分批做多 今日策略已出,欢迎加入会员群,实时跟上策略布局。💀 财富列车跟单咨询👁 Daiy戴哥 财富列车备用联系👁 Daiy戴哥 财富列车试单体验😐 免费试单群
❤21🔥12👍10💘2
美国10月非农数据强劲超预期,直接重燃了华尔街对美联储12月加息的押注。最新定价显示,12月加息25个基点的概率已飙升至八成以上!📈🏦 强劲的就业市场让美联储有了继续紧缩的底气,高利率维持更久的预期迅速升温。
👍12❤11🔥11🥰5💋1
今晚21:30的非农数据是当前市场最大的变量。市场预期新增6.5万人,但近期12月加息概率已从约80%回落至68.7%,2年期美债收益率也下行了12个基点,宏观预期正悄然生变。📉 数据推演很明确:若非农明显弱于预期,加息预期降温,被压制的风险偏好将迎来修复窗口 📈;若数据不弱甚至偏强,宏观的“第一刀”将继续压制市场 📉。 在数据正式落地前,大资金大概率按兵不动。
❤24👍12🔥12💘3
11月05日 比特币以太坊行情分析 BTC/ETH的突破:是“相对企稳”,不是“绝对转强”,当前市场的“不确定性”已全面落地,且川普的失势反而让预期更加乐观。原油价格跌破两个月新低,这极大地缓解了加密市场的流动性压力。🛢💧从盘面看,短期难以出现深度回踩,中小级别支撑正在同步上移。下方极限回踩位最多在79,000-78,000美元附近。整体上攻动能强劲,至少要到82,000美元上方,才会迎来一次像样的调整。操作上顺势而为,回踩即是上车机会!🚀🐂 ETH与BTC高度相关,整体仍受宏观与加密市场情绪主导。相对BTC的强度若持续,可能吸引更多资金轮动,但需警惕ETF资金流与链上活跃度变化。 重点关注:11月6日的非农就业和12月加息概率 操作建议: 日內支撐位:78,300—78,800 做多 日內阻力位:81,300—81,800 做空 今日策略已出,欢迎加入会员群,实时跟上策略布局。💀 财富列车跟单咨询👁 …
❤20👍8💘3🔥2
🎯回顾11月初,我们在市场恐慌中明确提示75,000-76,500美元的黄金抄底区间。如今BTC强势突破8万关口,思路已获完美验证!📈 虽然中间经历洗盘波折,但大方向始终未出错。无论是此前从81,800美元带大家一路做空,还是这次底部的精准狙击,节奏皆在掌控。 拒绝马后炮,实力无需多言,行情就是最好的证明!💪🚀 更多实时点位与高利润暴富单,请进VIP会员群 👉想进会员群私信戴哥 https://t.me/BDaiydaige
👍13❤7🔥6🥰1
戴哥唯一TG:✈️ https://t.me/BDaiydaige
👍10❤7🔥6
民主党同时拿下两院,宏观预期落地引发BTC早间一波加速下探。但盘面极其强悍,刚好插针跌破76,000后迅速收针反弹,这说明链上资金承接力度非常强,目前价格重新回到78,000附近震荡。🧲 短线洗盘极其激烈,这两天上下翻飞搞了好几次,但大方向我认为绝对不会变,因为周线级别已经形成了非常清晰的底部转换结构。🧱 整体操作思路依旧明确:持有76,500多单的朋友,可以在78,500减仓50%锁定利润,余仓设保本损. 短线先看79,000美元突破!后续只要把这阵子的利空消化完毕,大概率会再次挑战短期新高。坚定看好11月月线必收阳!☀️💪🚀
❤14👍6🔥4
Showing the 12 most recent of 125 posts we hold for @btc18688. 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.
@btc18688 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
We recorded 2 posts on @btc18688 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 1 registered channel — 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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 15 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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 25 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 12 November 2026 — this entry's latest reading, not the date you are reading this.
“以太坊币圈行情分析频道” (@btc18688), 29,675 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/btc18688.
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.