Telegram RegisterThe public register of Telegram
Telegram profile photo for 泰国新闻大事件

Channel

泰国新闻大事件

@BGM9897

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry

54,496subscribers

-36,882 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001570881659
TypeChannel
Username@BGM9897
Description本频道只负责相关发布信息,真假自行甄别 #泰国 #菲律宾 #柬埔寨 #缅甸 #中国 #老挝 #斯里兰卡 #新闻资讯 #博彩 🇲🇲缅甸新闻亚太大事件 @TTC9988 🇰🇭柬埔寨大事件 @JPZ963 🇹🇭泰国新闻大事件 @BGM9897 🇦🇪迪拜大事件曝光 @PPA633 🌸 反差|绿帽|乱伦|萝莉 @bgxs1450s ☎️广告投放 : @PPW881
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/BGM9897

Topic

Other / unclassifiable — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 53% 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.

Observations

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.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 3 other registered channels. 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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@TTC9988/352305 Sept 2026, 05:48 UTC@BGM9897/39586 · this entry5 Sept 2026, 05:49 UTC1.00under a minute
@TTC9988/353649 Sept 2026, 07:08 UTC@BGM9897/39694 · this entry9 Sept 2026, 07:08 UTC1.00under a minute
@TTC9988/3540411 Sept 2026, 04:49 UTC@BGM9897/39717 · this entry11 Sept 2026, 04:49 UTC1.00under a minute
@TTC9988/3547413 Sept 2026, 05:39 UTC@BGM9897/39774 · this entry13 Sept 2026, 05:39 UTC1.00under a minute
@TTC9988/3574122 Sept 2026, 15:14 UTC@BGM9897/40037 · this entry22 Sept 2026, 15:35 UTC1.0022 minutes
@JPZ963/4247814 Aug 2026, 12:11 UTC@BGM9897/39049 · this entry14 Aug 2026, 14:49 UTC1.002.6 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@TTC998827 (8/8 hand-verifiable sample passed)1.00under a minute@TTC9988 (23–4)
@JPZ96324 (8/8 hand-verifiable sample passed)1.00under a minute@JPZ963 (18–6)
@PPA63317 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (13–4)

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. 26 of the 26 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 1,414 comparable posts for this entry, running 7 August 2026 to 15 November 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the keys clone_copy · clone_source, last confirmed 16 November 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.

Growth

51,09791,37871,237.554,4967 August 202613 November 2026
64 measurements spanning 98 days, net -36,882. 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 45,055–97,420 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
13 Nov 2026, 09:5454,496+206
10 Nov 2026, 19:5954,290-824
9 Nov 2026, 02:5055,114-527
7 Nov 2026, 16:1555,641+981
6 Nov 2026, 13:1654,660-177
5 Nov 2026, 14:3954,837-370
4 Nov 2026, 16:2155,207-297
3 Nov 2026, 19:5155,504+401
2 Nov 2026, 17:0055,103-983
1 Nov 2026, 18:2656,086+728
31 Oct 2026, 17:3155,358-554
30 Oct 2026, 20:1955,912+3,195
29 Oct 2026, 18:2952,717-528
28 Oct 2026, 17:0853,245-573
27 Oct 2026, 13:4753,818-399
26 Oct 2026, 10:3854,217-489
25 Oct 2026, 10:1554,706-340
24 Oct 2026, 07:4655,046+3,949
23 Oct 2026, 06:5851,097-306
22 Oct 2026, 10:1951,403first reading

Engagement

1,436 posts held, back to 7 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 220 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
6.16%
avg views ÷ 54,496 subscribers
Avg views / post
3,360
445 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
445
of 1,436 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 15 November 2026
Posts held1,436 (7 August 2026 – 15 November 2026)
Views total1,494,635
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 04:31 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
≈25,600
Videos
≈2,160
Links
≈13,700

Lifetime counters from Telegram’s own channel header, read 16 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 16m
Average length
42s

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

