常规空降料 量大管饱 盘口直招 各种牛逼码丝滑码链接等通道 可滴滴我!汇率置顶!@Luck11135 常规空降料 量大管饱 盘口直招 各种牛逼码丝滑码链接等通道 可滴滴我!汇率置顶!@Luck11135 常规空降料 量大管饱 盘口直招 各种牛逼码丝滑码链接等通道 可滴滴我!汇率置顶!@Luck11135 常规空降料 量大管饱 盘口直招 各种牛逼码丝滑码链接等通道 可滴滴我!汇率置顶!@Luck11135 常规空降料 量大管饱 盘口直招 各种牛逼码丝滑码链接等通道 可滴滴我!汇率置顶!@Luck11135

Channel
七天担保—供♥️需频道🥰
@qt522
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
69,942subscribers
+15,627 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001755362148 |
|---|---|
| Type | Channel |
| Username | @qt522 |
| Description | 七天公群 @qtdb 七天公告 @qtdbbz 七天主群 @qitianjituan 七天供需 @qt522 七天系统 @qtxtx 七天曝光 @qt00 七天娱乐 @qt33 七天球盘 @qt44 精品供需 @qt55 前台接待 @qt77 🌐招财七 @qt66 🌐招财八 @qt88 🌐担保交易员 @mofa 🌐担保交易员 @xiqi 🌐七天运营号 @chun 一键群组:https://t.me/addlist/6lAQnIvApTU1MGFk |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 23 October 2026 |
| Measurements held | 46 |
| Confirmed unchanged | 1 time, most recently 23 October 2026 |
| On Telegram | t.me/qt522 |
Topic
Hacking & security — 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 52% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Oct 2026, 17:16 | 69,942 | -349 |
| 22 Oct 2026, 18:27 | 70,291 | -385 |
| 21 Oct 2026, 15:06 | 70,676 | -120 |
| 20 Oct 2026, 10:59 | 70,796 | -212 |
| 19 Oct 2026, 09:11 | 71,008 | -209 |
| 18 Oct 2026, 09:29 | 71,217 | +42 |
| 17 Oct 2026, 08:07 | 71,175 | -186 |
| 16 Oct 2026, 09:41 | 71,361 | +77 |
| 15 Oct 2026, 09:55 | 71,284 | -54 |
| 14 Oct 2026, 12:46 | 71,338 | -173 |
| 12 Oct 2026, 22:44 | 71,511 | -479 |
| 8 Oct 2026, 15:16 | 71,990 | -734 |
| 4 Oct 2026, 06:00 | 72,724 | -1,459 |
| 25 Sept 2026, 14:38 | 74,183 | +287 |
| 19 Sept 2026, 00:56 | 73,896 | +445 |
| 16 Sept 2026, 19:16 | 73,451 | +480 |
| 15 Sept 2026, 00:41 | 72,971 | +382 |
| 13 Sept 2026, 07:15 | 72,589 | +301 |
| 11 Sept 2026, 10:37 | 72,288 | +993 |
| 8 Sept 2026, 15:37 | 71,295 | first reading |
Engagement
3,100 posts held, back to 7 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 157 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.342%
- avg views ÷ 69,942 subscribers
- Avg views / post
- 239
- 1,185 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1,187
- of 3,100 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.
| Window | Rolling 30 days · latest post in window 23 October 2026 |
|---|---|
| Posts held | 3,100 (7 August 2026 – 23 October 2026) |
| Views total | 283,453 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 23 Oct 2026, 17:55 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
- ≈452
- Videos
- ≈7
- Links
- ≈9,650
Lifetime counters from Telegram’s own channel header, read 23 October 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.
- Video runtime
- 1m 14s
- Average length
- 1m 14s
Measured directly from 1 video 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.
Recent posts
【七天担保-VIP精品供需】 我司可付款市面上任何代付订单,不挑单子,有单就打 群贴1分钟内秒出款,白资博彩底料 有需要的老板请联系 💵💵💵 @chenqiiiii #承兑类
⚡⚡⚡⚡✅️️️️️️⚡⚡⚡⚡⚡⚡ 【骗子死全家】 🪙业务一: 【0.1TRX】一笔转账能量 转错包退 📱业务二:【TRX闪兑】 我们TRX太多了 亏本卖 📱业务三: 【免费生成U转账图,提供哈希即可】 📱业务四: 【终身永久无限能量,一次开通终身转u不要TRX】 ✅业务五: 【笔数套餐 50U=100笔能量】 全网上押100万USDT 重金打造只为推广 业务: @swk15_bot 老板: @sun_trx 公群: https://t.me/+rsCmq_ap00cxNjQ1 #代收类
一道空降上门色料日量50+ 主打料性安全,不司法 24小时招卡码,可循环使用 欢迎车队来合作:@sg88888 #资金类
t.me/qtdb_6017 顶级丝滑车找一手料 拒绝低价! 国内现有产品: 1/人头卡接六合料 2/营业执照办的聚合码接23存。 3/银联直扫2000-5000 国外车 越南/澳洲/菲律宾 联系人:@HS8881 #资金类
招永辉核销、自带ck 招永辉核销、自带ck 招永辉核销、自带ck @foxx9527 #密币类
😎😎😎😎😎😎😎😎😎 😀 优质公群|引流扶持活动 ━━━━━━━━━━━━━━ 01|公群:3427 押金:5000u 业务:MGM空降直盘招车放料-常规色/精聊- 02|公群:6866 押金:5000u 业务:KK常规刷单色会议直盘招码/卡车一切丝滑渠道 03|公群:6147 押金:5000u 业务: 李九九一手游戏置顶码 04|公群:6157 押金:5000u 业务: 晚霞微信/支付宝/QQ/下载付/码接回U 05|公群:6199 押金:5000u 业务: 众远QQ/微信/支付宝/云闪/银联置顶码 06|公群:6717 押金:5000u 业务:群引导一道码接回u群红包 07|公群:6727 押金:5000u 业务:二道微信备付金放料 08|公群:6747 押金:5000u 业务:金米 一道码接回u 09|公群:6778 押金:5000u| 业务: 鑫泰支付码接回U 10|公群:1010 押金:5000…
😎😎😎😎😎😎😎😎😎 😀 优质公群|引流扶持活动 ━━━━━━━━━━━━━━ 01|公群:5177 押金:5000u 业务:远东集团码接回U 02|公群:4477 押金:5000u 业务:世纪集团码接回U 03|公群:3247 押金:5000u 业务: 电动车专场码接回u 04|公群:2867 押金:5000u 业务:致胜支付码接回u 05|公群:2977 押金:5000u 业务:汇通常规色直盘一道招码接回u车 06|公群:2487 押金:5000u 业务:FK集团-支微/地区个码接放/回U 07|公群:6097 押金:5000u 业务:盛邦二道支付宝/微信/24h供码常规 08|公群:3668 押金:5000u 业务: 一手原生,收打赏,私服,VPN一切白量。收BC高内量 09|公群:3487 押金:5000u| 业务:招QQ实力车 10|公群:7187 押金:5000u| 业务:招二道现存车队 11…
纯BC信誉盘,招支付宝群贴码车 。保永久司法,保永久投诉。双押! 位置不多,懂行的来。 全网最稳养老项目,当个班来上! 时间宝贵 请先报备码数+押金。能否立即拉群上押!今天能立马开工的优先。 假群,记者,废话多的勿扰 招商负责人 @meimaotai53 #代收类
招小天才微信经营码承兑 量大 @LLLDD9 招小天才微信经营码承兑 量大 @LLLDD9 招小天才微信经营码承兑 量大 @LLLDD9 #承兑类
😎😎😎😎😎😎😎😎😎😎😎😎😎 七天担保官方精选|优质公群每日 😎 轮番推荐,持续曝光
⚡️⚡️⚡️⚡️远洋集团⚡️⚡️⚡️⚡️ 👍一手自营招各地区实物车 核销车 📢寻:小时达 次日达 手机 平板 显卡 笔记本 中介茶水费安排 📱📱📱📱📱📱 罚站我赔u 汇率全网最高 不需要移动 风险小 配卡 配资源 罚站有茶水费 每个月红包安排 💎💎💎💎💎💎💎💎💎💎 🔥主推 🔥主推🔥主推 🔥主推🔥主推 😐商务对接:@eqbbbb 😐双向: @JinS888bot ⚡️⚡️⚡️⚡️ ⚡️⚡️⚡️⚡️ #资金类
Showing the 12 most recent of 3,100 posts we hold for @qt522. 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
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 4 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.
@sanguochanggui · 1,29567 posts公群G组-002机中文首家 NFT礼物 888号码-公群-已押七天担保-8888U(@Mkts-大神)
@hwssss · 4,42462 posts公群H组 2588-帕梅一手渠道专业查档(在线接单)公群-七天担保-16320U(帕梅·天眼查档(24小时在线))
@PAMEITIANYAN · 7,08759 posts公群D组666-24h白资收u/收u代付100起,全国送现 -公群-七天担保-20000U(数字商行)
@qtdb_666 · 5,57451 posts全国高端雪生妹包yang(大熊)公群-七天担保-5000U(领航)
@BYmeimei666 · 3,43649 posts公群D组1277-相逢承兑-公群-七天担保-30000U(八馬承兑-相逢(认准888))
@xiangfeng66666 · 3,80248 posts公群J组2055-2Trx闪租 | 兑换 | 高频笔数67u100笔-公群 七天担保-3500U(小林-TRX能量会员飞机号888)
@silentnbyyds · 15,52145 posts公群L组-1368-千禧三方四方系统//代收系统/代付系统/出租/搭建/维护/开户-公群-七天担保-8888U(千禧-星辰)
@qtdb_1368 · 9,41244 posts公群B组1568 -bc集团收自营三方、码商- 公群 - 七天担保-10000U(支付协调-小熊)
@qtgq888 · 5,70143 posts公群D组7777- 百胜白资换汇全天24小时营业-公群-七天担保-51888U(百胜负责人-阿罪)
@bszf8888888 · 30,95241 posts七天担保-公群每日推荐
@qitiandanbaogongqun · 30,34939 posts公群D组-3688 金六福白资承兑-七天担保-10000U(晴空)
@qtdb_3688 · 11,36634 posts公群E组3666 专业代开直付通主体-公群 3000U (神话轩辕)
@daikaizhifutong · 2,71833 posts公群G组1314 - 香港流量卡−七天担保-3888U(橙子流量卡注册卡批发零售)
@qtdbgq1314 · 4,93533 posts公群E组222-起点集团(常规料招一切通道/原声为主)-七天担保-5222U(小肉包)
@qtdb_222 · 2,64031 posts公群B组2544 头文字D支付:收一切自营bc/资金通道 公群 -七天担保-10000U(高桥凉介)
@liaole6666 · 6,86627 posts公群D组2597-中信白资承兑 公群七天担保-10000U(信 中)
@qtdb_2597 · 6,22926 posts公群E组1333- 娜扎nz一手小天才群引导无限吃量- 七天担保-5000U(娜扎nz)
@qtgq_1333 · 1,86226 posts七天体育推单频道
@qitiantiyu · 2,39925 posts公群C组3232-Ulinx专业APP跑分 · 安全稳定保司法-七天担保-5000U(励)
@qtdb_3232 · 6,06924 posts公群D组2787-澜讯承兑上浮2分无限收企业BC款养号款-公群-已押七天担保-10000U(将军 [四方系统,收自营通道])
@zuiqiangsoso · 6,07521 posts公群E组168-电费话费信用卡网贷公户代还收U放料公群七天担保-10000U(無名)
@qtdb_168 · 5,04020 posts0.1TRX免费转U
@jingyubaizi · 4819 posts公群N组1589-阿酷代付卡卡支卡支付宝扫码现存白资代付-公群-七天担保-5000U(阿酷(运营号❤️))
@xynb98888 · 11,23019 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.
Handles this channel named that no longer answer
- Dead references
- 19
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 12
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 7
- vacant every time we have ever looked
@qt522 named 19 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 32 posts, 8 August 2026 – 24 September 2026 · confirmed gone 21 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 21 posts, 8 August 2026 – 3 September 2026 · confirmed gone 3 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 10 posts, 24 August 2026 – 21 September 2026 · confirmed gone 8 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 8 posts, 9 August 2026 – 1 September 2026 · confirmed gone 3 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 4 posts, 24 August 2026 – 26 August 2026 · confirmed gone 19 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 3 posts, 9 August 2026 – 25 August 2026 · confirmed gone 7 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 3 posts, 16 August 2026 – 18 August 2026 · confirmed gone 13 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 2 posts, 13 September 2026 – 13 September 2026 · confirmed gone 15 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 2 posts, 26 August 2026 – 26 August 2026 · confirmed gone 11 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 18 September 2026 – 18 September 2026 · confirmed gone 10 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 13 September 2026 – 13 September 2026 · confirmed gone 9 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 9 August 2026 – 9 August 2026 · confirmed gone 17 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 3 September 2026 – 7 September 2026
named in 1 post, 11 October 2026 – 11 October 2026
named in 1 post, 10 October 2026 – 10 October 2026
named in 1 post, 13 September 2026 – 13 September 2026
named in 1 post, 12 September 2026 – 12 September 2026
named in 1 post, 10 September 2026 – 10 September 2026
named in 1 post, 13 August 2026 – 13 August 2026
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.
“七天担保—供♥️需频道🥰” (@qt522), 69,942 subscribers as measured 23 October 2026. Telegram Register, tgregister.com/channel/qt522.
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.