Channel
@kk298
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
42,460subscribers
+28,970 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001835317942 |
|---|---|
| Type | Channel |
| Username | @kk298 |
| Description | 😃广告位招商 ： @kk130 ✈️七星海扶手交流群：@QXH177 💎七星海二手交易 ：@QXH14 ✅ 新闻联盟 ：@xw179 |
| 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 | 10 November 2026 |
| Measurements held | 61 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/kk298 |
National 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 100% 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 2 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 |
|---|---|---|---|
| @kk256/1193510 Aug 2026, 09:43 UTC | @kk298/7535 · this entry10 Aug 2026, 09:44 UTC | 1.00 | under a minute |
| @kk298/9791 · this entry29 Aug 2026, 13:07 UTC | @kk256/1432329 Aug 2026, 13:07 UTC | 1.00 | under a minute |
| @kk298/11528 · this entry15 Sept 2026, 14:35 UTC | @kk256/1605715 Sept 2026, 14:35 UTC | 1.00 | under a minute |
| @kk256/2002121 Oct 2026, 09:54 UTC | @kk298/15733 · this entry24 Oct 2026, 15:55 UTC | 1.00 | 3 days |
| @kk298/11947 · this entry18 Sept 2026, 16:16 UTC | @kk256/1647818 Sept 2026, 16:16 UTC | 0.98 | under a minute |
| @kk298/11421 · this entry14 Sept 2026, 16:24 UTC | @kk256/1594914 Sept 2026, 16:25 UTC | 0.92 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @kk256 | 14 (8/8 hand-verifiable sample passed) | 0.95 | under a minute | @kk256 (13–1) |
| @gegong05 | 7 (7/7 hand-verifiable sample passed) | 0.98 | under a minute | @gegong05 (4–3) |
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. 17 of the 17 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,501 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_copy · clone_mutual, 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 |
|---|---|---|
| 10 Nov 2026, 13:58 | 42,460 | -741 |
| 9 Nov 2026, 01:47 | 43,201 | -661 |
| 7 Nov 2026, 18:27 | 43,862 | +157 |
| 6 Nov 2026, 19:20 | 43,705 | +1,206 |
| 5 Nov 2026, 21:16 | 42,499 | -360 |
| 4 Nov 2026, 18:46 | 42,859 | -294 |
| 3 Nov 2026, 17:20 | 43,153 | -44 |
| 2 Nov 2026, 14:21 | 43,197 | -262 |
| 1 Nov 2026, 14:10 | 43,459 | -570 |
| 31 Oct 2026, 17:10 | 44,029 | -596 |
| 30 Oct 2026, 19:30 | 44,625 | -962 |
| 29 Oct 2026, 17:09 | 45,587 | +5,352 |
| 28 Oct 2026, 19:49 | 40,235 | +624 |
| 27 Oct 2026, 17:11 | 39,611 | -565 |
| 26 Oct 2026, 13:45 | 40,176 | -1,036 |
| 25 Oct 2026, 11:29 | 41,212 | -560 |
| 24 Oct 2026, 11:46 | 41,772 | -932 |
| 23 Oct 2026, 10:08 | 42,704 | -505 |
| 22 Oct 2026, 12:16 | 43,209 | -1,061 |
| 21 Oct 2026, 09:09 | 44,270 | first reading |
1,824 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 168 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 726 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 | 1,824 (6 August 2026 – 10 November 2026) |
| Views total | 109,254 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 00:19 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.
Lifetime counters from Telegram’s own channel header, read 11 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.
Measured directly from 222 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.
Telegram’s own ‘edited’ marker: 495 of 726 posts held from the last 30 days (68.2%) 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无人机攻击。前线称军方增兵遭击退后即用无人机回击，盟军予以拦截击落。 报道称，军方近期向皎瓦博山脉及莱凯考瀑布空投粮食、弹药及无人机设备，并从帕安第22师调增援车队进入妙瓦底，同时转运伤员及轮换部队。 Ps：挺怕泰国打过来🤣 ✅ 投稿 @kk130
#网友投稿：金三角特外近期将联合执法，会塞及他地已增派警力，特外停工撤离，暂无法停留。 ✅ 投稿 @kk130
#秘鲁资讯 🇵🇪 秘鲁外长莫斯科会晤拉夫罗夫，交涉俄招募秘鲁公民赴乌参战事宜 11月9日，秘鲁外长埃斯帕在莫斯科会见拉夫罗夫，就俄招募秘鲁公民赴乌参战提出正式交涉，要求俄方协助联系受伤公民并安排阵亡者遗体回国。 埃斯帕证实至少459名秘鲁公民在乌参战，家属迫切希望了解亲属安危。据悉，俄方高薪招募南美及非洲人员参战，并有消息指俄方派遣外籍囚犯上前线，南美雇佣兵出现在冲突双方。 哥伦比亚等多国亦要求俄方停止招募本国公民并归还遗体。哥方通报已有250多名公民在乌阵亡，近千人失踪。 ✅ 投稿 @kk130
#柬埔寨资讯 柬埔寨连续5年人口贩运评级最低，政府不满 11月9日，柬埔寨国家打击人口贩运委员会声明，回应美国国务院《2026年人口贩运报告》。柬埔寨连续第五年被评为第三级（Tier 3）。 柬政府不满，认为美方评价未反映其打击人口贩运的努力及成果。 美国国务院10月9日报告指出，柬埔寨未达消除人口贩运最低标准，且未作显著努力。报告指控部分柬高级官员、顾问及执法人员从电诈园区人口贩运中获利，并干预执法、庇护园区经营者。 ✅ 投稿 @kk130
#网友投稿：防止突袭 已从大其力迁至孟东镇逾一周，不再返回。 据缅军内部消息，本月起中国政府指令大其力全面整治电诈。 涉及中国人的电诈一律打击，绝不姑息。发现即逮捕，性质恶劣者引渡中国审判。此前四大诈骗家族头目引渡后，面临终身监禁。 保护公司的缅军士兵懵懂，军官畏惧。为保利益选择迁离藏匿。搬家时，保护我们的缅军携带肩扛式导弹和RPG，意在实战防御。 孟东仍有武力冲突风险，缅军携RPG旨在抵御敌对武装突袭，保护电诈基地。珍爱生命，请远离此地；若留缅，务必选无武装冲突地区。 ✅ 投稿 @kk130
#国内资讯 “期货回款”100万柜员没信，警察到了柜台，取款车手当场落网 赵某受境外电诈团伙雇佣当“取款车手”。在西安雁塔区一银行预约取现100万，谎称期货回款。柜员核查发现资金来源不明、流水符合涉诈特征，遂稳住其并报警。民警到场将其抓获，100万资金全部拦截冻结。 查实：赵某长期流窜甘肃、湖南、江西等地异地办卡，专门接收境外电诈赃款。其将线上赃款取现以切断追踪，事后领取佣金。 ✅ 投稿 @kk130
#缅甸新闻 缅甸掸邦南部捣毁网赌网诈窝点，抓获15名中国籍人员，起获星链设备 11月10日缅方通报，9日下午2时安全部队在掸邦南部柯西镇区Nongwo村以南2.5公里处查获一处电信网络诈骗、网络赌博窝点，抓获15名涉嫌非法入境的中国籍人员。 该据点为临时棚屋，含工作、住宿及生活设施。现场扣押40部手机、2台一体机、2套星链设备、6台路由器及发电机等物资。 11月5日，缅方在同区域孟瑙镇抓获17名中国籍人员，搜出50部手机、20台一体机、5套星链设备。两窝点位置不同，团伙关联尚不明确。 ✅ 投稿 @kk130
#法国新闻 法国启动司法调查，疑伊朗革命卫队黑客组织入侵温控系统，造成超市冷藏设备损毁 11月10日，巴黎检察官正式对伊朗伊斯兰革命卫队下属黑客组织“沙希德・卡韦”（Shahid Kaveh）立案调查。该组织负责攻击性网络行动，此次入侵导致超市冷藏冰箱异常高温，部分起火，大量肉类、冰淇淋变质，预估损失数千万欧元。血库冷藏设施亦受影响，血液样本紧急转移。 专家指出，设备固件老旧且缺乏更新是易受攻击原因。今年8月美军基地商店冰箱故障，美方怀疑与伊朗有关，五角大楼正与法国协作追查。目前无法证实两起事件是否同一团伙所为，伊朗否认实施攻击。此次事件或为相关冲突爆发以来破坏力最强的网络攻击之一。 ✅ 投稿 @kk130
#国际贸易 越南与日本深化全面战略伙伴关系，经济、贸易及投资合作稳步推进 越南与日本之间的经济合作持续受到关注。据VietnamPlus及BERNAMA报道，自2023年两国关系升级为全面战略伙伴关系以来，经济、贸易及投资领域一直是双边合作的核心支柱。 日本企业长期参与越南制造业、基础设施及相关产业的投资，双方亦通过贸易与商业合作保持紧密联系。 越南旨在提升制造业竞争力并拓展国际市场联系，而日本在技术、产业管理及资本方面具备显著优势，双方在多个领域存在广阔的合作空间。 国际企业正密切关注供应链稳定性及生产布局，越日经济关系亦与更广泛的亚洲贸易网络紧密相连。 此次报道主要回顾并介绍了双边经济合作的发展历程，并未确认于11月9日签署新的大型投资合同。 ✅ 投稿 @kk130
#网友反馈：西港日月兴赌场路段宪兵设卡查车、查毒品及违禁品，楼上推推闻风而逃。 ✅ 投稿 @kk130
#老挝资讯 警方端掉万象网赌窝点，抓获13名孟加拉嫌疑人 11月7日晚，老挝公安部突袭万象赛色塔县洪素帕村出租屋，捣毁网络犯罪窝点，抓获13名孟加拉籍嫌疑人（含1名女性）。现场查获手机21部、电脑12台。案件正深入侦办。 Ps：中国推推全军覆没 最近抓的都是老外 ✅ 投稿 @kk130
#马来资讯 不法分子假冒陈珊珊WhatsApp账号诈骗5万令吉 不法分子盗用马华柔佛再也州议员陈珊珊头像及身份，注册新WhatsApp账号行骗。起初以企业扶持政策为由，见对方无意后改称需代转领导礼金，以领导外出不便携带现金为由，诱骗向AmBank转账5万令吉并承诺归还。 陈珊珊获知后发脸书警示。受害者察觉异常未转账，无财务损失。目前无其他报案，骗子获取联系人途径待查。 ✅ 投稿 @kk130
Showing the 12 most recent of 1,824 posts we hold for @kk298. 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.
Named by 1 registered channel — 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.
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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“头条日报” (@kk298), 42,460 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/kk298.
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.