中信担保上压(公群列表)@zxdb pinned «寻一切一手卡扣渠道,有实力的联系 @ammppq»

Channel
中信担保上压(公群列表)@zxdb
@zxdb55
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
17,903subscribers
+8,252 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 | -1001884250203 |
|---|---|
| Type | Channel |
| Username | @zxdb55 |
| Description | 中信担保成立于2022年11月 官方相关工作人员: 【交易前仔细核查ID】 上押公群:@zxdb 专群担保:@zxdb01 纠纷处理:@zxdb02 广告发布: @zxdb03 二组发布 :@zhongxin120 推广负责: @zxdb04 付费供需: @zxdb44 在押公群: @zxdb55 (不是以上ID皆是骗子!!) 主动联系你发广告打款的都是骗子!!! |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 November 2026 |
| Measurements held | 62 |
| Confirmed unchanged | 1 time, most recently 18 November 2026 |
| On Telegram | t.me/zxdb55 |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 46% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Nov 2026, 10:45 | 17,903 | -291 |
| 15 Nov 2026, 09:16 | 18,194 | +18 |
| 12 Nov 2026, 02:01 | 18,176 | +78 |
| 10 Nov 2026, 02:07 | 18,098 | -31 |
| 8 Nov 2026, 14:57 | 18,129 | -64 |
| 7 Nov 2026, 09:34 | 18,193 | +46 |
| 6 Nov 2026, 08:09 | 18,147 | -43 |
| 5 Nov 2026, 07:55 | 18,190 | +115 |
| 4 Nov 2026, 06:49 | 18,075 | +11 |
| 3 Nov 2026, 07:11 | 18,064 | +123 |
| 2 Nov 2026, 08:35 | 17,941 | -81 |
| 1 Nov 2026, 10:45 | 18,022 | +68 |
| 31 Oct 2026, 10:36 | 17,954 | +1 |
| 30 Oct 2026, 09:30 | 17,953 | +30 |
| 29 Oct 2026, 08:34 | 17,923 | +24 |
| 28 Oct 2026, 06:08 | 17,899 | -138 |
| 27 Oct 2026, 04:57 | 18,037 | -380 |
| 26 Oct 2026, 06:56 | 18,417 | +162 |
| 25 Oct 2026, 07:27 | 18,255 | +172 |
| 24 Oct 2026, 10:25 | 18,083 | first reading |
Engagement
21 posts held, back to 24 May 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 77 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 2.33%
- avg views ÷ 17,903 subscribers
- Avg views / post
- 417
- 1 post measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 2
- of 21 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 21 October 2026 |
|---|---|
| Posts held | 21 (24 May 2024 – 21 October 2026) |
| Views total | 417 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Nov 2026, 17:31 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
- 17
- Videos
- 1
- Links
- 51
Lifetime counters from Telegram’s own channel header, read 18 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.
Reaction mix
87 reactions across 11 posts, in 7 distinct kinds. The most used accounts for 56.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 49 | 56.3% | |
| 👍 | 23 | 26.4% | |
| 👎 | 7 | 8.05% | |
| 💩 | 3 | 3.45% | |
| 😁 | 2 | 2.30% | |
| 🤮 | 2 | 2.30% | |
| 💯 | 1 | 1.15% |
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 13 of the 21 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 87 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 24 May 2024 to 21 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
Telegram’s own ‘edited’ marker: 0 of 2 posts held from the last 30 days (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).
寻一切一手卡扣渠道,有实力的联系 @ammppq
中信担保上压(公群列表)@zxdb pinned «📣📣📣重要通知‼️: 提升担保服务品质,我们在行动!所谓担保说白了就是交易安全,作为担保的一员,我们深知每一笔交易背后都承载着信任与期待。为了让大家的资金交易更加的安全可靠,我们对此作出了以下调整: 🔥中信担保即将更换新地址🔥 旧地址TFzyEWZeCiyRRovxgvMtuSQT7C4BX2E7Ae 新地址THXmnmmxAE76KYHmiQ2DUwXkDJFm7xYjbS 各位亲爱的会员发布充值/上押开群请认准新地址。 所有资金一分不少即将转移到新地址,中信上压百分百放心…»
📣📣📣重要通知‼️: 提升担保服务品质,我们在行动!所谓担保说白了就是交易安全,作为担保的一员,我们深知每一笔交易背后都承载着信任与期待。为了让大家的资金交易更加的安全可靠,我们对此作出了以下调整: 🔥中信担保即将更换新地址🔥 旧地址TFzyEWZeCiyRRovxgvMtuSQT7C4BX2E7Ae 新地址THXmnmmxAE76KYHmiQ2DUwXkDJFm7xYjbS 各位亲爱的会员发布充值/上押开群请认准新地址。 所有资金一分不少即将转移到新地址,中信上压百分百放心,我们坚决抵制任何假押在任何一个中信担保的公群里做业务若是公群老板跑路,我们都会全额赔付,中信担保为你保驾护航💙
❤10👍6👎5😁2
📣📣📣中信担保公告: 我们的业务担保团队一直在默默耕耘,努力打造一个更完善的担保体系,业务处理一目了然!1️⃣将新增广告客服号 @zxdb03,各位发布广告请移步 @zxdb03 所有包月包周老客户都会对接好!2️⃣担保开群联系 @zxdb,专群1v1担保 @zxdb01 交易金额100u以下免费担保! 在tg有交易?怕跑路?别担心,我们客服团队都已经准备好了,无论是交易纠纷还是使用疑问,一建呼叫我们的客服团队,都是经过专业培训,不仅懂业务,更懂得如何让大家满意。就是确保大家在交易过程中遇到的任何问题都能得到及时、有效的解答和帮助。无论是操作上的疑问,还是交易中的担忧,有任何的建议或反馈都可联系我们! 中信担保相关工作人员: 【交易前仔细核查ID】 上押公群:@zxdb 专群担保:@zxdb01 纠纷处理:@zxdb02 广告发布: @zxdb03 推广负责: @zxdb04 付费供需:…
❤5💯1
中信担保上压(公群列表)@zxdb pinned Deleted message
😀😀😀😀😀😀😀😀😀😀 公群018粤湘国际白资收u上押10000u —————————— 公群编号:018 公群链接:https://t.me/+BtDmpNnfb6g2MmNl 验群通道:https://t.me/zxdb55/77 —————————— 🎉中信担保祝您发大财行大运! 😀😀😀😀😀😀😀😀😀
👍2❤1
中信担保上压(公群列表)@zxdb pinned a photo
‼️重要公告: 最近有人造谣说中信担保是租的4字ID? 最近有人造谣说中信担保是租的4字ID? 最近有人造谣说中信担保是租的4字ID? ❤️在这里澄清一下 中信担保有这个实力也有这个能力拥有4字ID、上面图片是2023年8月中信担保购买4字ID的记录!现ID已价值二十几万人民币 ✅中信担保 成立于2022年11月,成立至今,担保金额达致2000万!已帮助数千人完成交易担保,波场链交易地址可查,避免遇到不良商家,在飞机上当受骗! 💰担保收款地址:🔻点击复制TFzyEWZeCiyRRovxgvMtuSQT7C4BX2E7Ae 中信担保推广花费了大量时间与精力去投放广告,招了一批又一批的推广员推广,又花了大量资金开发各种机器人服务大众推广和引流,覆盖飞机的各行各业群发与私信宣传,吸纳各行各业的老板精英!只为做好中信担保 因为自己淋过雨,所以想为别人撑伞! ——中信担保🔰 想交易?怕被骗?那就找中信担保为你保驾护航!🔰 …
❤23👍11💩3👎2🤮2
😀😀😀😀😀😀😀😀😀😀 公群050乔姐烟业主打置换品质 上押300u —————————— 公群编号:050 公群链接:https://t.me/qiaojie66 验群通道:https://t.me/zxdb55/77 —————————— 🎉中信担保祝您发大财行大运! 😀😀😀😀😀😀😀😀
❤2👍1
中信担保上压(公群列表)@zxdb pinned Deleted message
😀😀😀😀😀😀😀😀😀😀 公群049 大洲-代开会员/出售飞机号/出租888 上押300u【已退押】 —————————— 公群编号:049 公群链接:https://t.me/bbbapi 验群通道:https://t.me/zxdb55/77 —————————— 🎉中信担保祝您发大财行大运! 😀😀😀😀😀😀😀😀
❤3👍1
Showing the 12 most recent of 21 posts we hold for @zxdb55. 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.
Mentions
Names
Channels on the register whose handles appear in this channel's 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
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@zxdb55 named 2 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, 8 August 2026 – 18 August 2026 · confirmed gone 7 November 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 8 posts, 8 August 2026 – 18 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 18 November 2026 — this entry's latest reading, not the date you are reading this.
“中信担保上压(公群列表)@zxdb” (@zxdb55), 17,903 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/zxdb55.
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.