庄行镇野外打野战,女的被毒蛇咬了屁股然后去医院 估计因为是毒蛇报了奉贤卫健委!奉贤卫健委就爆出来了! PS、女方的老公报警了 #吃瓜
❤1

Channel
@luanlunsdjg
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry
29,625subscribers
-6,636 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002332727280 |
|---|---|
| Type | Channel |
| Username | @luanlunsdjg |
| Description | #缅甸 #柬埔寨 #菲律宾 #迪拜 #东南亚 #老挝 #泰国 #马来西亚 #印度 #全球新闻 #曝光 #吃瓜 #黑料 商务合作 @wanzaiyingshibot |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 67 |
| Confirmed unchanged | 1 time, most recently 14 November 2026 |
| On Telegram | t.me/luanlunsdjg |
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 63% 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. This entry also forms a group of 2 channels linked by matching posts. 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 |
|---|---|---|---|
| @luanlunsdjg/8403 · this entry26 Sept 2026, 05:34 UTC | @hhlgx/3636226 Sept 2026, 05:35 UTC | 1.00 | under a minute |
| @luanlunsdjg/8712 · this entry15 Oct 2026, 03:37 UTC | @hhlgx/3694115 Oct 2026, 03:37 UTC | 1.00 | under a minute |
| @luanlunsdjg/8730 · this entry15 Oct 2026, 07:44 UTC | @hhlgx/3696315 Oct 2026, 07:44 UTC | 1.00 | under a minute |
| @luanlunsdjg/9125 · this entry3 Nov 2026, 01:32 UTC | @hhlgx/375083 Nov 2026, 01:32 UTC | 1.00 | under a minute |
| @luanlunsdjg/9137 · this entry4 Nov 2026, 00:27 UTC | @hhlgx/375314 Nov 2026, 00:27 UTC | 1.00 | under a minute |
| @luanlunsdjg/9142 · this entry5 Nov 2026, 04:42 UTC | @hhlgx/375465 Nov 2026, 04:42 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @hhlgx | 110 (7/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (104–6) |
| @fenhongshequ | 6 (6/6 hand-verifiable sample passed) | 1.00 | under a minute | this entry (4–2) |
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. 8 of the 8 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 184 comparable posts for this entry, running 7 August 2026 to 16 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.
Of the group of 2 channels, the one whose matching posts we hold earliest is @luanlunsdjg — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 17 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.
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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 |
|---|---|---|
| 14 Nov 2026, 18:10 | 29,625 | -1,722 |
| 11 Nov 2026, 15:00 | 31,347 | -533 |
| 9 Nov 2026, 22:48 | 31,880 | -408 |
| 8 Nov 2026, 13:36 | 32,288 | -515 |
| 7 Nov 2026, 07:19 | 32,803 | -489 |
| 6 Nov 2026, 08:59 | 33,292 | -182 |
| 5 Nov 2026, 11:56 | 33,474 | -263 |
| 4 Nov 2026, 13:15 | 33,737 | -339 |
| 3 Nov 2026, 15:38 | 34,076 | -25 |
| 2 Nov 2026, 16:46 | 34,101 | -147 |
| 1 Nov 2026, 15:55 | 34,248 | -516 |
| 31 Oct 2026, 13:06 | 34,764 | -513 |
| 30 Oct 2026, 14:17 | 35,277 | -595 |
| 29 Oct 2026, 11:07 | 35,872 | -688 |
| 28 Oct 2026, 09:09 | 36,560 | -425 |
| 27 Oct 2026, 11:46 | 36,985 | -280 |
| 26 Oct 2026, 11:58 | 37,265 | -402 |
| 25 Oct 2026, 15:27 | 37,667 | -140 |
| 24 Oct 2026, 18:59 | 37,807 | -378 |
| 23 Oct 2026, 21:59 | 38,185 | first reading |
473 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 214 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 60 of 170 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 17 November 2026 |
|---|---|
| Posts held | 473 (6 August 2026 – 17 November 2026) |
| Views total | 124,915 |
| Reactions total | 42 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 08:34 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 17 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 193 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.
144 reactions across 106 posts, in 6 distinct kinds. The most used accounts for 75.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 108 | 75.0% | |
| 👍 | 27 | 18.8% | |
| 😁 | 5 | 3.47% | |
| 🔥 | 2 | 1.39% | |
| 🎉 | 1 | 0.694% | |
| 😢 | 1 | 0.694% |
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 157 of the 473 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 144 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 473 most recent posts we hold, published 6 August 2026 to 17 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: 1 of 170 posts held from the last 30 days (0.588%) 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).
庄行镇野外打野战,女的被毒蛇咬了屁股然后去医院 估计因为是毒蛇报了奉贤卫健委!奉贤卫健委就爆出来了! PS、女方的老公报警了 #吃瓜
❤1
咸鱼是最大的暗网!!!中国人的全球通!!!
黄果短剧突然开源,背后的原因居然这么他妈狗血! 𝕏上一个叫「怒愤离职的黄果码农」的账号,是开源黄果短剧的大佬,他爆料的原因是领导剽窃他的成果,并且克扣工资,一气之下把黄果开源了! 按照这哥们的详细爆料: 自己辛辛苦苦写代码、优化AI短剧卡顿问题,结果领导转头把他的方案交给刚招进来的嫡系。 项目火了,嫡系升组长,自己连晋升机会都没捞着。 更牛逼的是,后来版本出了事故,公司把锅甩给他,还拿他在技术群里吐槽的一句话,当成公开挑战负责人的证据。 功劳是领导的,奖金是嫡系的,出了事倒成了他的! 最后连续两个月绩效D,离职时还被要求确认代码归属、删除相关资料。 这哥们一怒之下,整理开发记录,把自己独立写的第三方客户端扔上GitHub免费开源! 公司也坐不住了,赶紧发声明,说根本没有核心代码泄露,所谓职场黑幕纯属个人编排。 结果这哥们又晒出工资条:税前59800,到手45100,项目奖金直接归零! 还在𝕏上怒喷领导,称对…
事实核查:卢比奥是故意搞掉黄仁勋的幕后黑手? 11月13日,《华盛顿邮报》发表了一篇颇有分量的重磅调查,认为美国国务卿卢比奥的一份情报备忘录,是引发黄仁勋下台风波的关键。 先看看三位作者的背景: 第一位是伊恩·邓肯(Ian Duncan),《华盛顿邮报》科技政策记者,长期报道白宫、国会与大型科技企业的关系。毕业于牛津大学,后在纽约大学攻读新闻学与国际关系,曾在《巴尔的摩太阳报》工作,参与过获得普利策奖的调查报道团队。 第二位是扎克·多夫曼(Zach Dorfman),长期调查美国情报机构、秘密行动和中美间谍活动,曾在《外交政策》《大西洋月刊》等媒体发表调查报道。他调查过中国情报网络与美国政治人物的关系,熟悉美国情报界,也曾获得杰拉尔德·福特新闻报道奖。 第三位是沃伦·斯特罗贝尔(Warren P. Strobel),拥有35年以上外交和国家安全报道经验,曾任《华尔街日报》资深记者,跟随七任美国国务卿出访,足迹遍及近百个国家。他曾…
Photo, posted without a caption
黑人抢劫莫桑比克的中国超市。 万幸没人伤亡!
媒体札记:黄仁勋下台仅三天,就宣告杀回英伟达?硅谷盟友组建“战情室”,但华盛顿有人反对 黄仁勋辞职才三天,复出的消息就传出来,整理媒体的报道顺序: 11月13日,《金融时报》率先报道,英伟达董事会正在接触Arm首席执行官Rene Haas等外部接班人选。 14日,马斯克公开表示,英伟达失去黄仁勋,可能影响重要商业交易。硅谷开始出现挽留他的声音。 15日,《金融时报》又独家披露,黄仁勋本人已与亲信讨论重返CEO岗位的可能性。他的硅谷盟友甚至组建了“战情室”,准备游说英伟达董事会,并争取白宫支持。 同一天,美国财政部长贝森特却公开要求英伟达从外部寻找新CEO,彻底调整领导层。路透社随后跟进报道,雅虎财经等媒体也陆续转载。 法新社当天还报道,要求黄仁勋复职的公开信已有超过15.8万人签名,包括马斯克、Epic Games创始人Tim Sweeney等科技界人士。 有意思的是,黄仁勋因为婚外情和间谍疑云辞职,川普仍称他是“传奇人物”;但…
网传360集团市场部副总裁卜思南被带走调查 今天下午有国内自媒体发文称,有消息人士透露,北京某知名互联网大厂的市场一号位(市场部负责人,也是公司副总裁)近期被带走调查。 市场传言称该人是360公司的集团副总裁、市场部负责人卜思南。卜思南于今年年中升任副总裁,主管市场部,向周鸿祎汇报。
王忠林_县委书记要响当当,硬邦邦,嗷嗷叫。 原来是这个意思啊😁
上海瑞和苑一家人昨晚被灭门了,外卖送到,13楼客户拿到后当面投诉外卖员,然后外卖员当场就把一家人干了。最小的才2岁,把家里老人没放过,最后外卖员从13楼跳下去了。 墙国高压锅,可能一点火星就能酿成一场惨剧。
出轨了五年都不愿意跟她老公离婚,还要以死相逼,这个女人也太炸裂了吧谁要娶到这种女的,仇人看了都释怀了 #吃瓜 #抽象
两个月前,中美对标就爆料武汉电视台主持人胡某与3个武汉市委常委有染,沒想到还包括王忠林书记
Showing the 12 most recent of 473 posts we hold for @luanlunsdjg. 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.
We recorded 39 posts on @luanlunsdjg 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.
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 14 November 2026 — this entry's latest reading, not the date you are reading this.
“吃瓜曝光|时事热点” (@luanlunsdjg), 29,625 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/luanlunsdjg.
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.