#美国海军陆新闻 访问者参观丛林作战训练中心,实地观看海军陆战队员在模拟实战地形中运用训练技能,并特别关注负责训练中心管理和教学工作的海军陆战队人员。

Channel
BBC中文频道
@BBDNEW
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
45,871subscribers
+14,257 since we began measuring on 29 September 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001339778409 |
|---|---|
| Type | Channel |
| Username | @BBDNEW |
| Description | 连接世界,洞察时代。 BBC 中文频道 —— 以全球视野,观风云变局;以深度真相,立时代潮头。 跨越国界,穿透表象;权威声音,无处不在。 我们不止记录世界,更定义世界的认知。 小编 @cctvzbj |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 29 September 2026 |
| Last confirmed live | 15 November 2026 |
| Measurements held | 31 |
| Confirmed unchanged | 1 time, most recently 15 November 2026 |
| On Telegram | t.me/BBDNEW |
Topic
International news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 13 October 2026 and assigned it the closest of 31 fixed categories, at 58% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Nov 2026, 21:14 | 45,871 | -1,102 |
| 12 Nov 2026, 11:56 | 46,973 | -830 |
| 10 Nov 2026, 08:56 | 47,803 | -594 |
| 8 Nov 2026, 23:59 | 48,397 | -522 |
| 7 Nov 2026, 14:56 | 48,919 | -488 |
| 6 Nov 2026, 16:56 | 49,407 | -265 |
| 5 Nov 2026, 14:17 | 49,672 | -459 |
| 4 Nov 2026, 13:30 | 50,131 | -547 |
| 3 Nov 2026, 14:46 | 50,678 | -2 |
| 2 Nov 2026, 14:16 | 50,680 | -55 |
| 1 Nov 2026, 15:45 | 50,735 | -166 |
| 31 Oct 2026, 15:19 | 50,901 | -163 |
| 30 Oct 2026, 12:19 | 51,064 | -130 |
| 29 Oct 2026, 13:59 | 51,194 | -163 |
| 28 Oct 2026, 12:40 | 51,357 | -113 |
| 27 Oct 2026, 09:59 | 51,470 | -53 |
| 26 Oct 2026, 10:30 | 51,523 | -92 |
| 25 Oct 2026, 12:57 | 51,615 | -21 |
| 24 Oct 2026, 10:55 | 51,636 | -2 |
| 23 Oct 2026, 07:56 | 51,638 | first reading |
Engagement
690 posts held, back to 29 September 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 100 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.714%
- avg views ÷ 45,871 subscribers
- Avg views / post
- 328
- 460 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 460
- of 690 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.
| Window | Rolling 30 days · latest post in window 18 November 2026 |
|---|---|
| Posts held | 690 (29 September 2026 – 18 November 2026) |
| Views total | 150,747 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Nov 2026, 12:30 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
- ≈4,180
- Videos
- ≈220
- Links
- ≈2
Lifetime counters from Telegram’s own channel header, read 18 November 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.
- Video runtime
- 1h 19m
- Average length
- 56s
Measured directly from 85 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.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 460 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
#美国军事训练新闻 美国空军工程中队与第56部队支援中队开展联合训练,在高海拔松林地区提升人员搜索与救援技能,通过基础交叉训练,增强空军人员在复杂对抗环境下执行关键支援任务的能力。
#北约新闻 有关人士高度评价芬兰为北约联盟作出的贡献,指出芬兰陆军组成司令部建设及F-35战斗机引进进展迅速,其多领域战备能力和行动效率值得北约其他成员国借鉴。
#斯洛伐新闻 在争取自由与民主日之际,向斯洛伐克和捷克盟友致以诚挚祝福,纪念两国争取自由与民主的历史。
#北约军事新闻 北约盟军转型最高司令皮埃尔·旺迪耶海军上将访问位于土耳其伊兹密尔的盟军陆军司令部,与工作人员围绕未来战争形态展开交流,强调加快创新步伐,推动北约整体作战能力发展。
#日本外交新闻 日本首相高市早苗访问菲律宾期间,与澳大利亚总理安东尼·阿尔巴尼斯、印度总理纳伦德拉·莫迪和美国总统唐纳德·特朗普举行美日印澳四方安全对话领导人峰会,就四国合作及地区事务进行交流。
#美国新闻 斯洛伐克国防部长罗伯特·卡利尼亚克及其代表团访问美国阿特伯里营和穆斯卡塔塔克城市训练中心,实地了解印第安纳州国民警卫队针对现代战争开展的全方位军事训练。
#美国军事新闻 加州大学伯克利分校预备役军官训练团学员访问特拉维斯空军基地第821应急响应大队,了解应急部署任务和日常工作,并参加无线电通信及战术战伤救护实操训练,学习快速部署相关能力。
#军事训练新闻 年度射击训练周末活动汇集多名学员,为其提供提升专业知识、自信心和射击技能的机会。学员们学习枪支安全和射击基础知识,并在靶场进行实弹射击,将所学内容应用于实践。
#菲律宾军事新闻 美菲双边训练活动“群岛海岸防御合作)旨在支持菲律宾海军陆战队的群岛海岸防御理念,加强菲律宾与美国军队之间的协同作战能力和联合战备水平。
#军事新闻 赫尔利和菲南以假想敌身份参与演习,通过观察和报告空降行动为训练提供支持。他们的参与营造了模拟对抗环境,帮助参演部队演练应对假想敌的作战行动,并提升适应战场变化的能力。
#日本军事新闻 日本海上自卫队护卫舰“阿武隈”号与加拿大海军号实施海上补给作业,进一步深化两国互信,并通过舰长和船员之间的交流巩固友好关系。双方表示将珍惜与海上伙伴的联系,继续全力执行各项任务。
Showing the 12 most recent of 690 posts we hold for @BBDNEW. 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 0
- vacant every time we have ever looked
@BBDNEW named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 2 posts, 22 October 2026 – 6 November 2026 · confirmed gone 27 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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 November 2026 — this entry's latest reading, not the date you are reading this.
“BBC中文频道” (@BBDNEW), 45,871 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/BBDNEW.
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.