Telegram RegisterThe public register of Telegram
Telegram profile photo for 中信担保上压(公群列表)@zxdb

Channel

中信担保上压(公群列表)@zxdb

@zxdb55

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

10,402subscribers

+751 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
TypeChannel
Username@zxdb55
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/zxdb55

Growth

9,65110,40210,026.57 August 2026 — 9,651 subscribers7 August 2026 — 9,673 subscribers10 August 2026 — 9,954 subscribers14 August 2026 — 10,312 subscribers15 August 2026 — 10,337 subscribers17 August 2026 — 10,402 subscribers7 August 202617 August 2026
6 measurements spanning 10 days, net +751. 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 9,538–10,515 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 10:3710,402+65
15 Aug 2026, 19:5310,337+25
14 Aug 2026, 06:5810,312+358
10 Aug 2026, 13:129,954+281
7 Aug 2026, 15:339,673+22
7 Aug 2026, 10:459,651first reading

Engagement

19 posts held, back to 24 May 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 18 pagesof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 3 July 2024. An engagement rate over an empty window would be a number about nothing.

Reaction mix

83 reactions across 11 posts, in 7 distinct kinds. The most used accounts for 55.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4655.4%
👍2327.7%
👎67.23%
💩33.61%
😁22.41%
🤮22.41%
💯11.20%

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

Measured over the 19 most recent posts we hold, published 24 May 2024 to 3 July 2024, 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

3 Jul 2024, 10:25 UTCviews —

中信担保上压(公群列表)@zxdb pinned «📣📣📣重要通知‼️: 提升担保服务品质,我们在行动!所谓担保说白了就是交易安全,作为担保的一员,我们深知每一笔交易背后都承载着信任与期待。为了让大家的资金交易更加的安全可靠,我们对此作出了以下调整: 🔥中信担保即将更换新地址🔥 旧地址TFzyEWZeCiyRRovxgvMtuSQT7C4BX2E7Ae 新地址THXmnmmxAE76KYHmiQ2DUwXkDJFm7xYjbS 各位亲爱的会员发布充值/上押开群请认准新地址。 所有资金一分不少即将转移到新地址,中信上压百分百放心…»

3 Jul 2024, 10:25 UTC≈18,200 views21 reactionsread 15 August 2026

📣📣📣重要通知‼️: 提升担保服务品质,我们在行动!所谓担保说白了就是交易安全,作为担保的一员,我们深知每一笔交易背后都承载着信任与期待。为了让大家的资金交易更加的安全可靠,我们对此作出了以下调整: 🔥中信担保即将更换新地址🔥 旧地址TFzyEWZeCiyRRovxgvMtuSQT7C4BX2E7Ae 新地址THXmnmmxAE76KYHmiQ2DUwXkDJFm7xYjbS 各位亲爱的会员发布充值/上押开群请认准新地址。 所有资金一分不少即将转移到新地址,中信上压百分百放心,我们坚决抵制任何假押在任何一个中信担保的公群里做业务若是公群老板跑路,我们都会全额赔付,中信担保为你保驾护航💙

9👍6👎4😁2

3 Jul 2024, 10:12 UTC≈15,300 views6 reactionsread 15 August 2026

📣📣📣中信担保公告: 我们的业务担保团队一直在默默耕耘,努力打造一个更完善的担保体系,业务处理一目了然!1️⃣将新增广告客服号 @zxdb03,各位发布广告请移步 @zxdb03 所有包月包周老客户都会对接好!2️⃣担保开群联系 @zxdb,专群1v1担保 @zxdb01 交易金额100u以下免费担保! 在tg有交易?怕跑路?别担心,我们客服团队都已经准备好了,无论是交易纠纷还是使用疑问,一建呼叫我们的客服团队,都是经过专业培训,不仅懂业务,更懂得如何让大家满意。就是确保大家在交易过程中遇到的任何问题都能得到及时、有效的解答和帮助。无论是操作上的疑问,还是交易中的担忧,有任何的建议或反馈都可联系我们! 中信担保相关工作人员: 【交易前仔细核查ID】 上押公群:@zxdb 专群担保:@zxdb01 纠纷处理:@zxdb02 广告发布: @zxdb03 推广负责: @zxdb04 付费供需:

