😎😎😎😎😎 😎😎😎😎 2597 😎😎😎😎 😎😎😎😎😎 🐋 公群链接:https://t.me/qtdb_2597 😎😎😎😎😎 @YSKM168 😎 公群D组2597 - 承兑-闽乐商行-公群 😎 😎 公群大全 各类业务 1️⃣ 七天官方人员 😎 公群报备流程 公群验群方法

Channel
七天担保-新公群发布
@xinqunfabu
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
18,665subscribers
-232 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 | -1002397831412 |
|---|---|
| Type | Channel |
| Username | @xinqunfabu |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/xinqunfabu |
Topic
Other / unclassifiable — 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 36% 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 |
|---|---|---|
| 18 Sept 2026, 22:41 | 18,665 | -49 |
| 16 Sept 2026, 11:22 | 18,714 | -42 |
| 14 Sept 2026, 14:19 | 18,756 | -29 |
| 12 Sept 2026, 23:40 | 18,785 | -66 |
| 11 Sept 2026, 03:55 | 18,851 | -56 |
| 8 Sept 2026, 02:59 | 18,907 | -100 |
| 5 Sept 2026, 00:21 | 19,007 | -30 |
| 3 Sept 2026, 10:03 | 19,037 | -35 |
| 2 Sept 2026, 07:24 | 19,072 | -31 |
| 1 Sept 2026, 06:25 | 19,103 | -23 |
| 31 Aug 2026, 02:55 | 19,126 | -26 |
| 30 Aug 2026, 05:46 | 19,152 | -35 |
| 29 Aug 2026, 02:56 | 19,187 | -24 |
| 28 Aug 2026, 01:18 | 19,211 | -19 |
| 26 Aug 2026, 22:23 | 19,230 | -19 |
| 25 Aug 2026, 22:16 | 19,249 | -19 |
| 24 Aug 2026, 20:48 | 19,268 | -43 |
| 23 Aug 2026, 05:49 | 19,311 | -38 |
| 21 Aug 2026, 16:58 | 19,349 | +5 |
| 20 Aug 2026, 18:37 | 19,344 | first reading |
Engagement
78 posts held, back to 28 July 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 55 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3.68%
- avg views ÷ 18,665 subscribers
- Avg views / post
- 687
- 16 posts measured
- Reaction rate
- 0.085%
- reactions ÷ views · ER floor
- Posts in window
- 17
- of 78 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. It is computed over the 6 of 16 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 78 (28 July 2026 – 2 September 2026) |
| Views total | 10,985 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 01:27 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.
Reaction mix
18 reactions across 16 posts, in 2 distinct kinds. The most used accounts for 94.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 17 | 94.4% | |
| 👍 | 1 | 5.56% |
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 22 of the 78 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 18 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 78 most recent posts we hold, published 28 July 2026 to 2 September 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
1️⃣1️⃣ 🐋🐋🐋🐋🐋 公群编号:1517 🀄️🀄️:🐋🐋🐋🐋🐋 公群链接:https://t.me/+HRDHiXgWBfo1ODBl 公群负责人:@Hczx1 👉 汇诚Pay-招各类核销 🐋 公群大全 各类业务 1️⃣ 七天官方人员 🐋 公群报备流程 公群验群方法
😎😎😎😎😎 😎😎😎😎 😎😎😎😎 😎😎😎😎😎😎😎😎 🐋 公群链接:https://t.me/+fMC8lOHIris3MjZl 😎😎😎😎😎 @laomianGoole 😎 公群K组1323-Goole软件开发公司-公群 😎 公群大全 各类业务 1️⃣ 七天官方人员 😎 公群报备流程 公群验群方法 Telegram
😎😎😎😎😎 😎😎😎😎 😎😎😎😎 😎😎😎😎😎😎😎😎 🐋 公群链接:https://t.me/+vNUR0G-6ohpmMjZl 😎😎😎😎😎 @JC_PAY88 😎 公群P组1587-德国/意大利/西班牙/立陶宛//尼日/越南/欧洲-美洲海外源头车公群 😎 公群大全 各类业务 1️⃣ 七天官方人员 😎 公群报备流程 公群验群方法
😎😎😎😎😎 😎😎😎😎 😎😎😎 😎😎😎😎 😎😎😎😎😎🐋 😎公群链接:https://t.me/qtdb_222 😎😎😎😎😎 @qd599 👉 公群A组222-起点集团(常规料招一切通道/原声为主) 😀 🐋 公群大全 各类业务 1️⃣ 七天官方人员 🐋 公群报备流程 公群验群方法
1️⃣1️⃣ 🐋🐋🐋🐋🐋 公群编号:1717 🀄️🀄️:🐋🐋🐋🐋🐋 公群链接:https://t.me/qtdb_1717 公群负责人: @huojian58888 👉 公群Q组1717-火箭三方招核销/车队BC常规一条龙-七天担保 5000U 😀 🐋 公群大全 各类业务 1️⃣ 七天官方人员 🐋 公群报备流程 公群验群方法
1️⃣1️⃣ 🐋🐋🐋🐋🐋 公群编号:3211 🀄️🀄️:🐋🐋🐋🐋🐋 公群链接:https://t.me/+qEl6fXX7pl81YTRl 公群负责人: @hehe399 👉 话费卡密支付系统出租/三方四方支付系统出租/三方四方整合系统出租 🐋 公群大全 各类业务 1️⃣ 七天官方人员 🐋 公群报备流程 公群验群方法
Channel photo updated
1️⃣1️⃣ 🐋🐋🐋🐋🐋 公群编号:2666 🀄️🀄️:🐋🐋🐋🐋🐋 公群链接:https://t.me/+yH55XdfbEZQzOTU1 公群负责人:@Dai08080 👉 公群N组2666-长安支付-微信支付宝代付-七天担保 5000u 🐋 🐋 公群大全 各类业务 1️⃣ 七天官方人员 🐋 公群报备流程 公群验群方法
🎊 七天担保 LOGO 大赛奖励发放完毕! 🥇 冠军奖励 7777U 🥈-🏅 其余获奖选手各奖励 777U 所有奖励均已真实转账,转账记录链上公开可查,全程透明可验证。 🔎官方发奖地址: TQcxbMEVhYFSRKKGNdHv5dLAuqpgipSsWT 每一笔奖励都有迹可循,每一次承诺都如期兑现。 感谢所有参赛选手与支持七天担保的朋友! 1️⃣1️⃣1️⃣1️⃣@qtdb 七天担保
🎉 @qtdb 七天担保 LOGO 设计大赛 🏆 最终获奖名单正式公布! 经过公开投票及最终统计,本次 LOGO 设计大赛最终排名如下: 🥇 第1名:演导 @Panamera_88 🥈 第2名:派派 @paipai 🥉 第3名:阿爆 @abfc88 🏅 第4名:小丸子 @xiaowzi520 🏅 第5名:皮诺 @pinuo666 🎊 恭喜以上获奖选手! 感谢所有参赛选手的用心设计,也感谢各位网友的积极参与与宝贵投票! 每一票都是认可,每一份创意都值得尊重。 再次恭喜各位获奖选手,感谢大家对 @qtdb 七天担保 的支持与关注!调整好后正式更换头像~~
👍1
1️⃣1️⃣ 🐋🐋🐋🐋🐋 公群编号:1927 🀄️🀄️:🐋🐋🐋🐋🐋 公群链接:https://t.me/+dF5Q0MZ4XewxNWU1 公群负责人:@Alian3023 👉 龙头支付 专业跑分平台·纯BC保司法·独家玩法 🐋 公群大全 各类业务 1️⃣ 七天官方人员 🐋 公群报备流程 公群验群方法
❤1
Showing the 12 most recent of 78 posts we hold for @xinqunfabu. 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
@xinqunfabu edited 5 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
- 12 August 2026
- Most recent edit
- 18 August 2026
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 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.
@qtdbbz · 20,45451 posts七天担保-公群每日推荐
@qitiandanbaogongqun · 31,19833 posts七天NFT典藏礼物-资讯 · @NFT999
@nft999 · 4,3312 posts七天NFT交流群 @qtnft
@qtnft · 1,4742 posts公群C组7777-百胜支付综合收BC量-公群-七天担保 51888U (阿罪)
@bszf8888888 · 31,1241 post公群S组3666 专业代开直付通主体-公群 3000U (神话轩辕)
@daikaizhifutong · 2,1321 post公群N组1427-景裕白资收出-公群-七天担保 10000U(九岭收到)
@jingyubaizi · 5,2811 postleyunsifangxitong
@leyunsifangxitong · 41 post公群 I 组 2588-帕梅一手渠道专业查档(在线接单)公群-七天担保 20000u (帕梅)
@PAMEITIANYAN · 6,2651 post公群B组6666·起点集团(888租/售/收/抵押/NFT礼物)七天担保 押金6666u (小肉包)
@qidianjituan888 · 3,6211 post公群F组1437-专业打赏养号陪跑刷流水商城打赏资金盘-七天担保-8000U(迪迪 宝妈团)
@qtdb_1437 · 3,7281 post公群Q组1717-火箭三方招核销/车队BC常规一条龙-七天担保-5000U(火箭)
@qtdb_1717 · 3,2521 post公群A组222-起点集团(常规料招一切通道/原声为主)七天担保 22222u (小肉包)
@qtdb_222 · 2,5811 post公群D组2597 - 承兑-闽乐商行-公群 - 七天担保 30200u (承兑)原地址退
@qtdb_2597 · 5,5961 post公群R组3232-Ulinx专业APP跑分 · 安全稳定保司法-七天担保 5000u(励)
@qtdb_3232 · 6,0691 post公群D组666-24h白资收u/收u代付100起,全国送现 -公群-七天担保-20000U(数字商行)
@qtdb_666 · 5,0121 post公群M组2291- 永恒支付收实力码商收一手通道-七天担保-10000U(崽崽)
@qtdb_gq2291 · 1,7871 post
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
- 4
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 4
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 0
- vacant every time we have ever looked
@xinqunfabu named 4 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 6 posts, 9 August 2026 – 19 August 2026 · confirmed gone 3 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 5 posts, 9 August 2026 – 18 August 2026 · confirmed gone 6 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 4 posts, 8 August 2026 – 12 August 2026 · confirmed gone 17 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 3 posts, 8 August 2026 – 10 August 2026 · confirmed gone 11 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“七天担保-新公群发布” (@xinqunfabu), 18,665 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/xinqunfabu.
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.