Telegram RegisterThe public register of Telegram
Telegram profile photo for 七天担保—供♥️需频道🥰

Channel

七天担保—供♥️需频道🥰

@qt522

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

74,183subscribers

+19,868 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
TypeChannel
Username@qt522
Description七天公群 @qtdb 七天公告 @qtdbbz 七天主群 @qitianjituan 七天供需 @qt522 七天系统 @qtxtx 七天曝光 @qt00 七天娱乐 @qt33 七天球盘 @qt44 精品供需 @qt55 前台接待 @qt77 🌐招财七 @qt66 🌐招财八 @qt88 🌐担保交易员 @mofa 🌐担保交易员 @xiqi 🌐七天运营号 @chun 一键群组:https://t.me/addlist/6lAQnIvApTU1MGFk
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live25 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.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

54,31574,18364,2497 August 2026 — 54,315 subscribers7 August 2026 — 54,556 subscribers8 August 2026 — 55,793 subscribers9 August 2026 — 57,230 subscribers10 August 2026 — 58,638 subscribers11 August 2026 — 60,048 subscribers12 August 2026 — 61,442 subscribers13 August 2026 — 63,318 subscribers15 August 2026 — 65,154 subscribers16 August 2026 — 67,169 subscribers17 August 2026 — 68,684 subscribers18 August 2026 — 70,023 subscribers19 August 2026 — 71,360 subscribers20 August 2026 — 71,869 subscribers22 August 2026 — 71,799 subscribers23 August 2026 — 71,719 subscribers24 August 2026 — 71,668 subscribers27 August 2026 — 71,643 subscribers28 August 2026 — 71,666 subscribers29 August 2026 — 71,690 subscribers30 August 2026 — 71,681 subscribers31 August 2026 — 71,626 subscribers1 September 2026 — 71,556 subscribers2 September 2026 — 71,542 subscribers3 September 2026 — 71,519 subscribers5 September 2026 — 71,477 subscribers8 September 2026 — 71,295 subscribers11 September 2026 — 72,288 subscribers13 September 2026 — 72,589 subscribers15 September 2026 — 72,971 subscribers16 September 2026 — 73,451 subscribers19 September 2026 — 73,896 subscribers25 September 2026 — 74,183 subscribers7 August 202625 September 2026
33 measurements spanning 49 days, net +19,868. 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 51,335–77,163 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
25 Sept 2026, 14:3874,183+287
19 Sept 2026, 00:5673,896+445
16 Sept 2026, 19:1673,451+480
15 Sept 2026, 00:4172,971+382
13 Sept 2026, 07:1572,589+301
11 Sept 2026, 10:3772,288+993
8 Sept 2026, 15:3771,295-182
5 Sept 2026, 09:3771,477-42
3 Sept 2026, 09:2371,519-23
2 Sept 2026, 00:4871,542-14
1 Sept 2026, 02:3871,556-70
31 Aug 2026, 04:3571,626-55
30 Aug 2026, 06:1471,681-9
29 Aug 2026, 09:3671,690+24
28 Aug 2026, 07:3571,666+23
27 Aug 2026, 04:1971,643-25
24 Aug 2026, 23:3571,668-51
23 Aug 2026, 11:0371,719-80
22 Aug 2026, 01:1771,799-70
20 Aug 2026, 18:1371,869first reading

Engagement

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

ERR · 30 days
0.362%
avg views ÷ 74,183 subscribers
Avg views / post
268
1,178 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
1,178
of 2,062 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 27 September 2026
Posts held2,062 (7 August 2026 – 27 September 2026)
Views total316,190
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 13:41 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
≈249
Videos
≈3
Links
≈6,580

Lifetime counters from Telegram’s own channel header, read 27 September 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.

Recent posts

27 Sept 2026, 13:40 UTC54 viewsread 27 September 2026

【七天担保-VIP用户供需】 ❤️‍🔥❤️‍🔥❤️‍🔥 需: 微信零钱通/支付宝余额宝 出款 每天300-500万余额 长期稳定出款! 需大量 外贸码,工厂码,商家码,换汇码 😊联系:@vip032 😄😃😄😄😃😄😃😄😃 😄😃😄😃😄😄😃😄😄

27 Sept 2026, 13:17 UTC300 viewsread 27 September 2026

一手自营沃尔玛、苹果卡 💥0偷卡0偷卡💥 ⭐️0纠纷0纠纷⭐️ 低费率高成率无限收量 一手卡密通道 收量!🏖 【沃尔玛】 100-1000 成功率70%+ 【苹果卡】 50-1000 成功率60%+ 价格见底 ,长期稳定! 诚信经营 欢迎各大小四方 .可担保可预付可下发骗子勿扰开户联系私信 🤝 联系人:@qqqqqqdh

27 Sept 2026, 13:12 UTC206 viewsread 27 September 2026

