Telegram RegisterThe public register of Telegram
Telegram profile photo for 金色财经/币圈快讯7*24小时

Channel

金色财经/币圈快讯7*24小时

@jinseBTC

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

23,705subscribers

+56 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001549184965
TypeChannel
Username@jinseBTC
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live2 September 2026
Measurements held26
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/jinseBTC

Topic

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 52% 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.

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 word for word on 2 other registered channels. They sit inside a group of 4 channels that share the same post bodies 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
@jinseBTC/218904 · this entry7 Aug 2026, 22:00 UTC@niuniubtc/116057 Aug 2026, 22:00 UTC0.98under a minute
@jinseBTC/218903 · this entry7 Aug 2026, 21:50 UTC@niuniubtc/116047 Aug 2026, 21:50 UTC0.97under a minute
@jinseBTC/218897 · this entry7 Aug 2026, 20:52 UTC@niuniubtc/115967 Aug 2026, 20:52 UTC0.97under a minute
@jinseBTC/218899 · this entry7 Aug 2026, 21:06 UTC@niuniubtc/115987 Aug 2026, 21:06 UTC0.96under a minute
@jinseBTC/218909 · this entry7 Aug 2026, 22:26 UTC@niuniubtc/116117 Aug 2026, 22:26 UTC0.94under a minute
@jinseBTC/218904 · this entry7 Aug 2026, 22:00 UTC@dnybtc/118077 Aug 2026, 22:00 UTC0.98under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@niuniubtc5 (5/5 hand-verifiable sample passed)0.97under a minutethis entry (50)
@dnybtc5 (5/5 hand-verifiable sample passed)0.97under a minutethis entry (50)

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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 70 comparable posts for this entry, running 6 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).

Across the whole group of 4, the earliest publisher we hold is @dnybtc. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 8 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 3 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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.

Growth

23,60923,71423,661.57 August 2026 — 23,649 subscribers7 August 2026 — 23,642 subscribers8 August 2026 — 23,655 subscribers9 August 2026 — 23,664 subscribers10 August 2026 — 23,663 subscribers11 August 2026 — 23,691 subscribers12 August 2026 — 23,681 subscribers13 August 2026 — 23,671 subscribers14 August 2026 — 23,643 subscribers16 August 2026 — 23,649 subscribers17 August 2026 — 23,633 subscribers18 August 2026 — 23,609 subscribers19 August 2026 — 23,616 subscribers20 August 2026 — 23,652 subscribers21 August 2026 — 23,676 subscribers23 August 2026 — 23,682 subscribers25 August 2026 — 23,664 subscribers26 August 2026 — 23,666 subscribers27 August 2026 — 23,676 subscribers28 August 2026 — 23,692 subscribers28 August 2026 — 23,705 subscribers29 August 2026 — 23,696 subscribers30 August 2026 — 23,683 subscribers31 August 2026 — 23,685 subscribers1 September 2026 — 23,714 subscribers2 September 2026 — 23,705 subscribers23,7057 August 20262 September 2026
26 measurements spanning 27 days, net +56. 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 23,593–23,730 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
2 Sept 2026, 23:4323,705-9
1 Sept 2026, 22:1523,714+29
31 Aug 2026, 22:2523,685+2
30 Aug 2026, 21:0523,683-13
29 Aug 2026, 23:3423,696-9
28 Aug 2026, 23:5923,705+13
28 Aug 2026, 01:2723,692+16
27 Aug 2026, 00:1423,676+10
26 Aug 2026, 00:2323,666+2
25 Aug 2026, 01:2423,664-18
23 Aug 2026, 14:3623,682+6
21 Aug 2026, 22:0723,676+24
20 Aug 2026, 18:5823,652+36
19 Aug 2026, 18:1323,616+7
18 Aug 2026, 17:1423,609-24
17 Aug 2026, 14:5823,633-16
16 Aug 2026, 08:2423,649+6
14 Aug 2026, 21:2523,643-28
13 Aug 2026, 14:0823,671-10
12 Aug 2026, 11:2623,681first reading

Engagement

1,142 posts held, back to 6 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 58 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.51%
avg views ÷ 23,705 subscribers
Avg views / post
357
1,142 posts measured
Reaction rate
0.23%
reactions ÷ views · ER floor
Posts in window
1,142
of 1,142 held

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 117 of 1,142 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 September 2026
Posts held1,142 (6 August 20263 September 2026)
Views total407,489
Reactions total118
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 11:04 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.

What this channel posts

Photos
17,200
Links
116,000

Lifetime counters from Telegram’s own channel header, read 3 September 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.

Reaction mix

102 reactions across 72 posts, in 18 distinct kinds. The most used accounts for 25.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2625.5%
👍2019.6%
🎉87.84%
💩87.84%
💯87.84%
👏65.88%
👀54.90%
👎43.92%
🔥43.92%
🤡32.94%
🥰32.94%
👌10.98%
😁10.98%
😢10.98%
😭10.98%
🤔10.98%
🤬10.98%
🤮10.98%

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 101 of the 1,000 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 102 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 8 August 2026 to 3 September 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.

