罗伯特·帕丁森将饰演下一任詹姆斯·邦德 😱
😍7💘2❤🔥1

Channel
@junmang
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Cite this entry
17,806subscribers
+367 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001478182074 |
|---|---|
| Type | Channel |
| Username | @junmang |
| Description | 大多数时候只放本频道感兴趣的东西,转载新闻不代表频道对内容的完全赞同。 没有任何其他平台账号,Telegram 相似频道均不是本频道运营。 撕逼谩骂、极端言论将会被删除或封禁。 |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 63 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/junmang |
International 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 37% 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 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 |
|---|---|---|---|
| @junmang/22138 · this entry3 Nov 2026, 23:00 UTC | @qiwen99/825814 Nov 2026, 08:01 UTC | 1.00 | 9.0 hours |
| @junmang/22156 · this entry4 Nov 2026, 06:20 UTC | @qiwen99/825904 Nov 2026, 08:03 UTC | 1.00 | 1.7 hours |
| @junmang/22168 · this entry5 Nov 2026, 00:39 UTC | @qiwen99/8280110 Nov 2026, 19:55 UTC | 1.00 | 6 days |
| @junmang/22177 · this entry5 Nov 2026, 05:26 UTC | @qiwen99/8282210 Nov 2026, 20:14 UTC | 1.00 | 6 days |
| @junmang/22186 · this entry5 Nov 2026, 23:30 UTC | @qiwen99/8298311 Nov 2026, 19:10 UTC | 1.00 | 6 days |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @qiwen99 | 5 (5/5 hand-verifiable sample passed) | 1.00 | 6 days | 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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 120 comparable posts for this entry, running 5 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.
Recorded under the key 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Nov 2026, 00:21 | 17,806 | +18 |
| 12 Nov 2026, 13:58 | 17,788 | +15 |
| 10 Nov 2026, 13:09 | 17,773 | +1 |
| 9 Nov 2026, 00:56 | 17,772 | -3 |
| 7 Nov 2026, 17:47 | 17,775 | -2 |
| 6 Nov 2026, 17:38 | 17,777 | -2 |
| 5 Nov 2026, 19:20 | 17,779 | +6 |
| 4 Nov 2026, 21:05 | 17,773 | +7 |
| 3 Nov 2026, 18:38 | 17,766 | +1 |
| 2 Nov 2026, 15:27 | 17,765 | +2 |
| 1 Nov 2026, 17:41 | 17,763 | -1 |
| 31 Oct 2026, 20:56 | 17,764 | -11 |
| 30 Oct 2026, 20:40 | 17,775 | +4 |
| 29 Oct 2026, 21:28 | 17,771 | +7 |
| 29 Oct 2026, 00:17 | 17,764 | +6 |
| 27 Oct 2026, 23:50 | 17,758 | +5 |
| 27 Oct 2026, 02:10 | 17,753 | +4 |
| 26 Oct 2026, 02:58 | 17,749 | +3 |
| 25 Oct 2026, 04:40 | 17,746 | +11 |
| 24 Oct 2026, 03:56 | 17,735 | first reading |
276 posts held, back to 4 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 83 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 137 of 138 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 276 (4 August 2026 – 16 November 2026) |
| Views total | 160,207 |
| Reactions total | 4,013 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Nov 2026, 17:28 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 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.
Measured directly from 80 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.
11,138 reactions across 273 posts, in 54 distinct kinds. The most used accounts for 20.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 2,229 | 20.0% | |
| 🤣 | 1,568 | 14.1% | |
| 🤡 | 855 | 7.68% | |
| 🌚 | 848 | 7.61% | |
| 👍 | 742 | 6.66% | |
| 🫡 | 607 | 5.45% | |
| 🥰 | 604 | 5.42% | |
| 😍 | 480 | 4.31% | |
| 🙏 | 460 | 4.13% | |
| 😭 | 286 | 2.57% | |
| 🔥 | 246 | 2.21% | |
| 🕊 | 205 | 1.84% | |
| 🤮 | 195 | 1.75% | |
| 🎉 | 174 | 1.56% | |
| ✍ | 169 | 1.52% | |
| 👏 | 167 | 1.50% | |
| 🤓 | 120 | 1.08% | |
| 😇 | 98 | 0.88% | |
| 🤯 | 92 | 0.826% | |
| 😨 | 82 | 0.736% | |
| 34 further kinds | 911 | 8.18% |
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 273 of the 276 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 11,138 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 276 most recent posts we hold, published 4 August 2026 to 16 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @junmang. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 276 most recent posts we hold for this entry, published 4 August 2026 to 16 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Telegram’s own ‘edited’ marker: 25 of 138 posts held from the last 30 days (18.1%) 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).
罗伯特·帕丁森将饰演下一任詹姆斯·邦德 😱
😍7💘2❤🔥1
老乡拍的本届珠海航展室内陆军外贸车辆展位,之前的 VT-4B 正脸,以及猛三底盘四面阵雷达车,阵面可升降
😁9🥰5👍2
😀😀😀
🤣43😎5👏3😁1
特朗普此次访华行程 11 月 18 日: 特朗普离开菲律宾马尼拉,启程前往中国深圳。 11 月 19 日: 上午 9:30 深圳国际交流中心 - 特朗普参加 APEC 领导人合影仪式 上午 9:45 深圳国际交流中心 - 特朗普参加 APEC 领导人全体会议 下午 12:45 深圳麒麟山庄 - 特朗普与习近平举行双边会晤 下午 14:30 深圳麒麟山庄 - 特朗普、习近平、普京举行三方会晤
🤯20👍4🤷♂3👻1
美国太空军宣布将于北京时间 11 月 18 日下午 3 点 01 分至晚上 9 点 01 分之间试射一枚”民兵-III“洲际弹道导弹,其称本次试射在数年前就已排定。
🤷♂23😁10
美国联合发射联盟(ULA)的“火神半人马座”(Vulcan Centaur)火箭于北京时间今日凌晨(美国东部时间 11 月 15 日中午)发射失败,起飞约 10 分钟后,火箭出现严重异常,未能将载荷送入预定轨道,星箭俱毁,所搭载的 40 颗 Amazon Leo 低轨宽带互联网卫星全部损失。 这也是 ULA 自 2006 年成立以来,20 年间遭遇的首次任务彻底失败,亚马逊共向 ULA 采购了 38 次“火神”火箭发射服务,本次是该合同的首次发射。 据路透社援引消息人士报道,蓝色起源正与联合发射联盟合作调查此次事件,故障似乎发生在“火神”第二级与第一级助推器分离之后,第二级负责搭载亚马逊卫星,第一级助推器则由蓝色起源 BE-4 发动机提供动力。
🌚17🔥4
外交部发言人 11 月 16 日宣布:11 月 19 日,国家主席习近平将同俄罗斯总统普京、美国总统特朗普在深圳举行中俄美元首会晤。
✍35🥰11
FT:据多位知情人士透露,黄仁勋正考虑重返英伟达担任首席执行官,他在硅谷的盟友也正在向该公司董事会施压,要求恢复其职务。 黄仁勋的一位盟友向《金融时报》透露,他们正在组建一个由硅谷高管组成的“作战室”,以游说让这位前英伟达掌门人回归,并将试图争取白宫的支持。 周末期间,特斯拉及 SpaceX 首席执行官埃隆·马斯克与知名游戏公司 Epic Games 首席执行官蒂姆·斯威尼等高管均支持了一封公开信,要求英伟达董事会“让黄仁勋回来”(Bring Jensen Back)。 复职的努力可能会遭到华盛顿关键政策制定者的抵制,美国财政部长斯科特·贝森特周日呼吁,在黄仁勋离职后,英伟达领导层应进行“彻底改组”。
😁37😭10🤨4
印度快报:印度空军军官用作战计划换取裸照。 一名印度空军中校于五个月前被捕,并依据《官方保密法》相关条款被立案。据指控,他向一名疑似巴基斯坦情报特工提供了机密作战信息,包括作战计划文件、无人机能力、军事部署位置、一线作战飞机的动向以及敏感设施的坐标。 据警方起诉书,这名军官在收到疑似巴基斯坦特工发来的一张裸照后,上传了一页“秘密作战计划”,甚至表示,每收到一张裸照,他就提供一页新的作战计划。起诉书称,该军官泄露了一支秘密无人机部队的兵力与组织结构、无人机试验的细节、该武器系统的续航能力及其目标锁定机制,还泄露了有关战斗机在列城部署、以及在苏拉特格尔的马哈詹野战靶场举行的一次军事演习的信息。 这名疑似特工发送了恶意软件应用程序,可获取存储在该军官设备上的敏感信息,以及他与其指挥链之间的通信内容,该空军中校麾下部队中五名下属的通信设备上也被安装了某些特定的恶意软件。 这名空军中校自今年 1 月 12 日至 4 月 1 日期间…
🤣51🥴4🤪2😁2
美国官员告诉 Axios,美国海军“罗斯福”号(CVN-71)已经抵达美国中央司令部责任区。 目前中东已经部署有三艘美国航母,另外两艘为“华盛顿”号(CVN-73)和“布什”号(CVN-77)。
😁12
当地时间 11 月 15 日上午,英国皇家海军“前卫”级战略核潜艇“复仇”号(HMS Vengeance)结束了创纪录的七个月部署,返回位于苏格兰的法斯兰海军基地,“复仇”号于 4 月 12 日开始此次部署,在水下度过 217 天后于周日返航,此次水下巡航超越了此前由“前卫”号(HMS Vanguard)保持的 205 天纪录。 潜艇长时间部署后的生锈、海洋生物附着和消声瓦脱落。
😨23🌚3🤪2👻1
今年九月底在山东青岛开馆的张超烈士纪念馆,馆内陈列有 117 号 歼-15 电传故障失事后的真机照片
🫡82🤡1
Showing the 12 most recent of 276 posts we hold for @junmang. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
@junmang edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 2 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.
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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“一个军盲” (@junmang), 17,806 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/junmang.
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.