‼️🇷🇺🇺🇦俄军对敌方港口基础设施发动了新一轮打击:敖德萨和尼古拉耶夫的设施遭到袭击,—— 俄罗斯国防部 ▪️此次打击使用了高精度空射武器和无人机。 ▪️在敖德萨港,储存用于供应乌克兰武装部队的燃料的储罐遭到袭击。 ▪️在尼古拉耶夫港,一艘经过改装用于搭载无人船的海上拖船遭到袭击。 https://t.me/JShangrong
👍19

Channel
@JShangrong
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
24,860subscribers
-613 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001704547736 |
|---|---|
| Type | Channel |
| Username | @JShangrong |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/JShangrong |
International news — 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 75% 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 |
|---|---|---|
| 19 Sept 2026, 06:00 | 24,860 | -47 |
| 16 Sept 2026, 22:17 | 24,907 | -24 |
| 14 Sept 2026, 23:57 | 24,931 | -19 |
| 13 Sept 2026, 11:18 | 24,950 | -53 |
| 11 Sept 2026, 15:22 | 25,003 | -55 |
| 8 Sept 2026, 22:16 | 25,058 | -48 |
| 5 Sept 2026, 17:19 | 25,106 | -27 |
| 3 Sept 2026, 16:20 | 25,133 | -18 |
| 2 Sept 2026, 06:58 | 25,151 | -21 |
| 1 Sept 2026, 05:36 | 25,172 | -13 |
| 31 Aug 2026, 08:07 | 25,185 | -21 |
| 30 Aug 2026, 06:49 | 25,206 | -13 |
| 29 Aug 2026, 06:13 | 25,219 | -24 |
| 28 Aug 2026, 05:28 | 25,243 | -17 |
| 27 Aug 2026, 04:25 | 25,260 | -11 |
| 26 Aug 2026, 04:54 | 25,271 | +1 |
| 25 Aug 2026, 06:03 | 25,270 | -16 |
| 24 Aug 2026, 08:24 | 25,286 | -16 |
| 22 Aug 2026, 17:24 | 25,302 | -18 |
| 21 Aug 2026, 08:18 | 25,320 | first reading |
7 posts held, back to 1 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 58 pages 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 7 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 videos 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.
58 reactions across 7 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 58 | 100.0% |
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 7 of the 7 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 58 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 1 August 2026 to 1 August 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.
‼️🇷🇺🇺🇦俄军对敌方港口基础设施发动了新一轮打击:敖德萨和尼古拉耶夫的设施遭到袭击,—— 俄罗斯国防部 ▪️此次打击使用了高精度空射武器和无人机。 ▪️在敖德萨港,储存用于供应乌克兰武装部队的燃料的储罐遭到袭击。 ▪️在尼古拉耶夫港,一艘经过改装用于搭载无人船的海上拖船遭到袭击。 https://t.me/JShangrong
👍19
‼️🇷🇺🇺🇦 俄罗斯军队解放了扎波罗热地区的柳比茨科耶,—— 俄罗斯国防部 ▪️额“东方”部队集群在航空和无人机部队的支持下,突破了乌克兰军队的防御,并将敌方从该村庄驱逐。 ▪️在战斗中,俄罗斯士兵占领了面积超过12平方公里的防御区域,并清理了500多座建筑物。 ▪️乌克方面损失了约一个排的士兵,26辆装甲车辆,17辆汽车,23辆摩托车,13套地面机器人系统,以及超过60架“巴巴-亚加”重型无人机。 https://t.me/JShangrong
👍9
‼️🇷🇺🇺🇦俄罗斯军队解放了哈尔科夫州奥尔霍夫卡,——俄罗斯国防部 ▪️俄“西部”部队的士兵将敌方从该城镇驱逐出去,并为进一步推进创造了桥头堡。 https://t.me/JShangrong
👍7
‼️🇷🇺🇺🇦 昨夜,基辅州的的多处军事工业部门目标遭到袭击,—— 俄罗斯国防部 ▪️使用了高精度制导的陆地和海上武器,以及攻击型无人机。 ▪️在基辅,袭击目标是“Радиоизмеритель”公司,该公司与导弹武器的电子元件以及无人机导航系统的生产有关。 ▪️此外,基辅的“Буревестник”工厂也遭到袭击,该工厂生产无人机的电子元件和雷达设备。 ▪️此外,名为“Fire Point”和“ПВ ГРУПП Украина”的设施也遭到袭击,这些设施生产导弹武器的部件以及电子对抗设备。 ▪️袭击还针对无人机的组装和储存地点,该地点生产无人机的各个部件和组件。 ▪️在基辅地区,位于维什涅沃姆的物流中心遭到袭击,该中心用于储存、组装和分发无人机的部件和战斗部分。 ▪️此外,在前一天,在奥德萨以南,两艘货船遭到袭击,这些货船正在向乌克兰的一个港口运送军事物资。 https://t.me/JShangrong
👍5
‼️🇺🇦🔥 基辅因夜间袭击和火灾而笼罩在浓烟之中。 ▪️当地居民表示,城市内的空气质量非常差,难以呼吸。 https://t.me/JShangrong
👍6
‼️🇺🇦🔥基辅附近,工业设施遭到袭击并起火 一枚火箭弹袭击了布查地区的工业设施。 https://t.me/JShangrong
👍6
‼️🇺🇦🏴☠️ 在基辅,一枚导弹袭击后形成了一个令人印象深刻的陨石坑。 https://t.me/JShangrong
👍6
Showing the 7 most recent of 7 posts we hold for @JShangrong. 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 3 registered channels — 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 3 seed channels' Telegram-generated recommendation lists in total. 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“俄罗斯资讯参考频道” (@JShangrong), 24,860 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/JShangrong.
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.