Telegram RegisterThe public register of Telegram
Telegram profile photo for 七天公告

Channel

七天公告

@qtdbbz

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

17,089subscribers

+689 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1003863596050
TypeChannel
Username@qtdbbz
Description七天主群 @qitianjituan 七天公群 @qtdb 七天公告 @qtdbbz 七天供需 @qt522 精品供需 @qt55 七天系统 @qtxtx 七天曝光 @qt00 七天娱乐 @qt33 七天球盘 @qt44 前台接待 @qt77 🌐招财七 @qt66 🌐招财八 @qt88 🌐担保交易员 @mofa 🌐担保交易员 @xiqi 🌐七天运营号 @chun 🌐反馈专员 @yan 一键关注七天集团:https://t.me/addlist/6lAQnIvApTU1MGFk
Created24 February 2026 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live12 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/qtdbbz

Topic

Marketing & affiliate — 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 32% 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.

Observations

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.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 2 other registered channels. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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.

Matching posts — open both and compare (4 of the pairs behind the counts below)
Posted firstThenOverlapGap
@qtdbbz/45 · this entry27 Aug 2026, 15:44 UTC@qt522/8703427 Aug 2026, 17:30 UTC1.001.8 hours
@qtdbbz/75 · this entry15 Oct 2026, 14:48 UTC@qt522/9882915 Oct 2026, 14:51 UTC1.004 minutes
@qtdbbz/82 · this entry8 Nov 2026, 08:38 UTC@qt522/1057938 Nov 2026, 16:11 UTC1.007.6 hours
@qtdbbz/82 · this entry8 Nov 2026, 08:38 UTC@xinqunfabu/13968 Nov 2026, 08:38 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@qt5226 (6/6 hand-verifiable sample passed)1.0055 minutesthis entry (6–0)
@xinqunfabu5 (5/5 hand-verifiable sample passed)1.004 minutesthis 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 39 comparable posts for this entry, running 24 February 2026 to 8 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 3 channels, the one whose matching posts we hold earliest is @qt522. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, 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.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with the channel listed below. 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.

1 more channel is in this same group but not listed individually here.

Growth

15,40925,00620,207.517,0897 August 202612 November 2026
64 measurements spanning 97 days, net +689. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 13,969–26,446 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
12 Nov 2026, 01:0817,089+163
10 Nov 2026, 00:5716,926+94
8 Nov 2026, 17:5016,832+161
7 Nov 2026, 10:0816,671+99
6 Nov 2026, 06:4016,572+77
5 Nov 2026, 03:0516,495+39
4 Nov 2026, 02:5516,456+61
3 Nov 2026, 01:5116,395+180
1 Nov 2026, 22:4416,215+114
1 Nov 2026, 01:1816,101+113
30 Oct 2026, 21:5115,988+150
29 Oct 2026, 21:3515,838+137
28 Oct 2026, 21:3815,701+136
27 Oct 2026, 22:3615,565+103
26 Oct 2026, 21:3915,462+53
25 Oct 2026, 18:5015,409-2,177
24 Oct 2026, 19:0717,586-7,295
23 Oct 2026, 18:0024,881+86
22 Oct 2026, 21:1024,795+72
21 Oct 2026, 21:0824,723first reading

Engagement

44 posts held, back to 24 February 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 102 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
81.7%
avg views ÷ 17,089 subscribers
Avg views / post
14,000
8 posts measured
Reaction rate
0.163%
reactions ÷ views · ER floor
Posts in window
8
of 44 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 November 2026
Posts held44 (24 February 2026 – 8 November 2026)
Views total111,670
Reactions total182
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Nov 2026, 05:09 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.

What this channel posts

Photos
29
Videos
6
Links
9

Lifetime counters from Telegram’s own channel header, read 12 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
6m 39s
Average length
1m 07s

Measured directly from 6 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.

Reaction mix

2,048 reactions across 37 posts, in 27 distinct kinds. The most used accounts for 15.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤31515.4%
❤‍🔥1838.94%
👍1517.37%
💔1045.08%
🔥1004.88%
💩994.83%
😡894.35%
🖕884.30%
😈884.30%
🥱854.15%
💯844.10%
🤩834.05%
🤮834.05%
🍌793.86%
🎉793.86%
🥰783.81%
👎773.76%
😢773.76%
😍552.69%
🤬241.17%
7 further kinds271.32%

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 39 of the 44 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 2,048 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 44 most recent posts we hold, published 24 February 2026 to 8 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.