Recent posts

3 Sept 2026, 11:02 UTC27 viewsread 3 September 2026
Photo

天猫上线Token充值中心,首批接入阿里云、智谱、Kimi、MiniMax等国产模型厂商 【天猫上线Token充值中心,首批接入阿里云、智谱、Kimi、MiniMax等国产模型厂商】金色财经报道,9月3日,天猫正式上线AI空间站(Token充值中心),用户可直接购买多家头部大模型订阅产品。页面显示,该充值中心集合了阿里云、智谱、Kimi、MiniMax等国内头部大模型厂商的订阅服务,在售商品包括按周期订阅的TokenPlan、CodingPlan以及按用量付费的充值方案,支持卡密或直充两种交付方式。此前一天,智谱已正式入驻天猫开设官方旗舰店,开售CodingPlan等订阅套餐。据了解,开店首日搜索环比暴涨40倍,大模型订阅服务开始进入电商消费场景。 交流群

3 Sept 2026, 10:58 UTC76 viewsread 3 September 2026

Fomo 昨日单日收入达 120 万美元,创历史新高 【Fomo 昨日单日收入达 120 万美元,创历史新高】金色财经报道,据 SolanaFloor 监测,Fomo 昨日单日收入达到 120 万美元,创历史新高。 交流群

3 Sept 2026, 10:42 UTC171 viewsread 3 September 2026

Circle在Solana链上新增铸造2.5亿枚USDC 【Circle在Solana链上新增铸造2.5亿枚USDC】金色财经报道,9月3日,据WhaleAlert监测,北京时间18时13分,Circle在Solana网络新增铸造2.5亿枚USDC。 交流群

3 Sept 2026, 10:42 UTC173 viewsread 3 September 2026

BTC跌破77500美元 【BTC跌破77500美元】金色财经报道,行情显示,BTC跌破77500美元,现报77496.84美元,24小时涨幅达到1.28%,行情波动较大,请做好风险控制。 交流群

3 Sept 2026, 10:40 UTC171 viewsread 3 September 2026

WTI原油日内涨超2%,现报90.90美元/桶 【WTI原油日内涨超2%,现报90.90美元/桶】金色财经报道,WTI原油日内涨超2%,现报90.90美元/桶。布伦特原油站上96美元/桶,日内涨1.81%。 交流群

3 Sept 2026, 10:36 UTC163 viewsread 3 September 2026

某地址累计买入 400 枚 BTC,持有 3104.6 万美元多单 【某地址累计买入 400 枚 BTC,持有 3104.6 万美元多单】金色财经报道,某地址自今日 05:42 起通过普通成交及三轮 TWAP 累计买入 400 枚 BTC,成交额约 3104.6 万美元。其中,该地址通过普通成交买入 250.65 枚 BTC,成交额约 1949.3 万美元;三轮 TWAP 合计执行 149.35 枚 BTC,成交额约 1155.3 万美元。两轮 TWAP 分别完成 68 枚及 50 枚 BTC 买入,另一轮原计划买入 200 枚 BTC,执行 31.35 枚后提前终止。该地址目前以 20 倍交叉杠杆持有 400 枚 BTC 多单,建仓均价为 7.7614 万美元,浮亏约 1.1 万美元,清算价约 7.2864 万美元。 交流群

3 Sept 2026, 10:34 UTC149 viewsread 3 September 2026

德银:SpaceX新基地规模或达1000亿美元,星舰下一步需要的是扩建工业走廊 【德银:SpaceX新基地规模或达1000亿美元,星舰下一步需要的是扩建工业走廊】金色财经报道,德银指出,路易斯安那新“星基地 ”的核心意义,是为未来大规模部署轨道数据中心和高频星舰发射提前铺路。这类卫星理想轨道接近太阳同步轨道,尤其是沿昼夜分界线运行的昏‑晨轨道,以获得更稳定的太阳能供应。得州博卡奇卡向南发射很快会受到墨西哥方向限制,而路易斯安那海岸拥有更长的向南开放水域走廊,更适合高频发射至这类轨道。 新址初步规划为5组双发射台、共10座发射塔,长期可能超过12座塔、每日发射30次以上。 但发射频率一旦从几十次上升到数百甚至数千次,瓶颈也会从“火箭能不能飞”转向“发射体系能不能持续供给”。按德银测算,仅液氧部分,一次发射就相当于约180辆卡车的运输量,显然无法支撑长期高频运营。因此SpaceX在新基地规划中加入了现场燃料加工、空气分离、管道输送

3 Sept 2026, 10:26 UTC140 viewsread 3 September 2026

普京:外资正涌入俄罗斯 【普京:外资正涌入俄罗斯】金色财经报道,据俄新社:俄罗斯总统普京称,金融当局在决定关键利率时,会考虑到维持宏观经济稳定的需要。没有宏观经济稳定,就谈不上投资。俄罗斯当局与企业保持着密切联系。外国投资正在涌入俄罗斯,并且流入外国企业感兴趣的项目。俄罗斯各银行的收入正在增长;资金充足。在当前主要投资周期成功完成后,俄罗斯经济有必要开启新的投资周期。 交流群

