Channel
@kk256
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
42,472subscribers
-18,869 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001827103148 |
|---|---|
| Type | Channel |
| Usernames | @kk256 @V5771 @zz456 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 191 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/kk256 |
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 20 August 2026 and assigned it the closest of 31 fixed categories, at 42% 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.
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 in near-verbatim form on 4 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @gegong05/652710 Aug 2026, 09:41 UTC | @kk256/11935 · this entry10 Aug 2026, 09:43 UTC | 1.00 | 2 minutes |
| @gegong05/667111 Aug 2026, 15:08 UTC | @kk256/12039 · this entry11 Aug 2026, 15:09 UTC | 1.00 | under a minute |
| @gegong05/920529 Aug 2026, 13:07 UTC | @kk256/14323 · this entry29 Aug 2026, 13:07 UTC | 1.00 | under a minute |
| @gegong05/1311314 Oct 2026, 16:05 UTC | @kk256/19467 · this entry14 Oct 2026, 16:05 UTC | 1.00 | under a minute |
| @gegong05/1392123 Oct 2026, 16:45 UTC | @kk256/20275 · this entry23 Oct 2026, 16:45 UTC | 1.00 | under a minute |
| @kk256/20021 · this entry21 Oct 2026, 09:54 UTC | @gegong05/1405124 Oct 2026, 15:55 UTC | 1.00 | 3 days |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @gegong05 | 14 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (9–5) |
| @kk298 | 14 (8/8 hand-verifiable sample passed) | 0.95 | under a minute | this entry (13–1) |
| @zol_com_cn | 5 (5/5 hand-verifiable sample passed) | 0.90 | 1.6 hours | this entry (5–0) |
| @gegong0000 | 5 (5/5 hand-verifiable sample passed) | 0.88 | 1.5 hours | this entry (5–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. 6 of the 6 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,833 comparable posts for this entry, running 6 August 2026 to 10 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.
Recorded under the keys clone_mutual · clone_source, last confirmed 11 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 08:21 | 42,472 | -21 |
| 10 Nov 2026, 11:05 | 42,493 | -18 |
| 9 Nov 2026, 18:28 | 42,511 | -3 |
| 9 Nov 2026, 14:55 | 42,514 | -6 |
| 8 Nov 2026, 22:09 | 42,520 | -19 |
| 8 Nov 2026, 09:04 | 42,539 | -2 |
| 8 Nov 2026, 04:17 | 42,541 | -14 |
| 7 Nov 2026, 11:28 | 42,555 | -13 |
| 7 Nov 2026, 01:59 | 42,568 | no change |
| 7 Nov 2026, 01:05 | 42,568 | +1,266 |
| 6 Nov 2026, 10:16 | 41,302 | +135 |
| 6 Nov 2026, 05:20 | 41,167 | +213 |
| 5 Nov 2026, 23:14 | 40,954 | +77 |
| 5 Nov 2026, 10:54 | 40,877 | -3 |
| 5 Nov 2026, 01:40 | 40,880 | -3 |
| 4 Nov 2026, 21:08 | 40,883 | -10 |
| 4 Nov 2026, 08:11 | 40,893 | -11 |
| 3 Nov 2026, 21:57 | 40,904 | -4 |
| 3 Nov 2026, 19:09 | 40,908 | -12 |
| 3 Nov 2026, 07:37 | 40,920 | first reading |
2,085 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 194 pages of 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. It is computed over the 1 of 683 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 10 November 2026 |
|---|---|
| Posts held | 2,085 (6 August 2026 – 10 November 2026) |
| Views total | 356,059 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 00:14 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.
Measured directly from 224 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.
32 reactions across 32 posts, in 8 distinct kinds. The most used accounts for 25.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤩 | 8 | 25.0% | |
| 🎉 | 6 | 18.8% | |
| ⚡ | 4 | 12.5% | |
| ❤ | 4 | 12.5% | |
| 🥰 | 4 | 12.5% | |
| 👍 | 2 | 6.25% | |
| 👏 | 2 | 6.25% | |
| 🔥 | 2 | 6.25% |
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 34 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 32 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 29 September 2026 to 10 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.
Telegram’s own ‘edited’ marker: 462 of 685 posts held from the last 30 days (67.4%) 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).
#缅甸局势 妙瓦底南部战事：军方改用FPV无人机攻击 据KNLA盟军消息，克伦邦妙瓦底市以南敏拉班村和黛布乔一带的战斗中，军方自11月7日后改用FPV无人机进行攻击。此前军方反攻时子弹越境落入泰国，遭泰方警告后改变战术。前线部队成员称，军方增兵遭击退后即改用FPV无人机回击，盟军方面也进行拦截击落。 据报道，军方还隔几天用降落伞向皎瓦博山脉和莱凯考瀑布一带空投粮食、弹药及无人机设备，并从帕安第22师调增援车队进入妙瓦底方向，同时转运伤员和轮换部队回帕安。 Ps：还是挺怕泰国打过来的🤣 👑联盟导航 @xw234 😄投稿 @cc319
#网友投稿： 金三角特外，最近会迎来联合执法，会塞和别的地区已经来了很多警察了，特外暂时停工撤离了，暂时是待不了。 👑联盟导航 @xw234 😄投稿 @cc319
#秘鲁资讯 🇵🇪 秘鲁外交部长于莫斯科会晤拉夫罗夫，就俄罗斯招募秘鲁公民赴乌克兰参战事宜进行正式交涉 11月9日，秘鲁外交部长埃斯帕在莫斯科会见俄罗斯外交部长拉夫罗夫，就俄方招募秘鲁公民前往乌克兰参与军事行动一事提出正式交涉，请求俄方协助联系受伤的秘鲁公民，并安排阵亡同胞遗体运回国内。 埃斯帕指出，经核实，至少有459名秘鲁公民在乌克兰参与战斗，各方家属均迫切希望了解亲属的安危状况，包括其生存状态及是否被俘。相关报道提及，俄方以高额薪酬招募外籍人员参战，招募对象主要来源于南美洲及非洲地区；另有消息称，俄方将部分在俄服刑的外籍囚犯派往前线，且南美洲雇佣兵在俄乌冲突双方中均有出现。 除秘鲁外，多个国家亦要求俄方停止招募本国公民，并归还阵亡者遗体。哥伦比亚此前通报称，已有250多名本国公民在乌克兰阵亡，近千人参战后失踪。 👑联盟导航 @xw234 😄投稿 @cc319
#柬埔寨资讯 连续5年被列人口贩运最严重等级 柬埔寨表示不满 11月9日，柬埔寨国家打击人口贩运委员会发表声明，回应美国国务院最新发布的《2026年人口贩运报告》。柬埔寨连续第五年被列入第三级（Tier 3），即报告中的最低评级。 柬埔寨政府对此表示不满，认为美国的评价未能充分反映柬埔寨近年来打击人口贩运的努力和实际成果。 美国国务院10月9日发布的《2026年人口贩运报告》指出，柬埔寨政府未达到消除人口贩运的最低标准，也未作出显著努力。报告指控，部分柬埔寨高级官员、顾问及执法人员从电诈园区的人口贩运活动中获利，并干预执法、庇护园区经营者。 👑联盟导航 @xw234 😄投稿 @cc319
#网友投稿：防止突袭 我们从缅甸大其力山区搬家到孟东镇边角上有一个多星期了，这次搬家后估计以后都不会再搬回大其力。 从保护我们的缅军内部人员传出消息，本月开始中国政府那边已经严肃的下来指令要求缅甸大其力全面配合整治打击残留在这里的电诈产业。 只要是从事有关中国人的电诈一律打击绝不姑息，不管他是缅甸佬泰国人还是越南人发现后都要先逮捕起来再做处罚，性质恶劣的还会被引渡去中国国内审判。 这是要再次警示那些依然在开中国电诈盘的外国人，不要以为是外国人中国政府就束手无策。看看之前的缅甸四大诈骗家族领导掌门人，引渡去中国审判后不说各个都会安排上死刑，但牢底坐穿直到变成骨灰还是可刑的。 保护我们公司的缅军士兵可能懵懂无知但他们的军官还是有些害怕，但又不想丢了电诈这块摇钱树大产业，那只能是搬家搬远些再躲好。搬家后看见有保护我们的缅军这次连肩扛式导弹RPG都带上了，那可不是拿着RPG用来吓唬公司员工不要逃跑的。 孟东这个地方现在依然有…
#国内资讯 “期货回款”100万柜员没信，警察到了柜台，取款车手当场落网 赵某受境外电诈团伙雇佣，当“取款车手”。提前预约大额取现，到西安雁塔区一家银行柜台，说100万是期货回款。柜员一问资金来源，说不清；再看流水，大额资金短时间入账，符合涉诈账户特征。一边稳住他、拖延办理，一边向反诈中心报警。民警赶到柜台，当场摁住。100万涉案资金全部拦截、冻结，没被取走。 查实：赵某长期流窜甘肃、湖南、江西等地，异地办卡，专门接收境外电诈赃款。接到上线指令后到银行大额取现，把线上赃款变成现金，切断资金追踪，事成拿佣金。 👑联盟导航 @xw234 😄投稿 @cc319
#缅甸新闻 缅甸掸邦南部捣毁网赌网诈窝点，抓获 15 名中国籍人员，起获星链设备 11 月 10 日缅方通报，缅甸安全部队 9 日下午 2 时在掸邦南部柯西镇区 Nongwo 村以南 2.5 公里处开展联合清查，破获一处电信网络诈骗、网络赌博窝点，抓获 15 名中国籍人员，怀疑他们非法入境参与相关犯罪。 该据点是临时搭建棚屋，包含工作间、住宿棚、厨房和储水设施。现场扣押 40 部手机、2 台一体机电脑、2 套星链卫星上网设备、6 台路由器，另查获发电机、冰柜、风扇等物资。 稍早的 11 月 5 日，缅方在同区域孟瑙镇抓获 17 名中国籍人员，搜出 50 部手机、20 台一体机、5 套星链设备。两起窝点位置不同，目前暂不清楚两个团伙是否有关联。 👑联盟导航 @xw234 😄投稿 @cc319
#突发事件： 金边市铁桥头区一处穆斯林居民住宅突发火灾，现场火势猛烈。目前，起火原因及人员伤亡情况尚不清楚。 👑联盟导航 @xw234 😄投稿 @cc319
#法国新闻 法国启动司法调查，疑伊朗革命卫队黑客组织入侵温控系统，造成超市冷藏设备损毁 11 月 10 日，巴黎检察官宣布，正式对伊朗伊斯兰革命卫队下属黑客组织 “沙希德・卡韦”（Shahid Kaveh）相关人员立案调查，该组织专门负责攻击性网络行动。 这起攻击针对冷链温控系统，黑客入侵后把超市冷藏冰箱调至异常高温，部分冰箱起火，大量肉类、冰淇淋变质报废，有商户估算法国全国损失可达数千万欧元。另有血库冷藏设施受波及，工作人员紧急转移血液样本。 专家分析，遭入侵设备固件老旧、缺少更新，是容易被攻破的原因。今年 8 月美国也出现美军基地商店冰箱异常故障事件，美方怀疑同样和伊朗相关，五角大楼正和法国协作追查。目前暂无法证实美欧两起事件是否为同一团伙所为，伊朗方面否认实施恶意网络攻击。报道称本次攻击或是相关冲突爆发以来破坏力最强的网络攻击之一。 👑联盟导航 @xw234 😄投稿 @cc319
#国际贸易 越南与日本深化全面战略伙伴关系，经济、贸易及投资合作稳步推进 越南与日本之间的经济合作持续受到关注。据VietnamPlus及BERNAMA报道，自2023年两国关系升级为全面战略伙伴关系以来，经济、贸易及投资领域一直是双边合作的核心支柱。 日本企业长期参与越南制造业、基础设施及相关产业的投资，双方亦通过贸易与商业合作保持紧密联系。 越南旨在提升制造业竞争力并拓展国际市场联系，而日本在技术、产业管理及资本方面具备显著优势，双方在多个领域存在广阔的合作空间。 国际企业正密切关注供应链稳定性及生产布局，越日经济关系亦与更广泛的亚洲贸易网络紧密相连。 此次报道主要回顾并介绍了双边经济合作的发展历程，并未确认于11月9日签署新的大型投资合同。 👑联盟导航 @xw234 😄投稿 @cc319
#网友反馈： 西港日月兴赌场路段，宪兵设卡查车，查毒品，违禁作，吓得楼上的推推闻风而逃。 👑联盟导航 @xw234 😄投稿 @cc319
#老挝资讯 警方打掉万象网络犯罪窝点，抓获13名孟加拉籍嫌疑人！ 老挝媒体报道：11月7日晚，老挝公安部专项工作组突袭万象市赛色塔县洪素帕村一处出租屋，成功打掉一处网络犯罪窝点，当场抓获13名孟加拉籍嫌疑人（含1名女性）。 行动现场查获手机21部、台式电脑12台等作案工具。 目前，案件正在进一步侦办深挖中。 Ps：中国推推全军覆没 最近抓的都是老外 👑联盟导航 @xw234 😄投稿 @cc319
Showing the 12 most recent of 2,085 posts we hold for @kk256. 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.
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“东南亚大事件|柬埔寨菲律宾斯里兰卡” (@kk256), 42,472 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/kk256.
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.