Recent posts

Telegram’s own ‘edited’ marker: 4 of 8 posts held from the last 30 days (50.0%) 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).

8 Nov 2026, 08:38 UTC≈14,500 views4 reactionsread 12 November 2026
Photo

😎七天担保|谨防假客服、假地址 😎 骗子常在广告群谈合作后拉群,冒充七天工作人员或机器人,发送相似地址,以“我先转、你再转”“删除地址里的汉字”等话术骗取上押! 上押前,务必做好三步: ① 验人: 点头像,核对账号的真实用户名+888号码,别只看头像、昵称、简介里的 @。 ② 验证: 认准真实用户名为 @qt77 的机器人,发送 验证 @用户名。群是真群,但是你的合作方不一定是真的,有可能冒充担保,有需要的话可与官方人员确认! ③ 验址: 完整核对地址前、中、后及大小写,粘贴到钱包后再核一次。对方先转账,也不能证明地址安全! ━━━━━━━━━━━━━━ ✅ 官方人员名单 投诉建议:@yang 888 0007 7077 负责人一组:@qt66 888 0770 7070|备用 @qtdb789 负责人二组:@qt88 888 0770 0707|备用 @qtdb567 魔法:@mofa 888 0112 2330 稀奇:@xi…

❤2👍2

19 Oct 2026, 07:50 UTC≈12,200 views7 reactionsread 12 November 2026

😎【七天担保】官方投诉与建议反馈通道 为进一步完善平台服务、提升问题处理效率,畅通商家与用户的意见反馈渠道,七天担保现设立官方投诉与建议反馈通道。 一、投诉与建议受理范围 1. 客服沟通与服务问题 2. 公群运营与服务问题 3. 交易纠纷与仲裁处理问题 4. 专群运营与商家合作问题 5. 账户安全与官方信息核实问题 6. 违规行为与社群管理问题 7. 其他意见与建议 二、官方投诉反馈联系方式 😀反馈专员:阳 😎电话号码:+888 0007 7077 1️⃣官方账号:@yang 如您在合作过程中遇到相关问题,或对平台服务、运营管理及合作流程有任何意见与建议,均可通过以上官方渠道进行反馈。所有投诉与建议均将按照登记反馈、核实情况、跟进处理、结果反馈的流程推进。 😎感谢广大商家与用户对七天担保的信任与监督!

❤7

16 Oct 2026, 12:47 UTC≈24,700 views48 reactionsread 12 November 2026

😎 关于近期不实报道的澄清声明 针对近日网络传播的《七天担保平台资金遭冻结》等文章,内容存在未经核实的指控及片面解读,七天担保在此统一回应: ① 关于所谓“资金冻结、遭到制裁” 部分客户通过交易所转账时出现风控提示,被有心人借题发挥,渲染为平台资金遭冻结、受到制裁。交易所风控提示不等于链上资金被冻结,更不能作为平台遭制裁的证据! 请以实际链上记录及权威信息为准。 ② 关于平台资金安全及退押问题 📊 最新公布的24小时链上统计: ✅ 累计转出 4,961,726 USDT ✅ 实际对外转出 4,844,726 USDT ✅ 实际对外转账 2,421笔 以上为所统计地址的链上转出数据,并非平台全部资产证明。相关交易记录可供进一步核验。 ③ 关于网络舆论 我们尊重客观监督与合理质疑,但反对将未经核实的猜测包装成既定事实,更反对借交易所风控提示制造不必要的恐慌, 以官方发布公告为实:点击查阅 造谣可以毫无成本,但链上数据不会撒谎!…

❤22👍18👌4👎4

15 Oct 2026, 23:10 UTC≈14,900 views35 reactionsread 12 November 2026
Photo