😎😎😎😎😎😎😎😎😎 😀 优质公群|引流扶持活动 ━━━━━━━━━━━━━━ 01|公群:3233 押金:2000u 业务: 代发苹果im信息推广无视内容百分百送达 02|公群:1088 押金:5000u 业务:一道常规 群引导 码接回U 03|公群:333 押金:10888u 业务:原生 H5 招常规料 招一切通道 04|公群:1235 押金:3888u 业务:耐操飞机号丨会员号丨精养老号丨飞机一切业务 05|公群:1447 押金:4100u 业务:旺财 𝗧𝗥𝗫兑换 公群 06|公群:666 押金:20000u 业务:白资收U 全国送现 群贴下浮代付 07|公群:3456 押金:20000u 业务:收个人宝 企业宝款 收U出U承兑 08|公群:6027 押金:6000u 业务:金鑫诚招全国拿现黄金车 09|公群:1377 押金:5000u| 业务:微信 支付宝 BC 收U 10|公群:188…

27 Sept 2026, 13:09 UTC216 viewsread 27 September 2026

⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ 需 需求类型:常规空降约炮色招支付宝口令转账码接车 优势,口令转账码接都可以,单笔万内量拉满,汇率拉满。 小车1500u起大车3000u起啦群开工,来实力大车。量管够 另招聚合码经营码接123存。 精聊盘招各种码车保5天,保量保量 另招一手水房盘口 对接方式/对接人: @qqwwee888

27 Sept 2026, 13:09 UTC275 viewsread 27 September 2026

私服四方收支付宝 微信通道 收通道 收通道 支付宝微信原生、小程序通道 扫码 大额uid 有合适的通道来撩 百分百纯私服量 限额1-2000-3000都可以 要求投诉不退款 我们可以处理 发财链接 @@siyepay68

27 Sept 2026, 13:00 UTC342 viewsread 27 September 2026

私服四方收支付宝 微信通道 收通道 收通道 支付宝微信原生、小程序通道 扫码 有合适的通道来撩 百分百纯私服量 限额1-2000-3000都可以 要求可以扛游戏投诉 发财链接 @@siyepay68

27 Sept 2026, 12:58 UTC354 viewsread 27 September 2026

招一手盘平台下分卡,你充u我代付(量很大很大) 卡转卡代付:色料空降一手直盘 一道色料,日量2000+ 金额3000-50000的卡 时效20-50分钟,进算保司法都可,量大的来 24小时客服在线 @JXJT_666

27 Sept 2026, 12:55 UTC356 viewsread 27 September 2026

💵💵💵💵💵原生📱、📱H5通道,📱内付通道(视频打赏量,纯视频量) 💵支付宝打赏养号通道、码队(专业养号,量大管饱) 帮BC、资金盘等通道养号,可稀释异常订单浓度,降低风控,放大跑量 💵打赏量(手机H5视频网站,付费解锁看片量) 通道全年稳定不日切,费率💵💵最低,成功率👌👌 💵💵💵 @tmpay888💵

27 Sept 2026, 12:55 UTC317 viewsread 27 September 2026

😎😎😎😎😎😎😎 💥聚鑫科技💥 💬公告:本人曾经也是带着会议枪手团队的负责人,在使用市面上会议软件的时候。 反馈声音嘈杂问题、网络问题、反馈迟迟得不到发行方整改。 我们决定与聚鑫科技,共同发行一款会议软件。整改市面上小瑕疵 ⚡️ 全新推出聚鑫会议 🚩聚鑫会议🚩 🚩聚鑫会议🚩 🚩聚鑫会议🚩 🚩🚩小时在线客户、解决客户反馈的软件使用问题。 💬💬官方:因现在软件刚上线阶段,希望全网各大会议枪手一起共同协助整改❗️❗️❗️ 本会议软件、前期不收费。 各位枪手、老板用舒服了再谈价钱。 发现问题、提出问题都有赠送时长奖励。 主打服务到位,让各位老板用得舒心用得放心。 📱📱📱 @jxkjqz 📱📱📱@jxkjqz 📱📱📱@jxkjqz 🐋 七天公群 ⬇️⬇️⬇️ https://t.me/QTDB_2828

27 Sept 2026, 12:46 UTC328 viewsread 27 September 2026

🥰💸迅阳支付💸🥰 😀😀😀 支转卡🥰支转支🥰 你❤️😛我❤️❤️🟢 2️⃣4️⃣小时稳定打款 🀄️🀄️永久 😀😄😃😀😃 下发模式:API/批量上传,群贴 ❤️❤️❤️❤️❤️❤️❤️❤️ 区间:1️⃣0️⃣0️⃣-1️⃣0️⃣0️⃣0️⃣0️⃣ ❤️❤️❤️ 业务对接:@xunyangpay777 拒绝玩套路 P图 小数点 拉假群 就别来浪费时间

27 Sept 2026, 12:45 UTC440 viewsread 27 September 2026

