Telegram RegisterThe public register of Telegram
Telegram profile photo for 博度-新闻大事件

Channel

博度-新闻大事件

@bodu3603

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

57subscribers

-3 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001822872894
TypeChannel
Username@bodu3603
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live11 November 2026
Measurements held5
Confirmed unchanged5 times, most recently 11 November 2026
On Telegramt.me/bodu3603

Topic

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 29 September 2026 and assigned it the closest of 31 fixed categories, at 51% 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

576058.57 August 2026 — 60 subscribers10 August 2026 — 60 subscribers14 August 2026 — 59 subscribers26 September 2026 — 58 subscribers14 October 2026 — 57 subscribers7 August 202614 October 2026
5 measurements spanning 68 days, net -3. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 57–60 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Oct 2026, 09:4857-1
26 Sept 2026, 12:5858-1
14 Aug 2026, 18:0459-1
10 Aug 2026, 05:0160no change
7 Aug 2026, 09:3960first reading

Engagement

9 posts held, back to 12 December 2023 — 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 9 posts for this entry, the most recent from 5 January 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
5s
Average length
5s

Measured directly from 1 video 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.

Reaction mix

2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤150.0%
👎150.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 3 of the 9 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 9 most recent posts we hold, published 12 December 2023 to 5 January 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

5 Jan 2024, 02:06 UTC341 views1 reactionsread 10 August 2026
Photo

🔆 #博度东南亚早报(2023年12月29日)周五 【缅甸】再次提醒在老街地区中国公民尽快转移撤离 https://www.bodu365.co/a/154431.html 【缅甸】国管委主席会见泰国皇家军队代表团 https://www.bodu365.co/a/154433.html 【柬埔寨】今年金边机场起降航班近9000架次、累计旅客150万! https://www.bodu365.co/a/154426.html 【柬埔寨】外国豪华邮轮时隔三年再次停靠西港,柬旅游部长有话要说! https://www.bodu365.co/a/154425.html 【菲律宾】近20年,他“无偿”帮许多菲律宾华裔在中国“寻亲”,最多来自福建泉州..... https://www.bodu365.co/a/154446.html 【菲律宾】菲律宾最美铁路线停运六年后再次开通 https://www.bodu36…

❤1

18 Dec 2023, 05:14 UTC559 views0 reactionsread 10 August 2026
File

《劝返通告》指出,非法滞留境外人员回国后自动投案,并如实供述自己违法犯罪行为的,是自首。 自2023年11月20日起至2023年12月30日前自首的,依法从轻或减轻处罚;情节较轻的,依法免除处罚。 准备回国自首的,应在回国前3日内向户籍所在地派出所、街道办事处或乡镇人民政府报备,通过正规渠道回国

18 Dec 2023, 05:12 UTC250 viewsread 10 August 2026
Video

#群友投稿:老街白家的兵现在还在抓中国人,敲诈!

18 Dec 2023, 05:12 UTC431 viewsread 10 August 2026
Photo

福建南安这五条大鱼,警方为了你们都注册小飞机了 福建南安警方通缉多名涉诈人员并征集资金来往账号和使用情况的公告 为严厉打击整治跨境违法犯罪活动,现对福建省南安市康美籍5名滞留境外涉诈重点地区人员予以公布、劝返,并立案进行调查,其中大部分人员已被上网追逃,现敦促此5名人员于2023年12月30日前主动报备入境、返家,相关园区、公司不得聘用非法滞留和非法劳务人员、不得窝藏、阻拦,对包庇在逃人员的将依法追究刑事责任。现公开征集这5名重点人员在国内有资金来往的账号,本人及其家人、直系亲属用疑似诈骗资金大额消费、买车、买房、建房等重要内容或涉诈人员在境外具体信息和涉赌涉诈行为信息,根据线索价值将给予举报者500-5000元/条的奖励,并严格保密。凡是能劝导涉诈重点对象回到属地的或抓获在逃对象并移交的我单位的,奖励人民币1-5万元整。 举报电话:0595-86653110 15396653709 飞机号:@lucky233456 …

18 Dec 2023, 05:12 UTC249 views1 reactionsread 10 August 2026
Photo

#曝光 对环江籍在缅甸、柬埔寨、金三角等国家和地区(以下统称为境外涉诈重点地区)从事违法犯罪活动的人员限期投案自首,并对目前仍滞留境外涉诈重点地区的其他环江籍人员实行集中劝返。 ps:国内打击力度越来越大了。快过年了,大家都在冲业绩😊

👎1

12 Dec 2023, 03:18 UTC480 viewsread 10 August 2026
File

《劝返通告》指出,非法滞留境外人员回国后自动投案,并如实供述自己违法犯罪行为的,是自首。 自2023年11月20日起至2023年12月30日前自首的,依法从轻或减轻处罚;情节较轻的,依法免除处罚。 准备回国自首的,应在回国前3日内向户籍所在地派出所、街道办事处或乡镇人民政府报备,通过正规渠道回国

12 Dec 2023, 03:18 UTC290 viewsread 10 August 2026
Photo

重大新闻 缅北大部分重要人物被通缉 详情:https://mp.weixin.qq.com/s/sm3wSWuxPSFcuSg4zlEfsQ

12 Dec 2023, 03:18 UTC260 viewsread 10 August 2026
Photo

#重磅新闻 中国公安对白所成发布通缉令 PS:还不投降?现在你们跑哪里都多余!

Showing the 9 most recent of 9 posts we hold for @bodu3603. 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

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.

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 14 October 2026 — this entry's latest reading, not the date you are reading this.

“博度-新闻大事件” (@bodu3603), 57 subscribers as measured 14 October 2026. Telegram Register, tgregister.com/channel/bodu3603.

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.