Reaction mix

10 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 30.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👏330.0%
⚡220.0%
🔥220.0%
❤110.0%
👍110.0%
😁110.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 12 of the 1,000 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 10 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 6 September 2026 to 15 November 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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 445 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).

15 Nov 2026, 15:41 UTC≈4,530 viewsread 16 November 2026
Photo

【泰国突发】橡胶园埋尸案2名证人被讯问!穆达汉府警方等待DNA确认失踪者身份 2026年11月15日,在穆达汉府坎猜县的一处橡胶园内发现一具被埋在土里的尸体,已送往法医鉴定以确认身份,推测是亲属失踪超过2个月的人员。此前家属已寻找失踪者超过2个月,直到有人发现可疑的坑洞并通知警方前来检查,最终将遗体挖出。根据警方和法医人员的初步检查,现场情况符合伪装谋杀的特征,但尚无法明确死因,需等待进一步的法医鉴定结果。最新消息,上午9时50分,警方对与发现尸体埋藏坑有关的2名证人进行了讯问,分别是49岁男子(第一个发现该坑的人)和52岁男子(被邀请一同前往查看该坑的人)。发现遗体后,警方在现场收集了证据,并对相关人员进行了询问,以梳理事件经过,查明死者身份及死因。与此同时,警方正在进行DNA鉴定,以确认发现的遗体是否为家属寻找了两个多月的失踪者,鉴定结果将成为确认身份及破案的重要证据。事件凸显埋尸案件的侦查复杂性与DNA身份确认的关键作用…

15 Nov 2026, 15:19 UTC4 viewsread 16 November 2026
Photo

#泰国新闻 巴吞他尼府发生家庭命案!丈夫疑因妻子不忠,持木棍和扳手将其打死后自首 11月15日上午泰国巴吞他尼府发生一起严重家庭暴力案件。一名男子怀疑妻子不忠,情绪失控后,涉嫌使用三叉木棍和拆轮扳手殴打妻子,最终导致妻子死亡。 案发后,男子向警方自首。目前案件仍有待进一步调查,具体冲突经过及相关细节将由警方依法查明。 ⭐️⭐️ 点击观看老湿机开车视频 ☎️免费投稿广告商务合作:@PPW881

15 Nov 2026, 14:28 UTC6 viewsread 16 November 2026
Photo

【泰国新闻】达府边境拦截一辆涉嫌走私牛油果皮卡 查获约3.5吨无进口文件货物 【事件通报】2026年11月13日,拉查曼努特遣部队联合相关部门,在泰缅边境拦截走私非法商品。最新发现一辆可疑皮卡车,车内装满130箱牛油果,总重约3500公斤,且无进口文件。 【调查细节】警方随后联手逮捕了该皮卡车司机,指控其违反《1964年植物检疫法》和《2017年海关法》,并查封了全部牛油果作为证物,随后将其移交给湄索警察局调查人员,以依法进一步处理。有关部门表示,正追查货物来源及走私网络,依法处理相关责任人。 ⭐️⭐️ 点击观看老湿机开车视频 ☎️免费投稿广告商务合作:@PPW881

15 Nov 2026, 14:05 UTC5 viewsread 16 November 2026
Photo

#泰国新闻 阿努廷回应柬首相指控 重申尊重双边协议 泰国总理兼内政部长阿努廷11月15日在脸书发文,回应柬埔寨首相洪玛奈有关泰国入侵并占领柬埔寨领土的指控,重申泰国一贯尊重与柬埔寨签署的全部协议。 阿努廷表示,洪玛奈在金边法语国家组织峰会发表相关言论,他因此再次表明泰方立场,称泰国行动目标是保护主权、领土完整与人民安全。 他表示,泰国没有政策将双边争端特别是领土或人道议题拿去与不属于该冲突当事方的其他国家讨论,仍致力于通过双边机制并依照国际法和平解决分歧。 ⭐️⭐️ 点击观看老湿机开车视频 ☎️免费投稿广告商务合作:@PPW881

