Channel
@DB_622
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Cite this entry
921subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002990288609 |
|---|---|
| Type | Channel |
| Username | @DB_622 |
| Created | Between 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 6 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 6 August 2026 |
| On Telegram | t.me/DB_622 |
National 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 11 August 2026 and assigned it the closest of 31 fixed categories, at 95% 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 why it has no browse page of its own yet.
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 word for word on 1 other registered channel. 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 |
|---|---|---|---|
| @dibai177/45395 Aug 2026, 07:45 UTC | @DB_622/4652 · this entry5 Aug 2026, 07:45 UTC | 1.00 | under a minute |
| @dibai177/45456 Aug 2026, 09:11 UTC | @DB_622/4658 · this entry6 Aug 2026, 10:23 UTC | 1.00 | 71 minutes |
| @dibai177/45466 Aug 2026, 09:38 UTC | @DB_622/4659 · this entry6 Aug 2026, 10:23 UTC | 1.00 | 44 minutes |
| @dibai177/45496 Aug 2026, 10:22 UTC | @DB_622/4662 · this entry6 Aug 2026, 10:23 UTC | 1.00 | under a minute |
| @dibai177/45516 Aug 2026, 10:22 UTC | @DB_622/4664 · this entry6 Aug 2026, 10:23 UTC | 1.00 | under a minute |
| @dibai177/45526 Aug 2026, 10:22 UTC | @DB_622/4665 · this entry6 Aug 2026, 10:23 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @dibai177 | 17 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @dibai177 (17–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. 14 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 20 comparable posts for this entry, running 5 August 2026 to 6 August 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.
Across the whole group of 2, the earliest publisher we hold is @dibai177. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 7 August 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.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Aug 2026, 20:00 | 921 | no change |
| 6 Aug 2026, 19:48 | 921 | first reading |
20 posts held, back to 5 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 1 pageof 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.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 20 (5 August 2026 – 6 August 2026) |
| Views total | 53 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 19:48 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.
#国内资讯：广东打掉特大虚假助贷诈骗团伙，106人落网 8月3日，广东警方公布一起特大虚假助贷诈骗案。近期，广东省公安厅组织梅州警方分批收网，打掉一个由线上引流、线下助贷公司和话务端组成的诈骗团伙，共抓获106名嫌疑人，涉案金额超过380万元。 该团伙冒充银行发送贷款信息，专门寻找重病人员、老年人、失业人员等急需用钱的群体，再把他们引到注册正规的线下助贷公司。 工作人员谎称有“内部贷款渠道”，可以帮助办理低息、大额贷款，并以“风险管理金”“资料费”等名义收钱。 部分受害者被收取贷款金额25%的费用。对于无法办理大额贷款的人，团伙仍会按照意向贷款金额的1%至2%收取资料费，随后再以审核未通过为由拒绝办理。 警方查明，这些公司并没有所谓的内部贷款渠道，也没有提供真实贷款服务。遇到受害者报警或维权时，团伙还会退还部分费用，试图把诈骗包装成普通贷款纠纷。目前，案件正在进一步侦办中
香港荃湾展开扫黄行动，13名内地女子涉违规逗留被捕 8月5日，荃湾警区联同相关部门，根据线报部署代号“岭马”的专项扫黄行动。执法人员突击巡查川龙街、兆和街等多处闹市街区，一举拘捕13名内地女子，年龄介于34至55岁。 经查，涉案人员均持双程证赴港，涉嫌违反逗留条件。目前13人已被警方扣留调查，案件后续将交由相关部门进一步跟进处理。
#国际新闻｜加沙举行集体葬礼 112具遗骸时隔近三年重见天日 今天，数千名巴勒斯坦民众在加沙市举行集体葬礼，共同送别112具从废墟中打捞出的遇难者遗骸。这些遗骸属于阿尔-哈萨因纳家族和阿布·沙里亚家族成员，在废墟下沉睡近三年后，终于得以安葬。 据巴勒斯坦方面介绍，这些遇难者是在2023年11月加沙市沙布拉区一栋住宅楼遭空袭时罹难。当时，大批来自当地贝都因部落的居民正在该建筑内避难，袭击造成重大人员伤亡。 巴勒斯坦当局表示，此次空袭共造成约308名部落成员死亡。目前，当地搜寻工作仍在持续，预计仍有约157人失踪，相关人员相信部分遇难者遗体仍被掩埋在废墟之下。 这场迟来近三年的集体葬礼，吸引了数千名民众前来送别，现场气氛沉重，家属与民众共同悼念逝者。
#迪拜南部修理厂起火引燃多辆卡车房车 周二晚间发生在Dubai South的火灾，起因是该区域一家修理厂发生的事故。火势从修理厂蔓延，引燃了附近停放的多辆卡车和房车。 消防队接报后迅速赶赴现场并将火扑灭。迪拜媒体办公室在声明中确认，事故未造成人员伤亡。目前，修理厂事故的具体原因以及财产损失情况尚未公布，更多细节有待后续披露。
#诈骗团伙在哈萨克被抓获 近日韩国政府与哈萨克斯坦执法部门联手行动，成功抓获14名以哈萨克斯坦为基地活动的韩国籍诈骗团伙成员。这些嫌疑人已被押送回韩国并遭羁押。这是韩国政府首次直接在中亚地区捣毁韩国籍诈骗组织。 这些嫌疑人大多在20岁至30岁之间。他们在海外建立呼叫中心，假冒韩国金融监管机构和检察机关，以“涉嫌犯罪”为由诈骗受害者。团伙还使用所谓的“自我监禁”策略，诱骗受害者因恐惧而自我隔离在旅馆等地，断绝与外界联系。 接着，他们指示受害者将资金转入指定账户，以此骗取钱财。目前已确认的受害者有16人，涉案金额高达6亿韩元。有关部门认为，实际损失可能高达数十亿韩元，正在继续调查是否还有更多受害者和其他犯罪行为。 该团伙最初在柬埔寨活动，随着当地打击力度加大，他们经越南于今年4月将据点转移至哈萨克斯坦。韩国国家情报院启动情报合作，寻求哈萨克斯坦的协助，韩国法务部也迅速启动刑事司法程序。
#日本新闻：8月5日9时22分，北海道JR千茂线松川道场一处无栏杆、无警示信号灯的4型平交道发生事故，钏路开往网走的列车与卡车相撞。 事故中，列车16名乘客及卡车男司机均未受伤，卡车受冲击后驶离道口。值得关注的是，该路段同类简易道口上月28日刚发生轻型车辆与火车相撞的意外。 受此影响，千茂线网走至知床斜里段临时停运，两班列车取消。目前警方已约谈卡车司机，正彻查事故具体缘由，后续将根据调查结果采取措施，避免类似安全事件再次发生。
#日本新闻快讯：5日下午3时许，日本福井县敦贺市一商场多层停车场发生坠车事故。 77岁男子驾车下坡时失控，撞破三楼防护墙后坠落地面，车辆翻覆损毁严重。同车76岁妻子髋骨骨折重伤，司机送医初期尚有意识，因腹部多处重伤现已昏迷，情况危急。 事发时伴随巨响与尘土飞扬，现场状况惊险。目前警方正就事故诱因展开彻查，包括车辆状况、操作失误等可能性，相关细节待进一步公布。 此次事故引发当地对高龄驾驶者安全及停车场设施防护的关注。
未在越南犯案卻遭拘捕 台越司法合作機制是否存在？官方應公開說明 近日，多名遭台灣司法機關通緝的人士，在未涉越南境內犯罪的情況下，遭越南公安拘捕並限制對外聯繫，引發外界高度關注。 由於越南與台灣並無正式外交關係，本案也因此引發一連串值得社會關注的疑問。 當事人的程序權利是否獲得充分保障？ 相關主管機關是否願意向社會說明本案的法律依據及決策過程？ 本案不僅涉及個案處理，更牽涉跨境司法合作的透明度、公權力的行使，以及程序正義等重要公共議題。 社會期待相關主管機關正面回應外界疑問，以公開、透明的方式說明本案的法律依據與程序，讓事實接受社會檢驗。
#柬埔寨资讯：西港LION BOXING拳击俱乐部遭突袭，多名人员被拘留调查 8月4日，柬埔寨西哈努克市发生一起执法行动。当天上午，警方突袭位于当地的 “LION BOXING”拳击俱乐部，并逮捕数名涉嫌涉及DU品犯罪的人员。 随后，在一起持械抢劫案件调查过程中，执法部门再次对该场所展开行动。据初步消息，28月4日下午，警方在西哈努克市第四分区（Sangkat 4）采取进一步措施，拘留包括一名女性在内的4名相关人员，以便进行讯问及后续法律程序。 行动结束后，该场所被有关部门贴上封条，暂时关闭接受调查。消息人士透露，目前警方正在扩大调查范围，进一步核实是否还有其他涉案人员，以及该地点是否涉及更多违法活动。
柬埔寨严打新型诈骗套路 团伙诱骗泰国返乡劳工作案 柬埔寨执法部门正全力排查、严查并打击一类新型犯罪模式：不法团伙专门诱骗从泰国归国的柬籍劳工，吸纳其参与网络诈骗活动。此前当地已捣毁多处大型诈骗窝点，并持续向社会发布警示，提醒民众提高反诈意识。 柬埔寨内政部官员表示，这是犯罪分子迭代后的新型作案手法。随着官方持续清剿大型诈骗据点，不法分子为规避打击，纷纷分散藏匿于社区、民宅、山野及稻田等隐蔽区域。团伙依托无线网络，甚至利用车辆实施移动式网络诈骗，持续对接境内外犯罪链条。 官方坦言，人口贩运犯罪并未彻底肃清，犯罪手段已和网络诈骗深度结合、花样翻新。当局再次呼吁民众及家属谨慎甄别网络信息，切勿轻信陌生诱导、参与非法活动，遇可疑线索及时上报，避免沦为犯罪受害者。
吉隆坡Setapak住宅区突击行动，警方接报展开检查，现场多人被带走调查 2026年8月5日凌晨马来西亚吉隆坡 Setapak Danau C区 昨晚发生突击检查行动（Ops），执法人员进入当地部分住宅及场所展开检查。 据了解，警方此前接获民众举报，随后展开行动。由于该区域平时有较多中国籍人士活动，外界关注此次行动是否涉及网络诈骗（Online Scam）等违法活动。 现场消息称，有人员被执法人员带走进行检查，但目前具体被捕人数、涉及人员身份以及行动原因尚未有官方公布。 警方后续调查结果，将进一步确认此次行动详情。
#马来西亚资讯：柔佛河中惊现被捆绑浮尸 39岁华裔商人遭弃尸河道 3名嫌疑人被捕 援引马媒报道：8月3日12时30分，柔佛州峇株巴辖巴力拉惹镇，当地渔民在丹绒森宝隆河发现河面上有一团不明漂浮物，远看无法辨识具体物体，起初误以为是动物尸体，靠近查看后才确认是一具男性浮尸，随即向警方报案。 接报后，当地警方迅速赶赴现场，开展现场勘验、区域封锁等处置工作。随着调查推进，柔佛州副警察总长胡传发对外通报了该案初步详情：遇难者遗体被渔网层层包裹，手脚遭胶带捆绑，躯体多处存在伤痕。 7月29日，遇难者的妻子曾前往新山慕蒂亚拉里尼警局报案，报称丈夫失踪，该案彼时按失踪人口案件处理。此次浮尸事件发生后，家属到场，结合遗体的衣着及随身物品进行辨认，确认死者正是此前失踪的男子。据悉，遇难者是当地一名39岁华裔商人。 案件侦办过程中，警方锁定3名年龄介于26至40岁的本地男子，并将其全部抓获归案。经查，三名嫌疑人当中有两人存有犯罪及吸Du前科，…
Showing the 12 most recent of 20 posts we hold for @DB_622. 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.
Citation-graph rank — 268,652 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 31 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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 6 August 2026 — this entry's latest reading, not the date you are reading this.
“迪拜新闻 🪻” (@DB_622), 921 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/DB_622.
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.