涨停雷达:油气开采+伊拉克项目+ST摘帽预期 ST洲际 08月11日 15:01 今日走势:ST洲际今日触及涨停板,该股近一年涨停30次。 异动原因揭秘:行业原因:据财闻,8月11日,特朗普公开批评伊朗在谈判中提出的战争赔偿要求,令市场此前对快速达成协议、重开战略水 ...

Channel
股市涨停异动解析 A股票
@yidongjiexi
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
2,969subscribers
-76 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001480420635 |
|---|---|
| Type | Channel |
| Username | @yidongjiexi |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/yidongjiexi |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 19:17 | 2,969 | -11 |
| 12 Sept 2026, 04:01 | 2,980 | -19 |
| 7 Sept 2026, 18:17 | 2,999 | -16 |
| 2 Sept 2026, 16:39 | 3,015 | -5 |
| 30 Aug 2026, 15:34 | 3,020 | -5 |
| 24 Aug 2026, 09:05 | 3,025 | -9 |
| 20 Aug 2026, 20:46 | 3,034 | -3 |
| 18 Aug 2026, 07:22 | 3,037 | -8 |
| 12 Aug 2026, 00:42 | 3,045 | no change |
| 11 Aug 2026, 19:01 | 3,045 | first reading |
Engagement
20 posts held, back to 11 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 20 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
涨停雷达:液冷服务器+智慧灯杆+照明工程 豪尔赛 08月11日 15:01 今日走势:豪尔赛今日触及涨停板,该股近一年涨停10次。 异动原因揭秘:1、据2025年2月24日互动易,公司参股的华奕新能源已中标某头部通讯公司的数据中心冷板试点项目,其基于蒸发冷却独有冷 ...
涨停雷达:参股算力建设(金额较小)+工程咨询+AI应用+甘肃国资 甘咨询 08月11日 14:51 今日走势:甘咨询今日触及涨停板,该股近一年涨停3次。 异动原因揭秘:1、据2024年12月30日互动易,2023年8月20日,公司参股公司丝绸之路信息港股份有限公司参与建设的全国一体化算力网络枢 ...
涨停雷达:工程咨询+国企改革+AI应用 甘咨询 08月11日 14:51 今日走势:甘咨询今日触及涨停板,该股近一年涨停3次。 异动原因揭秘:1、据2026年8月11日异常波动公告,公司目前经营情况正常,内外部经营环境未发生重大变化;公司、控股股东及实际控制人 ...
涨停雷达:橡胶密封件+新能源汽车+年报增长 朗博科技 08月11日 14:51 今日走势:朗博科技今日触及涨停板,该股近一年涨停8次。 异动原因揭秘:1、据2026年4月28日年报,公司2025年实现营业收入2.70亿元,同比增长16.71%;归母净利润4524.61万元,同比增长62.04% ...
涨停雷达:机器人概念+电磁线+年报增长 长城科技 08月11日 14:21 今日走势:长城科技今日触及涨停板,该股近一年涨停10次。 异动原因揭秘:1、据2025年8月26日互动易,公司电磁线产品已应用于包括机器人应用领域在内的低压线圈产品;据2026年4月22日年报, ...
涨停雷达:母婴用品+摘帽+中报预计扭亏 金发拉比 08月11日 14:11 今日走势:金发拉比今日触及涨停板,该股近一年涨停14次。 异动原因揭秘:1、据2026年6月18日公告,公司股票自2026年6月22日起撤销退市风险警示,证券简称由“*ST金比”变更为“金发拉比”。 ...
涨停雷达:光刻胶+战略入股+PEEK材料+有机颜料 百合花 08月11日 14:01 今日走势:百合花今日触及涨停板,该股近一年涨停21次。 异动原因揭秘:1、据2026年8月3日互动易,公司已完成对清荷科技的战略入股,双方产业链深度耦合,合力打通“颜料—色浆—光刻胶”国 ...
涨停雷达:机器人+汽车饰件+全球化布局 新泉股份 08月11日 13:51 今日走势:新泉股份今日触及涨停板,该股近一年涨停9次。 异动原因揭秘:1、据2026年半年度报告,公司子公司新泉机器人引入战略投资者凯迪股份,聚焦智能机器人核心零部件业务。据2026年3月2 ...
涨停雷达:机器人+汽车内饰件+定增获批 福赛科技 08月11日 13:41 今日走势:福赛科技今日触及涨停板,该股近一年涨停3次。 异动原因揭秘:1、据2026年4月3日业绩说明会,公司已完成部分机器人零部件产品研发、小批量试制及送样实验工作;据2026年6月29日募 ...
涨停雷达:黄金开采+矿山装备+高端装备 南矿集团 08月11日 13:31 今日走势:南矿集团今日触及涨停板,该股近一年涨停11次。 异动原因揭秘:1、据公司2025年7月26日公告及2025年年报,公司境外子公司与SucpassGold签订合作协议,负责津巴布韦Brownhill金矿地 ...
涨停雷达:机器人+谐波减速器+汽车轮毂轴承 斯菱智驱 08月11日 13:31 今日走势:斯菱智驱今日触及涨停板,该股近一年涨停1次。 异动原因揭秘:1、据2025年年度报告,公司已实现谐波减速器和减速器专用轴承的投产工作,产品适用于工业机器人、协作机器人、人形机 ...
Showing the 12 most recent of 20 posts we hold for @yidongjiexi. 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.
Mentions
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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“股市涨停异动解析 A股票” (@yidongjiexi), 2,969 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/yidongjiexi.
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.