15 Nov 2026, 14:05 UTC3 viewsread 16 November 2026
Photo

#泰国新闻 泰内政部副部长赴湄索检查掩体建设 2026年11月15日,泰国内政部副部长杰拉塞前往达府湄索县玛哈万镇,检查用于应对泰缅边境战事影响民众的掩体建设进展。 此次检查旨在为受边境战事影响的民众做好安全准备并加强照顾措施。泰方军警和行政部门继续在边境地区全天24小时部署力量,以维护主权并保护边境民众生命财产。 11月初,一枚火箭推进榴弹越境落入玛哈万镇一名村民住宅,房屋受损但屋主及家人安全,军警到场检查取证。此前10月29日,一枚迫击炮弹越境落入民宅致一名55岁居民受伤 ⭐️⭐️ 点击观看老湿机开车视频 ☎️免费投稿广告商务合作:@PPW881

15 Nov 2026, 13:25 UTC5 viewsread 16 November 2026
Photo

【中国男子涉职务侵占5700万泰铢 潜逃泰国被捕】 2026年11月15日,泰国打击犯罪警察在曼谷拉差达披色地区逮捕26岁中国籍男子刘某。其2024年9月至2025年7月任芜湖一仓储公司仓库主管期间,偷运零部件非法出售并伪造单据,造成损失1130万元人民币(约5720万泰铢),被中国警方通缉后潜逃泰国,已被移送并协调引渡。 ⭐️⭐️ 点击观看老湿机开车视频 ☎️免费投稿广告商务合作:@PPW881

15 Nov 2026, 12:59 UTC6 viewsread 16 November 2026
Photo

#春武里府车祸 【“从后方加速、撞上对向摩托车”——春武里府三死车祸目击者还原撞击瞬间】 据泰国邦拉蒙县警方2026年11月14日消息,春武里府邦拉蒙县农普鲁分区发生三辆摩托车相撞事故,造成3人死亡。23岁目击者塔纳乔(Thanachot)向警方表示,事发时他驾驶轿车从Soi Khao Talo驶向素坤逸路,看到一辆雅马哈XMAX跟在后方,随后该车突然加速,撞上一辆逆向行驶的本田Wave 125,车上司机和乘客被甩向不同方向。 两名17岁死者的朋友称,他们刚从海滩捕鱿鱼回来,正骑车返回住处,途中得知朋友遭遇事故。邦拉蒙警察局调查官瓦塔纳吉·约德迈警中校已在现场拍照取证,并指示调取附近监控,以确认事故原因。警方将结合目击者陈述、监控画面及车辆痕迹,调查XMAX是否超速或违规超车,并依法认定责任。 ⭐️⭐️ 点击观看老湿机开车视频 ☎️免费投稿广告商务合作:@PPW881

15 Nov 2026, 12:32 UTC6 viewsread 16 November 2026
Photo

#泰国新闻 碧差汶警方两天检查 1524 辆车 处罚 794 名摩托车骑手 国家警察总署交通管理中心副主任尼提通・金达甘警中将 11 月 14 日通报,警方联合第一警区、第六警区及中央调查警察总部,针对 11 月 13‑15 日在碧差汶府举办的 “不沾水之旅” 摩托车团体活动开展交通管控,在主要道路、休息点、加油站沿线布设检查站,严查超速、危险驾驶、车辆非法改装、无证驾驶、未佩戴头盔等违法行为。 11 月 13 日至 14 日,警方累计查验摩托车 1308 辆、摩托车运输车 216 辆,合计 1524 辆;对 794 人作出交通违法处罚,违法行为包含无证驾驶、车辆设备故障、未戴头盔、无牌照、非法改装等,现场扣押摩托车 23 辆。行动当中共抓获 3 名涉案人员,其中一人持有北标府法院通缉令,另外两人涉嫌毒品犯罪,警方缴获甲基苯丙胺药丸合计 96 粒,相关案件正在办理。 尼提通警中将表示,按照总署署长萨拉暖・努阿尔玛的政策…