3 Sept 2026, 10:26 UTC163 viewsread 3 September 2026

美、布两油日内均涨超1%,现分别报90.01美元/桶和95.26美元/桶 【美、布两油日内均涨超1%,现分别报90.01美元/桶和95.26美元/桶】金色财经报道,美、布两油日内均涨超1%,现分别报90.01美元/桶和95.26美元/桶。 交流群

3 Sept 2026, 10:26 UTC132 viewsread 3 September 2026

Outcomexyz 24 小时交易量达 322 万美元,创历史新高 【Outcomexyz 24 小时交易量达 322 万美元,创历史新高】金色财经报道,HyperliquidNews 在 X 平台表示,Outcomexyz 24 小时交易量达到 322 万美元,创下历史新高。 交流群

3 Sept 2026, 10:22 UTC143 viewsread 3 September 2026

USDC Treasury 在 Solana 链上新增铸造 2.5 亿枚 USDC 【USDC Treasury 在 Solana 链上新增铸造 2.5 亿枚 USDC】金色财经报道,链上数据显示,(UTC+8)今日 2 时 13 分,USDC Treasury 在 Solana 网络新增铸造 2.5 亿枚 USDC。 交流群

3 Sept 2026, 10:22 UTC139 viewsread 3 September 2026

Mike McGlone:美股波动率处于低位,黄金相对美债表现接近历史高点 【Mike McGlone:美股波动率处于低位,黄金相对美债表现接近历史高点】金色财经报道,9 月 3 日,彭博大宗商品策略师 Mike McGlone 表示,当前美国股市波动率相对黄金处于 2007 年以来最低水平,且 SPDR 黄金 ETF 与 iShares 20 年以上美国国债 ETF 的比率接近历史最高水平。Mike McGlone 指出,极低的股市波动率曾出现在 2008 年金融危机前夕。 交流群

Showing the 12 most recent of 1,142 posts we hold for @jinseBTC. 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.

Forward network

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.

Mentions

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.

Appears in Telegram’s recommendations for other channels

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.

Telo News 简体中文 - 加密货币|DeFi |Web3
@telonews_cn · 84,902
Telegram ranks this channel #1 of 65 here — alongside 64 others — read 18 August 2026
金十数据 闪电资讯
@jin10light · 34,253
Telegram ranks this channel #2 of 78 here — alongside 77 others — read 3 September 2026
金色财经
@jinsecaijinpingdao · 247,003
Telegram ranks this channel #5 of 90 here — alongside 89 others — read 17 August 2026
分叉财经(crypto news)
@fenchacaij · 262,601
Telegram ranks this channel #5 of 83 here — alongside 82 others — read 17 August 2026
Toncoin 中文频道
@toncoin_cn · 142,434
Telegram ranks this channel #9 of 87 here — alongside 86 others — read 17 August 2026
【华尔街见闻】- 财经时讯 | AI 实时互动
@FinanceNewsDaily · 54,612
Telegram ranks this channel #12 of 60 here — alongside 59 others — read 24 August 2026
Btok News
@BtokMedia · 297,150
Telegram ranks this channel #12 of 88 here — alongside 87 others — read 17 August 2026
华尔街日报
@HuaErJie1 · 69,428
Telegram ranks this channel #20 of 80 here — alongside 79 others — read 20 August 2026
币安公告
@binance_cn · 34,468
Telegram ranks this channel #23 of 84 here — alongside 83 others — read 3 September 2026
BlockBeats
@theblockbeats · 37,299
Telegram ranks this channel #23 of 92 here — alongside 91 others — read 1 September 2026
Coindesk
@Coindesk001 · 56,222
Telegram ranks this channel #24 of 57 here — alongside 56 others — read 22 August 2026
互联网观察
@guanchahulw · 69,624
Telegram ranks this channel #24 of 72 here — alongside 71 others — read 20 August 2026
海外素材库
@sucai1 · 106,673
Telegram ranks this channel #27 of 41 here — alongside 40 others — read 14 August 2026
Floki & TokenFi 中文社区入口
@flokiinuchina · 207,174
Telegram ranks this channel #36 of 81 here — alongside 80 others — read 17 August 2026
欧易OKX公告
@OKXAnnouncements_CN · 44,823
Telegram ranks this channel #52 of 88 here — alongside 87 others — read 28 August 2026
舒琴比特币行情资讯(其他均为仿冒)
@bitebishuqin · 40,260
Telegram ranks this channel #67 of 90 here — alongside 89 others — read 30 August 2026
Telo News - Crypto | DeFi | Web3
@telonews · 201,532
Telegram ranks this channel #73 of 77 here — alongside 76 others — read 11 August 2026
動區動趨 BlockTempo⚡️區塊鏈 加密貨幣新聞
@blocktemponews · 39,560
Telegram ranks this channel #74 of 87 here — alongside 86 others — read 30 August 2026

This channel appears in 18 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“金色财经/币圈快讯7*24小时” (@jinseBTC), 23,705 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/jinseBTC.

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.