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

Channel

七天公告

@qtdbbz

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

24,881subscribers

+8,481 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
Created24 February 2026 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live23 October 2026
Measurements held47
Confirmed unchanged1 time, most recently 23 October 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 why it has no browse page of its own yet.

Growth

16,40025,00620,7037 August 2026 — 16,400 subscribers8 August 2026 — 16,422 subscribers9 August 2026 — 16,511 subscribers10 August 2026 — 16,611 subscribers11 August 2026 — 16,696 subscribers12 August 2026 — 16,745 subscribers13 August 2026 — 16,799 subscribers14 August 2026 — 16,891 subscribers16 August 2026 — 16,988 subscribers17 August 2026 — 17,067 subscribers18 August 2026 — 17,132 subscribers19 August 2026 — 17,209 subscribers20 August 2026 — 17,348 subscribers21 August 2026 — 17,442 subscribers22 August 2026 — 17,510 subscribers24 August 2026 — 17,586 subscribers25 August 2026 — 17,688 subscribers26 August 2026 — 17,729 subscribers27 August 2026 — 17,813 subscribers28 August 2026 — 17,863 subscribers29 August 2026 — 17,946 subscribers30 August 2026 — 17,990 subscribers31 August 2026 — 17,995 subscribers1 September 2026 — 18,037 subscribers2 September 2026 — 18,049 subscribers3 September 2026 — 18,110 subscribers5 September 2026 — 18,104 subscribers8 September 2026 — 18,165 subscribers11 September 2026 — 19,028 subscribers13 September 2026 — 19,327 subscribers14 September 2026 — 19,683 subscribers16 September 2026 — 20,051 subscribers19 September 2026 — 20,454 subscribers25 September 2026 — 21,247 subscribers4 October 2026 — 22,181 subscribers9 October 2026 — 22,640 subscribers13 October 2026 — 23,343 subscribers14 October 2026 — 23,641 subscribers15 October 2026 — 23,997 subscribers16 October 2026 — 24,356 subscribers17 October 2026 — 24,626 subscribers18 October 2026 — 24,739 subscribers19 October 2026 — 24,854 subscribers20 October 2026 — 25,006 subscribers21 October 2026 — 24,723 subscribers22 October 2026 — 24,795 subscribers23 October 2026 — 24,881 subscribers24,8817 August 202623 October 2026
47 measurements spanning 77 days, net +8,481. 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 15,109–26,297 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 47
Measured (UTC)SubscribersChange
23 Oct 2026, 18:0024,881+86
22 Oct 2026, 21:1024,795+72
21 Oct 2026, 21:0824,723-283
20 Oct 2026, 17:0525,006+152
19 Oct 2026, 13:3424,854+115
18 Oct 2026, 10:2624,739+113
17 Oct 2026, 13:3624,626+270
16 Oct 2026, 15:0124,356+359
15 Oct 2026, 15:5623,997+356
14 Oct 2026, 17:2023,641+298
13 Oct 2026, 05:4623,343+703
9 Oct 2026, 00:1522,640+459
4 Oct 2026, 10:3722,181+934
25 Sept 2026, 22:1621,247+793
19 Sept 2026, 06:2120,454+403
16 Sept 2026, 19:3720,051+368
14 Sept 2026, 19:5919,683+356
13 Sept 2026, 06:4219,327+299
11 Sept 2026, 13:0119,028+863
8 Sept 2026, 17:5718,165first reading

Engagement

43 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 81 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
48.6%
avg views ÷ 24,881 subscribers
Avg views / post
12,100
13 posts measured
Reaction rate
0.124%
reactions ÷ views · ER floor
Posts in window
13
of 43 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 19 October 2026
Posts held43 (24 February 2026 – 19 October 2026)
Views total157,140
Reactions total195
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken23 Oct 2026, 14:14 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

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,029 reactions across 36 posts, in 27 distinct kinds. The most used accounts for 14.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤30114.8%
❤‍🔥1839.02%
👍1477.24%
💔1045.13%
🔥1004.93%
💩994.88%
😡894.39%
🖕884.34%
😈884.34%
🥱854.19%
💯834.09%
🤩834.09%
🤮834.09%
🍌793.89%
🎉793.89%
🥰783.84%
👎773.79%
😢773.79%
😍552.71%
🤬241.18%
7 further kinds271.33%

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

Measured over the 43 most recent posts we hold, published 24 February 2026 to 19 October 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

19 Oct 2026, 07:50 UTC≈3,080 views2 reactionsread 23 October 2026

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

❤2

16 Oct 2026, 12:47 UTC≈19,400 views43 reactionsread 23 October 2026

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

❤18👍17👌4👎4

15 Oct 2026, 23:10 UTC≈11,600 views34 reactionsread 23 October 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👍6🫡6🤝2

15 Oct 2026, 14:48 UTC≈6,990 views36 reactionsread 23 October 2026
Photo

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

👍18❤15😨3

15 Oct 2026, 12:55 UTC≈17,600 views23 reactionsread 23 October 2026
Photo

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

❤20👏3

15 Oct 2026, 11:14 UTC≈8,940 views23 reactionsread 23 October 2026
Photo

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

❤16👍7

12 Oct 2026, 15:59 UTC≈5,080 views3 reactionsread 23 October 2026
Photo

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

❤3

9 Oct 2026, 11:19 UTC≈4,720 views10 reactionsread 23 October 2026
Photo

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

❤6👍2💯2

9 Oct 2026, 04:36 UTC≈4,100 views0 reactionsread 23 October 2026
Photo

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

3 Oct 2026, 04:41 UTC≈18,800 views3 reactionsread 23 October 2026
Video

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

❤2👍1

1 Oct 2026, 05:08 UTC≈34,400 views4 reactionsread 19 October 2026
Photo

😎😎😎😎七天担保 • 全网公群扶持活动|重磅开启 😀本次计划扩展全网新开公群|优质老群同步开启🔥🔥🔥 😎 新公群大礼包3777U+ 老板专属红包 17777U 😎 扩展资源(五大类新入驻免三个月公群月费)(价值900U) ✧ 类别:(资金类|海外类|卡商类|账号类|引流类) ✧ 其余类公群新入驻享受活动一次性缴纳3个月 777U优惠价 😎 资源加持|曝光赋能|导流助推(所有新公群) ✧20条定向供需|10条精品供需 |(价值1200U) ✧ 强烈推荐轮播|每日推荐轮播 | (价值777U) ✧ 精准业务匹配|强私曝光3000+ |(价值300U) 😎经营满3个月的(优质老群) ✧ 7条定向供需 + 7条精品供需 (价值700U) ✧ 持续扶持| 助力老群长期运营+优先资源匹配 😎 资源联动·老板专属 【七天老板圈】 人数每满500人 天降17777U红包福利 ✧入驻公群老板,直接申请…

❤4

Showing the 12 most recent of 43 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 23 October 2026 — this entry's latest reading, not the date you are reading this.

“七天公告” (@qtdbbz), 24,881 subscribers as measured 23 October 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.