15 Nov 2026, 12:32 UTC4 viewsread 16 November 2026
Photo

#芭提雅 紧急营救:19 岁留学生被勒索千万泰铢,警方 30 分钟成功解救 11 月 14 日,一名 19 岁中国留学生在泰国芭提雅疑似被跨国犯罪团伙控制,家属收到200 万元人民币(约 1000 万泰铢) 赎金要求,对方扬言不付款将砍断其手臂。 中泰警方紧急联动,泰国快速反应小组迅速锁定酒店位置,接报约 30 分钟后安全救出受害者,目前案件仍在进一步调查中。 ⭐️⭐️ 点击观看老湿机开车视频 ☎️免费投稿广告商务合作:@PPW881

14 Nov 2026, 15:24 UTC10 viewsread 15 November 2026
Photo

#泰国新闻 玛哈沙拉堪山上发现掩埋尸体 亲属疑为失踪两月男子 11月12日,泰国玛哈沙拉堪府甘他拉威猜县班科山上一具遗体被发现埋在地下约40厘米深处。当地村民上山寻找野生动物时,狗在附近刨土并传出异味,村民随即下山通知村长并联系警方。11月13日记者到场核实,发现地点距村庄约10公里。警方表示死者身份及死因均在调查中;有亲属怀疑死者是30岁的苏帕乔克,其为班科分区居民,自2026年9月3日起失联,曾告诉家人要去曼谷找工作。遗体已送往孔敬府尸检,苏帕乔克父母随行并采集DNA样本比对。警方表示需待DNA检测结果正式确认身份,并等待尸检结果查明死因,之后才进入法律程序。 ⭐️⭐️ 点击观看老湿机开车视频 ☎️免费投稿广告商务合作:@PPW881

14 Nov 2026, 14:42 UTC≈5,080 viewsread 15 November 2026
Photo

#泰国新闻 泰内阁下发紧急公文 要求警方和平处置集会 泰国内阁秘书处发出紧急公文,传达内阁针对民众集会确定的处置方针。文件提出,政府尊重民众合法和平表达诉求的权利,要求警方搭配相关单位提供基础便民设施,优先依靠谈判沟通维持秩序,杜绝武力对峙。公文同时要求各公务部门主动跟进集会诉求,在职权范围内加速处理,并及时向民众通报处置进度,保障集会活动有序开展。 ⭐️⭐️ 点击观看老湿机开车视频 ☎️免费投稿广告商务合作:@PPW881

14 Nov 2026, 14:02 UTC≈5,350 viewsread 15 November 2026
Video

#普吉岛货车刹车失灵连撞10车 1人受伤 据泰国媒体报道,11月14日上午8时许,普吉岛拉沙达县普吉主路附近一路口处,一辆货车因刹车失灵,高速撞上正在等红绿灯的多辆汽车,造成10辆车损毁、1人受伤。 警方调查称,42岁司机从那空帕侬府运货驶往普吉岛,事发前曾踩刹车约20次,但刹车已失灵,车辆失控撞上其他车辆。 酒精检测结果为阴性,但尿液检测呈阳性。警方正对司机进一步讯问,并将依法处理。 ⭐️⭐️ 点击观看老湿机开车视频 ☎️免费投稿广告商务合作:@PPW881

Showing the 12 most recent of 1,436 posts we hold for @BGM9897. 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.

Posts recorded as deleted after publishing

We recorded 15 posts on @BGM9897 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
8 August 2026
Most recent seen missing
18 October 2026
Median time before seen missing
16 hours
Seen missing in the last 30 days
1

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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

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.

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

“泰国新闻大事件” (@BGM9897), 54,496 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/BGM9897.

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.