📢 七天担保|24小时链上退押数据公示 🔥 造谣可以毫无成本,但链上数据不会撒谎! 面对昨日网络上的各种质疑与传言,七天担保从不打口水仗,用真实转账记录回应,用实际行动证明! 📊 最新24小时|USDT链上转出数据 主要退押地址: TPSBkNjfP9urQoe4vyw44uR2mxNnSi2hbK TLJKf1aWuDT8eHdT8SUUV93ExZ4u9ViSaB TTxTrPznVpKbNSkpS4UYYHHjLQiPnQufka TLE2zeqv5zB1e6GUrXvBRzLFMaYLKVuRrq 💰 累计转出 4,961,726 USDT ✅ 实际对外转账 2,421笔 🔗 统计涉及 8个TRON钱包地址 🔄 内部互转 3笔,共117,000 USDT 🏦 实际对外转出 4,844,726 USDT 24小时,累计转出496万U!实际对外转出488万U!所有堆积退押已全部完成,每一笔交易均可通过链上记录核…

❤20👍7🫡6🤝2

15 Oct 2026, 14:48 UTC≈9,060 views36 reactionsread 12 November 2026
Photo

📢 七天担保|退押进度及资金安排公告 ✅ 目前退押工作正在持续进行,所有申请按顺序核实、陆续处理,相关链上转账记录将持续公示。 请已申请退押的老板耐心等待,避免重复催单影响处理效率。 🙏 感谢各位老板的理解与支持,请理性看待网络信息,一切以官方公告及可核实记录为准。 还是三个字:稳嘟嘟! 退押地址: TLJKf1aWuDT8eHdT8SUUV93ExZ4u9ViSaB TQxVTUNfpiEE1kfjNtVUQpKE4JwGjMa3LW

👍18❤15😨3

15 Oct 2026, 12:55 UTC≈19,500 views26 reactionsread 12 November 2026
Photo

😎【七天担保·新增上押地址及变更公告】 尊敬的各位客户与合作伙伴: 为了更好地迎合市场需求,全面保障广大用户的资金安全,七天担保现对上押地址进行更换调整 😎全新官方上押地址将于 2026年10月17日 00:00 正式启用 【新增上押地址】 TFrApRxigkVTSLkV4ZZGReTQ48YaBNGT8B 【地址校验信息】 开头:TFrApRxi 结尾:YaBNGT8B 【原上押地址】 TQcxbMEVhYFSRKKGNdHv5dLAuqpgipSsWT ⚠️ 过渡与下架安排:原地址自新地址上线之日起保留 15 天过渡期,期满后全面下架并停止使用。 😎 安全提示: ① 新地址生效前请勿提前转入;上线后上押请务必认准官方新地址。 ② 请大家及时更新保存的地址记录,15天过渡期结束后原地址将不再接收任何上押资金。 😎 “担保,你可以永远相信七天!”

❤23👏3

15 Oct 2026, 11:14 UTC≈12,100 views23 reactionsread 12 November 2026
Photo

📢 七天担保|辟谣公告 ➕受网络不实传言影响,退押申请集中增加,导致处理排队。目前退押工作正按顺序陆续进行中,相关退押转账记录同步公示,请各位老板耐心等待。 ❗️不信谣、不传谣,一切以官方公告及实际链上转账记录为准! 担保,你可以永远相信七天! 🛡上押地址: TQcxbMEVhYFSRKKGNdHv5dLAuqpgipSsWT 🛡退押地址: 1⃣TAkWXtVKyzKWiunU4dZh7AWS3fpsTHxHUu 2⃣THevaS5YiF2UsrNShHejHDGc7JpSBFUESn 3⃣TLJKf1aWuDT8eHdT8SUUV93ExZ4u9ViSaB 4⃣TA9UR4GcfJ5BZxqhodCRV93XWHsmtDgg4W 5⃣TTxTrPznVpKbNSkpS4UYYHHjLQiPnQufka 6⃣TQxVTUNfpiEE1kfjNtVUQpKE4JwGjMa3LW

❤16👍7

12 Oct 2026, 15:59 UTC≈6,440 views3 reactionsread 12 November 2026
Photo

