明天需要更新什么打在下方🤓
👍37🤔2
Signed 墨风

Channel
@qh7786
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts recorded as deleted · Citations · Cite this entry
27,375subscribers
-1,274 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002325429919 |
|---|---|
| Type | Channel |
| Username | @qh7786 |
| Description | 频道拥有者:情话 情话本人→ @qh9528bot 情话本人(广告/合作)联系 @qh9528bot 情话改文件交流群 @qhnb5528 情话文件的初心是希望每个学生党都能玩上稳定的公益文件 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 60 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/qh7786 |
Gaming — 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 91% 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. 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 |
|---|---|---|---|
| @qh8876/240911 Aug 2026, 11:45 UTC | @qh7786/6563 · this entry11 Aug 2026, 11:45 UTC | 1.00 | under a minute |
| @qh8876/243415 Aug 2026, 10:43 UTC | @qh7786/6588 · this entry15 Aug 2026, 10:43 UTC | 1.00 | under a minute |
| @qh8876/244116 Aug 2026, 12:55 UTC | @qh7786/6595 · this entry16 Aug 2026, 12:55 UTC | 1.00 | under a minute |
| @qh7786/6609 · this entry19 Aug 2026, 03:34 UTC | @qh8876/245519 Aug 2026, 03:34 UTC | 1.00 | under a minute |
| @qh7786/6633 · this entry22 Aug 2026, 13:13 UTC | @qh8876/247922 Aug 2026, 13:13 UTC | 1.00 | under a minute |
| @qh8876/248924 Aug 2026, 07:08 UTC | @qh7786/6643 · this entry24 Aug 2026, 07:08 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @qh8876 | 133 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (131–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. 2 of the 2 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 281 comparable posts for this entry, running 10 August 2026 to 17 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 @qh7786 — 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 |
|---|---|---|
| 16 Nov 2026, 02:45 | 27,375 | -77 |
| 12 Nov 2026, 13:55 | 27,452 | -40 |
| 10 Nov 2026, 07:41 | 27,492 | -32 |
| 8 Nov 2026, 22:57 | 27,524 | +36 |
| 7 Nov 2026, 16:17 | 27,488 | +2 |
| 6 Nov 2026, 13:46 | 27,486 | -17 |
| 5 Nov 2026, 15:18 | 27,503 | -19 |
| 4 Nov 2026, 14:37 | 27,522 | -23 |
| 3 Nov 2026, 13:26 | 27,545 | -40 |
| 2 Nov 2026, 16:26 | 27,585 | -6 |
| 1 Nov 2026, 18:28 | 27,591 | -23 |
| 31 Oct 2026, 20:37 | 27,614 | -39 |
| 30 Oct 2026, 22:36 | 27,653 | -31 |
| 29 Oct 2026, 23:47 | 27,684 | -26 |
| 28 Oct 2026, 23:31 | 27,710 | -24 |
| 27 Oct 2026, 22:10 | 27,734 | -15 |
| 27 Oct 2026, 01:08 | 27,749 | -32 |
| 26 Oct 2026, 01:19 | 27,781 | +6 |
| 25 Oct 2026, 01:40 | 27,775 | -16 |
| 24 Oct 2026, 01:51 | 27,791 | first reading |
514 posts held, back to 9 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 154 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.
| Window | Rolling 30 days · latest post in window 17 November 2026 |
|---|---|
| Posts held | 514 (9 August 2026 – 17 November 2026) |
| Views total | 107,556 |
| Reactions total | 6,187 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 15:15 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 19 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.
13,054 reactions across 512 posts, in 17 distinct kinds. The most used accounts for 94.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 12,285 | 94.1% | |
| ❤ | 429 | 3.29% | |
| 😍 | 99 | 0.758% | |
| 🤔 | 76 | 0.582% | |
| 🍌 | 41 | 0.314% | |
| 🕊 | 25 | 0.192% | |
| 🤓 | 20 | 0.153% | |
| 🥰 | 17 | 0.13% | |
| 😁 | 15 | 0.115% | |
| 💯 | 10 | 0.077% | |
| 🎉 | 8 | 0.061% | |
| 👏 | 8 | 0.061% | |
| 👀 | 5 | 0.038% | |
| 🔥 | 5 | 0.038% | |
| 🤨 | 5 | 0.038% | |
| 🤩 | 5 | 0.038% | |
| 😇 | 1 | 0.008% |
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 512 of the 514 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 13,054 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 514 most recent posts we hold, published 9 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @qh7786. 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 514 most recent posts we hold for this entry, published 9 August 2026 to 17 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: 2 of 166 posts held from the last 30 days (1.20%) 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).
明天需要更新什么打在下方🤓
👍37🤔2
Signed 墨风
情话自用v6 无后100% 防抖100% 十字架100% 强锁自瞄 快速切枪 撞火抢托连发 无跳弹 有效枪械 AUG UZI AK QBZ SKS SLR M416 狗砸 M249 M762 维克多 死噶 ACE 赤霄 M338 P18C MK47 M16A4 S12K S1897 ❤️使用方法: 公告导入功能 局内导入原版 ❤️高速网盘下载教程: 首先先保存文件 之后再把后缀改成.apk即可 点我跳转百度网盘高速下载 点我跳转UC网盘高速下载 🏘表情包越多 下一个更新越快
👍22
Signed 墨风
三角洲游戏v9 无后100% 防抖100% 十字架100% 人物强锁自瞄 平滑自瞄 人物绘制 物资绘制 地图除草 地图土地模型 人物白体 全皮肤美化 人物红白上色 头盔背包白体 所有游戏版本都已更新 文件里面自带文本教程 有效枪械 全部枪械 ❤️网盘高速下载方法: 首先先保存文件 之后把后缀改成.apk形式即可 点我跳转百度网盘高速下载 点我跳转UC网盘高速下载 ↑↑↑↑↑↑↑↑↑↑↑
👍25🤔3❤1
Signed 墨风
情话内透v3 11.17最新内透思路 人物掩体变色内透(双色) 全枪软锁(可以添加或者不加) 500米内地图全显 人物头部上色 人物头部发光 HDR画质发光 支持裸奔(全新思路) 支持全模式通用 百分百稳定且裸奔 修复所有特殊衣服不显示 ❤️使用方法: 桌面导入功能 局内导入原版 ❤️网盘高速下载方法: 首先先保存 之后后缀改成.apk形式即可 点我跳转百度网盘高速下载 点我跳转UC网盘高速下载 ↑↑↑↑↑↑↑↑ 🏘表情包越多 下一个更新越快
👍17🤔1
Signed 墨风
今天更新撞火抢托自动连发怎么样 你们想玩什么枪 还有更新三角洲文件 自带文本教程
👍10🤔1
Signed 墨风
🏘你们觉得双枪好还是三枪好 并且把你们认为这个版本好玩的枪打出来
👍43❤2
Signed 墨风
情话范围v3 11.16全新范围思路 0.45头部环绕范围 0.25全身小范围 人物红色头部内透 密钥内透:黄 侦察兵 灰 突击兵 青 特种兵 蓝 指挥官 全枪软锁(软锁神力) 软锁搭配范围稳定乱穿 全枪范围 支持裸奔 支持全模式(地铁或者经典) 蓝圈记得导入原版 ❤️使用方法: 公告导入功能 经典大厅删掉功能 点我跳转百度网盘高速下载 点我跳转UC网盘高速下载 ↑↑↑↑↑↑↑↑
👍23🤔4
Signed 墨风
暗区突围v2 无后100% 防抖100% 十字架100% 强锁自瞄 平滑自瞄 人物内透 人物头盔背包白体 游戏内部设置自调功能 有效枪械:支持全部枪械 点我跳转百度网盘高速下载 点我跳转UC网盘高速下载 ↑↑↑↑↑↑↑↑↑↑↑
👍24
Signed 墨风
情话自用v5 无后100% 防抖100% 十字架100% 强锁自瞄 快速切枪 无跳弹 有效枪械 AUG UZI AK QBZ M4 狗砸 M249 M762 ACE 赤霄 M338 P18C 维克多 死噶 SKS SLR ❤️使用方法: 公告导入功能 局内导入原版 ❤️高速网盘下载教程: 首先先保存文件 之后再把后缀改成.apk即可 点我跳转百度网盘高速下载 点我跳转UC网盘高速下载 🏘表情包越多 下一个更新越快
👍21❤4
Signed 墨风
今天更新暗区突围文件 到时候里面添加文本教程改法 你们自行观看就行
👍19
Signed 墨风
我去了 和平更新ACE跟赤霄的补丁了 学生党们你们有福了🤓
👍51🤔2❤1
Signed 墨风
密钥内透1.0 11.15最新思路 资源绘制 黄 侦察兵 灰 突击兵 青 特种兵 蓝 指挥官 此文件已经增加了稳定性 依旧可以做到裸奔 支持全模式 支持裸奔 ❤️高速网盘下载教程: 首先先保存文件 之后把后缀改成.apk即可 点我跳转百度网盘高速下载 点我跳转UC网盘高速下载 ↑↑↑↑↑↑↑↑ 🏘表情包越多更新得越快
👍44❤1🤔1
Signed 墨风
Showing the 12 most recent of 514 posts we hold for @qh7786. 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 1 post on @qh7786 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.
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 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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“情话改文件官方频道” (@qh7786), 27,375 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/qh7786.
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.