Channel
@hejrb233
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
10,061subscribers
+26 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001635306108 |
|---|---|
| Type | Channel |
| Username | @hejrb233 |
| Description | 华尔街日报（The Wall Street Journal）创刊于1889年，以超过200万份的发行量成为美国付费发行量最大的财经报纸。这份在美国纽约出版的报纸，着重在财经新闻的报道，其内容足以影响每日的国际经济活动。 本频道提供华尔街日报免费全文阅读，更新及时，长期维护。 |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/hejrb233 |
International news — 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 81% 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.
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 word for word on 1 other registered channel. 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 |
|---|---|---|---|
| @HuaErJie1/140176 Aug 2026, 10:27 UTC | @hejrb233/25199 · this entry6 Aug 2026, 10:39 UTC | 1.00 | 12 minutes |
| @HuaErJie1/140186 Aug 2026, 10:45 UTC | @hejrb233/25200 · this entry6 Aug 2026, 10:49 UTC | 1.00 | 5 minutes |
| @HuaErJie1/140216 Aug 2026, 14:37 UTC | @hejrb233/25203 · this entry6 Aug 2026, 14:50 UTC | 1.00 | 13 minutes |
| @HuaErJie1/140236 Aug 2026, 23:46 UTC | @hejrb233/25205 · this entry6 Aug 2026, 23:49 UTC | 1.00 | 3 minutes |
| @HuaErJie1/140307 Aug 2026, 08:59 UTC | @hejrb233/25213 · this entry7 Aug 2026, 09:09 UTC | 1.00 | 10 minutes |
| @HuaErJie1/140327 Aug 2026, 09:38 UTC | @hejrb233/25215 · this entry7 Aug 2026, 09:49 UTC | 1.00 | 11 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @HuaErJie1 | 19 (8/8 hand-verifiable sample passed) | 1.00 | 9 minutes | @HuaErJie1 (19–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. 19 of the 19 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 21 comparable posts for this entry, running 6 August 2026 to 7 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.
Across the whole group of 2, the earliest publisher we hold is @HuaErJie1. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 7 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.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 05:07 | 10,061 | +12 |
| 11 Aug 2026, 04:21 | 10,049 | -2 |
| 10 Aug 2026, 02:41 | 10,051 | +7 |
| 9 Aug 2026, 00:51 | 10,044 | +11 |
| 8 Aug 2026, 01:22 | 10,033 | -2 |
| 7 Aug 2026, 11:00 | 10,035 | no change |
| 7 Aug 2026, 10:59 | 10,035 | first reading |
107 posts held, back to 6 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 15 pagesof 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 12 August 2026 |
|---|---|
| Posts held | 107 (6 August 2026 – 12 August 2026) |
| Views total | 18,282 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 14:29 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 12 August 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.
俄国防部：俄军夜间在敖德萨港击中向乌军提供燃料的油库 据俄罗斯国防部消息，俄军夜间在敖德萨港击中向乌军部队提供燃料的燃滑油料库。 俄国防部表示，俄军继续对服务于乌军的乌克兰港口基础设施及海船实施打击。 消息显示：“夜间，俄军使用空基高精武器和远程攻击无人机在敖德萨港击中了向乌军部队提供燃料的燃滑油料库。” 此前，据俄国防部消息，自特别军事行动开始以来，俄军共摧毁673架飞机、284架直升机、203025架无人机、669套防空导弹系统、30520辆坦克及其他装甲战车、1769辆多管火箭炮系统战车、36110门野战炮和迫击炮、68889辆特种军用车辆。
Telegram必备的搜索引擎，极搜JISOU帮你精准找到，想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_408985724
俄“北部”集群本月已摧毁超40个乌军无人机控制点和发射点 俄罗斯 “北部”集群第11军无人机规划与对抗主任向卫星通讯社表示，自八月初以来，“北部”集团军人已摧毁哈尔科夫州40多个乌军无人机控制点和发射点。 该军官说：“自八月初以来，‘北部’集群第11军无人系统和炮兵分队已摧毁哈尔科夫州40多个敌方无人机控制点和发射点。” 据他称，在空中侦察过程中，操作手发现阵地、通信和控制天线，以及乌军无人机班组信号放大器。坐标传送至指挥所，随后分发给攻击无人机班组。 他说，目标被FPV无人机操作手和装备杀伤爆破和温压弹药的“闪电-2”固定翼无人机精确打击。 该军官补充道：“摧毁敌方无人机控制点可降低乌军无人机在战斗接触线特定区域的活动强度，从而让突击分队在无人系统班组的掩护下向前推进。”
香港特区政府医务卫生局局长卢宠茂将访海南深化医疗卫生交流合作 香港特区政府医务卫生局局长卢宠茂今日（12日）率领代表团前往海南省进行为期3天的访问，与当地医疗卫生官员会面，以持续深化香港与内地在医疗卫生方面的交流和合作，并会参观海南博鳌乐城国际医疗旅游先行区和当地医药企业，了解当地医疗服务和药业的最新发展。
俄罗斯工业通讯银行计划占据全球稳定币市场10%的份额 俄罗斯工业通讯银行董事长彼得·弗拉德科夫在接受俄罗斯媒体采访时表示，开发同名跨境结算系统的俄罗斯公司A7，将占据全球稳定币市场10%的份额作为其目标。 据弗拉德科夫介绍，公司的任务是打造一款有竞争力的产品，不仅满足俄罗斯自身需求，也用于第三国之间的结算。 弗拉德科夫在回答公司希望在稳定币细分市场占据多大份额的问题时表示：“我认为，10%的市场份额是充分的。如果设定这样雄心勃勃的的目标，那么就不仅仅指的是俄罗斯的贸易，而是在国际贸易中使用该结算机制。” 工业通讯银行董事长介绍，A7公司发行的稳定币A7A5市值约5.7亿美元，已是全球最大的非美元稳定币。该公司有意识地发展自身基础设施，与锚定美元且由发行方控制的USDT不同，俄方方案采用去中心化的结算中心网络，由合作伙伴机构和法律架构组成，在各国的当地法律框架内运作。系统运作原理基于分布式流动性管理，不存在传统的跨境支付，从而能…
韩国东南部干旱严重 政府发布国家消防动员令 由于韩国东南部地区今夏迎来罕见的持续高温干燥天气，庆尚南道各地农业水库近日开始干涸，干旱形势日益严重。韩国政府为此发布了国家消防动员令，自12日起向干旱严重的庆尚南道提供200辆水罐车和400名消防人员，进行供水支援工作。据统计，截至12日，庆尚南道共有2121公顷农田遭受旱灾；截至当天，在庆尚南道的18个市、郡中，密阳市、巨济市和咸安郡的农业用水处于“农业用水干旱警戒”中最严重的“严重干旱”阶段。其中，干旱最严重的密阳市农业用水蓄水率当天为25.7%，仅为常年标准的三分之一左右；而庆尚南道的平均蓄水率仅为33.3%，与常年相比下降了近一半。
苏州：新就业群体台风中受伤最高可获10000元救助 据“苏州发布”，近日，受台风“白海豚”影响，户外劳动者作业风险攀升，部分新就业群体在工作过程中不慎发生摔伤、骨折等意外事故。苏州市依托“新就业群体困难对象急难救助”基金，专门针对本次台风灾害开通专项救助通道，覆盖快递员、网约配送员、货车司机、网约车司机等新就业群体，申请对象为在“白海豚”台风期间在岗上线接单的新就业群体。从业者在工作时间内因台风原因受伤或家庭经济困难的，每户可一次性获5000-10000元救助金。
也门胡塞武装称愿与沙特对话 当地时间8月11日，也门胡塞武装发表声明称，愿与沙特保持对话，但同时称，除非有关要求得到满足，否则将继续对沙特相关船只以及沙特支持的军事目标发动袭击。声明说，胡塞武装近期对沙特相关船只以及也门境内由沙特支持的武装力量发动袭击，是对胡塞武装控制地区遭袭的回应。声明还指责沙特加强对胡塞武装控制地区的经济施压。目前，沙特方面尚未就胡塞武装上述言论作出回应。
美媒：利雅得劝阻美国对伊朗发动攻击因担心无法抵御反击 《纽约时报》援引一位沙特阿拉伯官员的话报道称，沙特在8月初呼吁美国不要实施原计划对伊朗的袭击，因其担心美军无法保护该地区各国免受伊朗的报复性打击。 美国总统唐纳德·特朗普8月初表示，美国已取消原定于本周末对伊朗发动的攻击——部分原因是应德黑兰方面的请求，但美国随时准备重启空袭。他补充指出，沙特阿拉伯、阿联酋和卡塔尔也曾请求他取消这次行动。 据该报报道，沙特阿拉伯王储穆罕默德·本·萨勒曼向美国领导人表示，美国的侵略行为可能会导致伊朗对邻国境内的目标发动报复性打击。 该报指出：“鉴于美国拦截机数量不足，且伊朗已展示出其有能力突破这一防空系统，遭受严重损失的威胁是完全真实的……沙特王储呼吁特朗普缓和局势。” 在特朗普宣布6月18日与德黑兰达成的停火协议不再有效后，该地区的紧张局势进一步升级。随后，美军对伊朗境内的目标发动了一系列打击。美国中央司令部解释称，此次袭击是对针对穿越霍尔…
中国对日稀土出口上半年骤降51%，镝铽出口量归零 据《日经新闻》援引中国海关总署数据报道，今年上半年，中国对日本出口的七类受管制稀土同比大幅减少51%，其中电动汽车电机所需的关键金属镝和铽的出口量已降至零。同期，中国对全球稀土出口整体降幅为16%。 单月数据更为显著。6月，中国对日受管制稀土出口量较去年同期锐减81%，已连续四个月呈下滑态势。此外，应用于飞机引擎涂层、半导体制造及癌症治疗设备等领域的高科技材料钇，其6月对日出口亦跌至零。 此次出口骤降正值中日关系趋紧之际。今年1月，中国强化了对日本的两用物项出口管制，涵盖上述七类稀土及稀有金属。消息人士透露，中方仍会视情况向部分日企发放出口许可，意在既避免日企完全脱离中国供应链，也通过商界向日本政府传递重视双边关系的信号。 近期，涉及稀土相关案件的司法行动亦引发关注。今年5月，两名日本富士电机集团员工因涉嫌违规出口内置稀土磁体的马达等产品被中国拘留，其后被捕。知情人士称，包括日…
俄常驻联合国代表：将加沙和平计划破裂的责任全部推给哈马斯是不可接受的 俄罗斯常驻联合国代表瓦西里•涅边贾表示，不应把加沙地带和平计划陷入停滞的全部责任仅归咎于巴勒斯坦伊斯兰抵抗运动（哈马斯），并指出以色列方面系统性地违反了停火协议。 涅边贾在联合国安理会会议上指出：“在安理会的会议上，一些西方代表团把加沙和平计划停滞不前的全部责任完全归咎于哈马斯。我们都记得当时呼吁该组织领导人放下武器，接受‘和平理事会’总干事尼古拉·姆拉德诺夫提出的路线图。希望我们的西方同事在对待冲突的另一方（以色列）时，也能展现出同样的团结和决心。” 这位外交官同时指出，美国的加沙和平计划实际上已经陷入僵局，而以色列方面则有条不紊地违反停火协议。他表示，在正式停火期间，加沙地带有近1300名巴勒斯坦人死亡，其中约300名是儿童。 以色列总理本杰明·内塔尼亚胡周日表示，以色列拒绝了“和平理事会”关于加沙地带的15点计划，在哈马斯组织完全解除武装前军队不会撤出…
世界气象组织：今年全球7月气温为有记录以来第二高 世界气象组织发言人克莱尔·纳利斯表示，西欧今年6月至7月经历有记录以来最热时期，全球7月气温为有记录以来第二高，全球海洋表面平均温度则创同期最高纪录。世界气象组织统计显示，日本和韩国上周均出现破纪录高温，亚洲其他地区和拉丁美洲部分地区也遭遇高温，西非部分地区出现强季风降雨和洪水。今年1月至6月底，全球约82%的海洋经历不同程度的海洋热浪。
Showing the 12 most recent of 107 posts we hold for @hejrb233. 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.
Citation-graph rank — 1,037,423 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“华尔街日报 股票财经新闻” (@hejrb233), 10,061 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/hejrb233.
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.