鸿运支付:微信BC专业户 ❤❤❤❤❤❤❤❤❤ 自营微信BC一手通道价格 量大可谈!!! 😀产品名称:3w+微信内层真原生扫码 通道限额:100-500任意金额 ✔ 😀产品名称:10w+微信内层真原生扫码 通道限额:100-500任意金额✔ 通 道: 474 通道名: 自有微信-BC 总成率: 52.3%(77130/147580) 一小时: 63.4%(5180/8170) 五分钟: 77.5%(620/800) 以上通道,全天成率50+ 24小时不日切,全年无休,稳定输出,无限收量⚡️⚡️⚡️⚡️ ‼️‼️寻:盘口 包网 大四方 长期合作‼️‼️ ‼️‼️无限收量,支持担…

27 Sept 2026, 12:33 UTC363 viewsread 27 September 2026

需 需求类型:盘口直招 【招】:大额扫街码 支付宝个码 经营码 【招】:微信个码 经营码 大额 卡 【招】:大额支付宝账号 各种丝滑大额通道 【發】:量大不罚站,大车管饱 ,罚站陪U 【發】:小车扶持 罚站陪U 24小时开工 联系业务员:@sanyi666 群链接:https://t.me/+2558-eVt2cMwNjA1

Showing the 12 most recent of 2,062 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.

Names

Channels on the register whose handles appear in this channel's posts.

公群B组6666·起点集团(888租/售/收/抵押/NFT礼物)七天担保 押金6666u (小肉包)
@qidianjituan888 · 3,621
66 posts
公群G组-002机中文首家 NFT礼物 888号码-公群-已押七天担保8888u(Mkts-大神)
@hwssss · 3,594
62 posts
公群 I 组 2588-帕梅一手渠道专业查档(在线接单)公群-七天担保 20000u (帕梅)
@PAMEITIANYAN · 6,265
59 posts
公群D组666-24h白资收u/收u代付100起,全国送现 -公群-七天担保-20000U(数字商行)
@qtdb_666 · 5,012
51 posts
全国高端雪生妹包yang(大熊)公群-七天担保-5000U(领航)
@BYmeimei666 · 3,327
49 posts
公群D组1277-相逢承兑-公群-七天担保-30000U(相逢何必曾相识)
@xiangfeng66666 · 3,190
47 posts
公群H组688-帽子源头天眼查全天在线-公群七天担保-10888U(帽子天眼查)
@qtdb_688 · 7,036
46 posts
公群J组2055-2Trx闪租 | 兑换 | 高频笔数67u100笔-公群 七天担保 3500u(小林)
@silentnbyyds · 15,097
45 posts
公群K组-1368-千禧三方四方系统//代收系统/代付系统/出租/搭建/维护/开户-公群-七天担保-8888U(星辰)
@qtdb_1368 · 8,070
44 posts
公群Q组1568 -bc集团收自营三方、码商- 公群 - 七天担保-15000U(支付协调-小熊)
@qtgq888 · 4,390
43 posts
公群C组7777-百胜支付综合收BC量-公群-七天担保 51888U (阿罪)
@bszf8888888 · 31,124
41 posts
七天担保-公群每日推荐
@qitiandanbaogongqun · 30,984
39 posts
公群D组-3688 万胜白资承兑-七天担保-10000U(晴空)
@qtdb_3688 · 10,031
34 posts
公群T组1314 - 香港流量卡−七天担保3888u(香港卡)
@qtdbgq1314 · 5,065
33 posts
公群S组3666 专业代开直付通主体-公群 3000U (神话轩辕)
@daikaizhifutong · 2,132
32 posts
公群E组1088-四海集团一道群引导码接回U-公群七天担保-5555U(四海集团~老黑)
@qtdb_1088 · 5,850
31 posts
公群A组222-起点集团(常规料招一切通道/原声为主)七天担保 22222u (小肉包)
@qtdb_222 · 2,581
31 posts
公群Q组2544 头文字D支付:收一切自营bc/资金通道 公群 -七天担保 10000u (高桥凉介)
@liaole6666 · 5,696
27 posts
公群Y组168-电费话费信用卡网贷公户代还收U放料公群七天担保-10000U(無名)
@qtdb_168 · 3,321
20 posts
公群D组2597-中信白资承兑 公群七天担保-10000U(中信)
@qtdb_2597 · 5,874
20 posts
公群K组2206-自动拉码插件/支付逆向协议定制-公群-七天担保 3000u (渣渣辉)
@zhifubaopojie · 1,921
20 posts
公群N组1427-景裕白资收出-公群-七天担保 10000U(九岭收到)
@jingyubaizi · 5,281
19 posts
公群N组1589-阿酷代付卡卡支卡支付宝扫码现存白资代付-公群-七天担保-5000U(阿酷)
@xynb98888 · 9,869
19 posts
公群D组1067-澜讯承兑上浮2分无限收企业BC款养号款-公群-已押七天担保10000u(将军)
@zuiqiangsoso · 5,488
18 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.

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

“七天担保—供♥️需频道🥰” (@qt522), 74,183 subscribers as measured 25 September 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.