5💯1

6 Jun 2024, 11:47 UTC≈11,600 views3 reactionsread 15 August 2026

😀😀😀😀😀😀😀😀😀😀 公群018粤湘国际白资收u上押10000u —————————— 公群编号:018 公群链接:https://t.me/+BtDmpNnfb6g2MmNl 验群通道:https://t.me/zxdb55/77 —————————— 🎉中信担保祝您发大财行大运! 😀😀😀😀😀😀😀😀😀

👍21

2 Jun 2024, 13:48 UTC≈12,700 views39 reactionsread 15 August 2026
Photo

‼️重要公告: 最近有人造谣说中信担保是租的4字ID? 最近有人造谣说中信担保是租的4字ID? 最近有人造谣说中信担保是租的4字ID? ❤️在这里澄清一下 中信担保有这个实力也有这个能力拥有4字ID、上面图片是2023年8月中信担保购买4字ID的记录!现ID已价值二十几万人民币 ✅中信担保 成立于2022年11月,成立至今,担保金额达致2000万!已帮助数千人完成交易担保,波场链交易地址可查,避免遇到不良商家,在飞机上当受骗! 💰担保收款地址:🔻点击复制TFzyEWZeCiyRRovxgvMtuSQT7C4BX2E7Ae 中信担保推广花费了大量时间与精力去投放广告,招了一批又一批的推广员推广,又花了大量资金开发各种机器人服务大众推广和引流,覆盖飞机的各行各业群发与私信宣传,吸纳各行各业的老板精英!只为做好中信担保 因为自己淋过雨,所以想为别人撑伞! ——中信担保🔰 想交易?怕被骗?那就找中信担保为你保驾护航!🔰

21👍11💩3👎2🤮2

1 Jun 2024, 15:21 UTC≈19,200 views3 reactionsread 15 August 2026

😀😀😀😀😀😀😀😀😀😀 公群050乔姐烟业主打置换品质 上押300u —————————— 公群编号:050 公群链接:https://t.me/qiaojie66 验群通道:https://t.me/zxdb55/77 —————————— 🎉中信担保祝您发大财行大运! 😀😀😀😀😀😀😀😀

2👍1

31 May 2024, 12:40 UTC≈15,200 views4 reactionsread 15 August 2026

😀😀😀😀😀😀😀😀😀😀 公群049 大洲-代开会员/出售飞机号/出租888 上押300u【已退押】 —————————— 公群编号:049 公群链接:https://t.me/bbbapi 验群通道:https://t.me/zxdb55/77 —————————— 🎉中信担保祝您发大财行大运! 😀😀😀😀😀😀😀😀

3👍1

31 May 2024, 11:56 UTC≈16,700 views0 reactionsread 15 August 2026

😀😀😀😀😀😀😀😀😀😀 公群048万鸿售卖飞机号/代开会员/+888出租 上押500u —————————— 公群编号:048 公群链接:https://t.me/WH8448 验群通道:https://t.me/zxdb55/77 —————————— 🎉中信担保祝您发大财行大运! 😀😀😀😀😀😀😀😀

30 May 2024, 08:00 UTC≈10,300 viewsread 15 August 2026

😀😀😀😀😀😀😀😀😀😀 公群046银河兼职电销 微信语音 上押400u 已退押 —————————— 公群编号:046 公群链接:https://t.me/+CdKDlF_yV5pjOTI1 验群通道:https://t.me/zxdb55/77 —————————— 🎉中信担保祝您发大财行大运! 😀😀😀😀😀😀😀😀

Showing the 12 most recent of 19 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

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

“中信担保上压(公群列表)@zxdb” (@zxdb55), 10,402 subscribers as measured 17 August 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.