😎😎😎😎 公群报备以及自助供需升级 😎升级时间:2026.10.12 23:59 公群报备步骤 ① 发起报备(认准公群方管理,使用机器人 @qt77 验证公群证伪) 供需双方谈好交易内容后,联系公群方报备,公群方管理在公群发送【公群报备】。 ② 核对信息 管理员发起报备订单,双方仔细核对交易信息、金额及交涉回款地址。 ③ 确认报备 信息无误点击【确认】,有误点击【拒绝】并联系管理员重新报备。 ④ 报备成功 做单客人确认后,系统冻结相应担保额度,报备正式生效。 ⑤ 交易结束 交易完成后,双方点击【交易完成】,即可结束订单、解除担保额度占用。 ====================================================== 【禁止私下交易】 公群交易和沟通必须在公群内报备后进行,不允许引导客户私聊交易或者拖延申报纠纷,与客户交易,必须群内报备。如诱导客户私下交易押金不予退还! 【禁止超押】…

❤3

9 Oct 2026, 11:19 UTC≈6,100 views11 reactionsread 12 November 2026
Photo

📢 七天担保|年关将至·交易风险防范公告 🚨 临近年底,部分资金周转压力增大,合作方失联、拖欠结算、恶意跑路等风险有所增加。为保障供需双方资金安全,七天担保郑重提醒: ① 严格执行报备制度 所有公群合作必须通过官方机器人 @qt77 报备,严禁私下交易、口头报备,专群切勿绕过担保流程避免不必要的损失! ② 控制交易额度 切勿因长期合作、熟人介绍或历史信誉而放松警惕。大额交易建议分批进行,严禁超出实际担保额度。 ③ 账目核对 合作期间及时核对账目,避免长期压款、累计欠款,防止风险集中爆发。 ④ 警惕异常行为 如发现合作方突然加大量、频繁更换账户、拖延结算、拒绝对账或异常失联,请立即暂停交易并联系担保客服核实。 ⑤ 保留完整交易证据 交易规则、报备记录、转账凭证、聊天记录及结算明细务必妥善保存,以便发生纠纷时核实处理。 七天担保将持续加强风险排查及交易纠纷处理,提醒各位老板提高防范意识,严格遵守担保规则,共同维护安全、…

❤6💯3👍2

9 Oct 2026, 04:36 UTC≈4,720 views0 reactionsread 12 November 2026
Photo

😎😎😎 【七天担保|官方防骗警告】 请广大公群老板注意:七天担保平台不会以“报备”“报备费”“报备押金”等形式向用户收取任何费用。 ⚠️凡以“报备订单”“报备审核”“报备服务费”等名义要求转账、缴费、付款的,均属于非官方行为,请勿相信! ⚠️任何收费操作,请先通过官方渠道进行核实,未经官方确认,切勿向任何个人或陌生地址转账。 😎😎😎😎 请认准官方平台人员:@qt66 @qt88 @mofa @xiqi

3 Oct 2026, 04:41 UTC≈19,700 views3 reactionsread 8 November 2026
Video

【自助供需 — 用户操作说明】 😎😎😎😎😎😎😎😎😎😎 在担保 @qt77 私聊中使用「自助供需」功能。 1. 功能概述 1️⃣余额充值 ;用 USDT(TRC20)充值到个人账户 2️⃣购买套餐 ;用余额购买普通/精品供需次数 3️⃣发布供需 ;上传广告、选择投放时间参数并提交审核 4️⃣个人中心 ;查看余额、次数、充值/供需/账变记录 5️⃣供需说明 ;查看发布规则与收费标准 ⚠️普通供需与精品供需次数相互独立,不可混用。 2. 供需信息 ✧供需频道 20U一条(适用于所有客户) ✧VIP精品供需 80U一条(适用于专群/公群合作者) 🎁供需广告 一次性预存10条 免费送2条 🎁供需广告 一次性预存20条 免费送5条 🈲非官方任何频道链接,🈲图片,🈲费率 😎😎😎😎 @qt55 😎😎😎😎 @qt522 😎😎😎😎😎 @qtdb

❤2👍1

Showing the 12 most recent of 44 posts we hold for @qtdbbz. 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.

Posts edited after publishing

@qtdbbz edited 10 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.

First edit seen
14 August 2026
Most recent edit
16 October 2026

Forward network

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.

Mentions

Named by 6 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.

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.

Cite this entry

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 12 November 2026 — this entry's latest reading, not the date you are reading this.

“七天公告” (@qtdbbz), 17,089 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/qtdbbz.

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.