Channel
@jinse2017
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
22,598subscribers
-554 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001748596288 |
|---|---|
| Type | Channel |
| Username | @jinse2017 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 23 October 2026 |
| Measurements held | 47 |
| Confirmed unchanged | 1 time, most recently 23 October 2026 |
| On Telegram | t.me/jinse2017 |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 64% 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 |
|---|---|---|
| 23 Oct 2026, 11:46 | 22,598 | -8 |
| 22 Oct 2026, 10:56 | 22,606 | -7 |
| 21 Oct 2026, 01:40 | 22,613 | -9 |
| 20 Oct 2026, 00:18 | 22,622 | -13 |
| 18 Oct 2026, 21:04 | 22,635 | +15 |
| 17 Oct 2026, 21:26 | 22,620 | -2 |
| 16 Oct 2026, 22:38 | 22,622 | -8 |
| 15 Oct 2026, 20:18 | 22,630 | -13 |
| 14 Oct 2026, 21:17 | 22,643 | +24 |
| 13 Oct 2026, 16:40 | 22,619 | -45 |
| 9 Oct 2026, 23:14 | 22,664 | +14 |
| 5 Oct 2026, 14:37 | 22,650 | -38 |
| 29 Sept 2026, 21:36 | 22,688 | -96 |
| 18 Sept 2026, 03:15 | 22,784 | -5 |
| 15 Sept 2026, 20:55 | 22,789 | +9 |
| 14 Sept 2026, 04:56 | 22,780 | -27 |
| 12 Sept 2026, 12:41 | 22,807 | -3 |
| 10 Sept 2026, 08:41 | 22,810 | +18 |
| 7 Sept 2026, 03:02 | 22,792 | -21 |
| 4 Sept 2026, 11:36 | 22,813 | first reading |
847 posts held, back to 5 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 86 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 21 October 2026 |
|---|---|
| Posts held | 847 (5 August 2026 – 21 October 2026) |
| Views total | 249,554 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 21 Oct 2026, 08:11 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.
【快讯】SK海力士完成40万亿韩元股票回购 【SK海力士完成40万亿韩元股票回购】金色财经报道，10月21日，据韩联社，继三星电子之后，SK海力士的大规模股票回购也于21日结束。SK海力士表示，公司当天在韩国证券交易所（KOSPI）完成了历时两个月、规模达40万亿韩元的股票回购。此前，SK海力士宣布，将投入40.0434万亿韩元回购2407万股公司股票，并在回购完成后将全部股份注销。此次回购股份约占公司已发行股份总数的3.3%，是韩国上市公司规模最大的股票注销操作。SK海力士原先公告的回购期限为8月20日至11月19日，但实际回购工作提前约一个月完成。 原文链接：https://www.jinse.com.cn/lives/537120.html
Signed 金色财经JinSeFinance
【快讯】BTC突破83000美元 【BTC突破83000美元】金色财经报道，行情显示，BTC突破83000美元，现报83116.53美元，24小时涨幅达到1.81%，行情波动较大，请做好风险控制。 原文链接：https://www.jinse.com.cn/lives/537116.html
Signed 金色财经JinSeFinance
较低点最高上涨3倍 9年老币BAT新路线图是个好交易吗 Brave 拥有 1.28 亿用户，在 AI 支付叙事中处于极其有利的位置。但BAT 是一个押注代币经济文章发布的交易，而不是对 Brave 的可靠敞口。 原文链接：https://www.jinse.com.cn/blockchain/3739970.html
Signed 金色财经JinSeFinance
【快讯】三星晶圆代工：4纳米产能拉满 5纳米接力拓客 2nm谈判进度滞后 【三星晶圆代工：4纳米产能拉满 5纳米接力拓客 2nm谈判进度滞后】金色财经报道，10月21日，据ChosunBiz，三星4纳米和5纳米工艺的良率相对稳定。由于近期客户订单激增，三星电子晶圆代工业务部门的4纳米工艺产能已接近饱和，公司正加大销售力度，力求为其5纳米工艺争取更多客户。据悉，5纳米工艺还能提高现有生产设施的利用率。业内人士预计，4纳米工艺利用率的提高和新的5纳米订单将有助于三星晶圆厂近期业绩的提升。相比之下，三星在下一代旗舰级2纳米工艺上争取重要客户仍面临挑战。三星电子正在与全球大型科技公司洽谈基于2纳米工艺的半导体生产合同，但部分谈判进度有所滞后。由于尖端工艺不仅需要对良率进行验证，还需要对能效、知识产权以及稳定的量产能力进行全面验证，从签订合同到实现量产需要相当长的时间。 原文链接：https://www.jinse.com.cn/li…
Signed 金色财经JinSeFinance
【快讯】英国政府债务首次突破3万亿英镑 【英国政府债务首次突破3万亿英镑】金色财经报道，10月21日，英国本财年前六个月的政府借款规模高于预期，凸显财政大臣希利在下周首次公布预算案前面临的种种限制。今年4月至9月，英国财政赤字扩大至978亿英镑（约合1300亿美元），比英国预算责任办公室（OBR）今年3月的预测高出60亿英镑。9月，英国政府借款额达到245亿英镑，不仅高于预算责任办公室的预测，也超过去年同期的水平。这组数据是英国政府在10月28日公布预算案前，公共财政状况的最新情况。届时，希利必须为首相伯纳姆领导的新一届政府制定施政方向，同时避免引发债券市场恐慌，因为市场正担忧英国政府债务规模过高。英国政府债务总额首次突破3万亿英镑。尽管英国经济展现出较强韧性，能够抵御中东冲突引发的能源冲击，而且税收收入超过预算责任办公室的预测，但在2025至2026财年迄今，政府借款规模仍超出预期。 原文链接：https://www.ji…
Signed 金色财经JinSeFinance
永续合约改变一切：“要区块链不要BTC”也有道理？ 永续合约的基本结构可以用于从股票到石油再到欧元和日元的任何东西。 原文链接：https://www.jinse.com.cn/blockchain/3739963.html
Signed 金色财经JinSeFinance
投机仍是这个十年的主线：值得押注的标的该是什么 不要直接押注投机标的，而是通过承接这些交易的交易场所。 原文链接：https://www.jinse.com.cn/blockchain/3739955.html
Signed 金色财经JinSeFinance
【快讯】英伟达宣布投资四家德国初创企业，涉机器人、医疗与卫星 【英伟达宣布投资四家德国初创企业，涉机器人、医疗与卫星】金色财经报道，10月21日，据Sifted报道，英伟达宣布计划投资四家德国初创企业，为其总额近100亿美元的欧洲投资计划的一部分，该计划面向欧洲各地的企业、高校与科研机构。四家企业分别为：研发面向制造、物流与医疗场景AI机器人的Agile Robots，开发AI医院管理软件的Avelios Medical，研发视频与音频生成AI模型的Mirelo，以及设计与制造卫星的Reflex Aerospace。英伟达未披露本次计划投资的具体金额。该消息于周一在柏林举行的德国投资峰会上宣布。同日，德国政府与英伟达签署联合意向声明，共同推进面向工业场景的AI模型研发，英伟达还将扩大与德国联邦政府及工业4.0平台的合作。英伟达CEO黄仁勋称，德国在制造、数学与科研方面积淀深厚，AI只会增强而非取代德国的工业能力。此前一周，黄仁…
Signed 金色财经JinSeFinance
【快讯】英伟达洽谈投资Firmus数亿美元，押注Neocloud 【英伟达洽谈投资Firmus数亿美元，押注Neocloud】金色财经报道，10月21日，据The Information报道，英伟达（NVDA.O）正与澳大利亚AI云服务提供商Firmus洽谈投资事宜，金额可能达数亿美元。Firmus本月初曾突然撤回IPO计划。报道称，此次洽谈表明英伟达可能继续支持一批尚未经充分市场验证的云计算企业，即所谓Neocloud（新型AI云服务商）。这类企业此前大量举债购买英伟达GPU并部署于数据中心，如今正面临日益加大的财务压力。The Information分析称，英伟达已为这类企业及其他大型客户投入超1700亿美元资金承诺，其中包括为客户提供信用担保以帮助其获得债务融资。 原文链接：https://www.jinse.com.cn/lives/537029.html
Signed 金色财经JinSeFinance
【快讯】前OpenAI高管创Arda融资2.3亿美元，估值15亿美元 【前OpenAI高管创Arda融资2.3亿美元，估值15亿美元】金色财经报道，10月20日，据CNBC报道，前OpenAI高管Bob McGrew已低调创立AI制造软件初创公司Arda，并为其完成2.3亿美元融资，公司估值15亿美元。该轮由Altimeter Capital领投，Accel与Khosla Ventures参投，Altimeter的Apoorv Agrawal主导此轮交易。Arda为制造业打造AI助手，其模型已与军工科技公司Anduril合作部署。McGrew称，该产品是面向制造工程师的用户界面与智能体，作用如同Claude或Cursor对程序员。他曾在Palantir任产品与工程负责人十余年，亦曾任职于PayPal。公司称软件混合使用自研专有模型、开源模型及部分前沿模型，机器人为其下一步路线图。投资方称全球制造业规模约16万亿美元，美国约3万…
Signed 金色财经JinSeFinance
【快讯】Citrini测试Claude Science后看好生命科学股 【Citrini测试Claude Science后看好生命科学股】金色财经报道，10月21日，据Bloomberg Technology 消息，独立投资研究机构 Citrini Research 在测试 Anthropic 的 Claude Science 工具后表示，生命科学公司有望受益于 AI 推动的药物发现热潮。该机构将 Charles River Laboratories International 与 Revvity 列为首选生命科学标的。 Citrini 此次判断源于其使用该 Anthropic 工具创建了一个新药候选物，过程显示 AI 可缩短研究时间，并刺激对实验验证的需求。 该观点来自 Citrini 研究结论，为其看好标的而非确定性判断，不构成投资建议。 原文链接：https://www.jinse.com.cn/lives/53703…
Signed 金色财经JinSeFinance
【快讯】美联储10月维持利率不变的概率为83.9% 【美联储10月维持利率不变的概率为83.9%】金色财经报道，10月21日，据CME“美联储观察”：美联储到10月维持利率不变的概率为83.9%，累计加息25个基点的概率为16.1%。美联储到12月维持利率不变的概率为9.8%，累计加息25个基点的概率76.1%，累计加息50个基点的概率为14.2%。 原文链接：https://www.jinse.com.cn/lives/537011.html
Signed 金色财经JinSeFinance
Showing the 12 most recent of 847 posts we hold for @jinse2017. 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.
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.
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.
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 20 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 37 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 23 October 2026 — this entry's latest reading, not the date you are reading this.
“金色财经新闻频道” (@jinse2017), 22,598 subscribers as measured 23 October 2026. Telegram Register, tgregister.com/channel/jinse2017.
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.