Telegram RegisterThe public register of Telegram
Telegram profile photo for 钻石担保官方 @ZuanShi 💎

Channel

钻石担保官方 @ZuanShi 💎

@zuanshi

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

24,376subscribers

-15,888 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-1001066288604
TypeChannel
Username@zuanshi
Description一键收藏💎钻石担保 https://t.me/addlist/BSQcujguV2szYzY0 唯一客服 @ZSDB 钻石公群 @ZSGQ 钻石供需 @ZSGX 钻石官方 @ZuanShi
Created21 July 2016 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live10 November 2026
Measurements held62
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/zuanshi

Topic

Marketing & affiliate — 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 50% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 4 other registered channels. This entry also sits inside a group of 5 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@zuanshi/3118 · this entry9 Aug 2026, 03:33 UTC@ysys/26809 Aug 2026, 03:34 UTC1.00under a minute
@zuanshi/3120 · this entry10 Aug 2026, 03:33 UTC@ysys/268310 Aug 2026, 03:34 UTC1.00under a minute
@ysys/269512 Aug 2026, 03:32 UTC@zuanshi/3124 · this entry12 Aug 2026, 03:32 UTC1.00under a minute
@ysys/270114 Aug 2026, 03:31 UTC@zuanshi/3128 · this entry14 Aug 2026, 03:31 UTC1.00under a minute
@zuanshi/3130 · this entry16 Aug 2026, 03:55 UTC@ysys/270916 Aug 2026, 03:55 UTC1.00under a minute
@zuanshi/3131 · this entry17 Aug 2026, 01:57 UTC@ysys/271117 Aug 2026, 01:57 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@ysys21 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (16–5)
@gaoxin10 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (8–2)
@onix9 (8/8 hand-verifiable sample passed)1.0072 seconds@onix (5–4)
@ysdb6 (6/6 hand-verifiable sample passed)1.00under a minute@ysdb (6–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 18 of the 18 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 42 comparable posts for this entry, running 8 December 2025 to 8 October 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 5 channels, the one whose matching posts we hold earliest is @ysys. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 5 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

19,82940,26430,046.524,3767 August 202610 November 2026
62 measurements spanning 95 days, net -15,888. 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 16,764–43,329 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 62
Measured (UTC)SubscribersChange
10 Nov 2026, 11:1124,376-19
8 Nov 2026, 21:4924,395+3
7 Nov 2026, 15:0124,392-112
6 Nov 2026, 15:0624,504-1
5 Nov 2026, 14:4824,505+29
4 Nov 2026, 16:5924,476-27
3 Nov 2026, 13:4724,503+36
2 Nov 2026, 16:4624,467+90
1 Nov 2026, 17:2924,377+85
31 Oct 2026, 15:4424,292+9
30 Oct 2026, 19:0824,283-100
29 Oct 2026, 17:5424,383+2
28 Oct 2026, 16:0824,381-15
27 Oct 2026, 17:5824,396+55
26 Oct 2026, 15:3624,341+46
25 Oct 2026, 13:3924,295-51
24 Oct 2026, 10:5624,346-12
23 Oct 2026, 11:0724,358+23
22 Oct 2026, 08:0724,335-33
21 Oct 2026, 00:5924,368first reading

Engagement

44 posts held, back to 21 July 2016 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 129 pages of 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 44 posts for this entry, the most recent from 8 October 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Videos
2
Links
4

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

Video runtime
5m 07s
Average length
11s

Measured directly from 29 videos 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

8 Oct 2026, 14:06 UTCviews —

钻石担保官方 @ZuanShi 💎 pinned «😃😃😃😃 近日接获多起通报,已有专门团伙假冒钻石公群相关负责人员与公群频道,请大家务必认明真正钻石公群!以免受骗上当! 💎钻石恒久远 担保永流传 ⭐不用到处找 一键收藏钻石担保 【机器人】 😃唯一验证 @ZSDB 🔰超级群管 @CBOT 【官方频道】 ⚡️钻石公群 @ZSGQ 💎新群电报 @YSDB 💍福利基地 @YSYS 💎钻石官方 @ZuanShi 💎钻石供需 @ZSGX 🌟超级供需 @LALA 📣永盛供需 @ONIX 【工作人员】 💎公群负责人 @SSLL 💎供需负责人 @SSFF…»

8 Oct 2026, 14:06 UTC≈7,560 viewsread 11 November 2026

😃😃😃😃 近日接获多起通报,已有专门团伙假冒钻石公群相关负责人员与公群频道,请大家务必认明真正钻石公群!以免受骗上当! 💎钻石恒久远 担保永流传 ⭐不用到处找 一键收藏钻石担保 【机器人】 😃唯一验证 @ZSDB 🔰超级群管 @CBOT 【官方频道】 ⚡️钻石公群 @ZSGQ 💎新群电报 @YSDB 💍福利基地 @YSYS 💎钻石官方 @ZuanShi 💎钻石供需 @ZSGX 🌟超级供需 @LALA 📣永盛供需 @ONIX 【工作人员】 💎公群负责人 @SSLL 💎供需负责人 @SSFF 💎纠纷仲裁官 @ZiZi 💎专群负责人 @Bros 【钻石隶属】 🔍超级索引 @CJSY 🌟官方频道 @SSYQ 集团旗下 【高新大群】 ✅超级同省 @GaoXin(原汇旺高薪)

9 Sept 2026, 18:42 UTC≈11,300 viewsread 11 November 2026

押金不是越多越好,适合自己才最重要 从当年的汇旺,到如今的新币。 一次次行业风波都在告诉我们:树大招风,人怕出名猪怕壮,枪打出头鸟!担保平台没有绝对安全的,资金过度集中本身就是风险。 所以钻石想提醒所有公群老板: 不要攀比押金,量力而行。 500U就做500U的业务,1000U就做1000U的业务,根据自己的真实业务量合理上押。 生意好不好,从来不是看谁押金多。 真正好的担保,无论押金多少,都应该有流量、有生意。 即日起,转移入驻钻石担保的符合条件公群,可享:800U 资金扶持,可用于供需广告、购买管理、超级索引 @cjsy 广告位等推广消费。 少一点押金攀比,多一点资金安全。 💎钻石恒久远|担保永流传! —— 钻石担保

1 Sept 2026, 01:39 UTC205 viewsread 1 September 2026

😃😃😃😃 提醒您: 😃公群2795 供押500u 全网最稳微信im 话术不死号 量最大 🧧 超狂钻石活动红包将于😄😄:😄😄发放! 😃公群211 供押550u 【租号换钱•诚达公司《咸鱼代聊/PCZM》超强续租•不掉一直续】 🧧超狂钻石活动红包将于😄😄:😄😄发放! 💎 钻石福利限时放送 🎁 幸运惊喜持续掉落 🧧请于当日00:00前领取红包后联系 @ssll 领取活动钻石,过时不统计。 关注钻石官方 @zuanshi,每天预告发红包位置 关注钻石公群导航 @ZSGQ,最新做单情报,尽在这里! 😃😃😃😃😃😃 钻石久远,富贵永恒

31 Aug 2026, 03:01 UTC213 viewsread 31 August 2026
Video

😃😃😃😃 提醒您: 😃公群013 供押1202u 租咸鱼QQ微信小红书 🧧 超狂钻石活动红包将于😄😄:😄😄发放! 😃公群030 供押555U 微信三人群兼职数据全网最高价28-35 普v模式 🧧超狂钻石活动红包将于😄😄:😄😄发放! 💎 钻石福利限时放送 🎁 幸运惊喜持续掉落 🧧请于当日00:00前领取红包后联系 @ssll 领取活动钻石,过时不统计。 关注钻石官方 @zuanshi,每天预告发红包位置 关注钻石公群导航 @ZSGQ,最新做单情报,尽在这里! 😃😃😃😃😃😃 钻石久远,富贵永恒

29 Aug 2026, 05:40 UTC397 viewsread 30 August 2026
Video

😃😃😃😃 提醒您: 😃 公群033 供押500u 小婷专注租咸鱼快手支付宝全网天花板 🧧 超狂钻石活动红包将于😄😄:😄😄发放! 😃公群024 供押500u 宇宇盘口直招微信ZM PC 闲鱼 小红书公群 🧧超狂钻石活动红包将于😄😄:😄😄发放! 💎 钻石福利限时放送 🎁 幸运惊喜持续掉落 🧧请于当日00:00前领取红包后联系 @ssll 领取活动钻石,过时不统计。 关注钻石官方 @zuanshi,每天预告发红包位置 关注钻石公群导航 @ZSGQ,最新做单情报,尽在这里! 😃😃😃😃😃😃 钻石久远,富贵永恒

28 Aug 2026, 04:48 UTC195 viewsread 28 August 2026
Video

😃😃😃😃 提醒您: 😃 公群444 供押508u 沐金高价收微信群聊 【保底3000➕】 🧧 超狂钻石活动红包将于😄😄:😄😄发放! 😃公群1234 供押500U 太子苹果id贷款 | 10元利息 | 全网最低 🧧超狂钻石活动红包将于😄😄:😄😄发放! 💎 钻石福利限时放送 🎁 幸运惊喜持续掉落 🧧请于当日00:00前领取红包后联系 @ssll 领取活动钻石,过时不统计。 关注钻石官方 @zuanshi,每天预告发红包位置 关注钻石公群导航 @ZSGQ,最新做单情报,尽在这里! 😃😃😃😃😃😃 钻石久远,富贵永恒

27 Aug 2026, 05:01 UTC175 viewsread 27 August 2026
Video

😃😃😃😃 提醒您: 😃公群663 供押668u 鸿运集团租/闲鱼代聊/云机/四百分秒上 🧧 超狂钻石活动红包将于😄😄:😄😄发放! 😃公群887 供押1200U 金蟾集团超长续租 微信/QQ/闲鱼/视频号/淘宝/抖音 (钻石最稳续租集团) 🧧超狂钻石活动红包将于😄😄:😄😄发放! 💎 钻石福利限时放送 🎁 幸运惊喜持续掉落 🧧请于当日00:00前领取红包后联系 @ssll 领取活动钻石,过时不统计。 关注钻石官方 @zuanshi,每天预告发红包位置 关注钻石公群导航 @ZSGQ,最新做单情报,尽在这里! 😃😃😃😃😃😃 钻石久远,富贵永恒

26 Aug 2026, 04:39 UTC202 viewsread 26 August 2026
Video

😃😃😃😃 提醒您: 😃公群550 供押500u Gapay-跑分(窗口公群) 🧧 超狂钻石活动红包将于😄😄:😄😄发放! 😃公群2026 供押1000u【招闲鱼代聊400起 秒死补200 租Q优选【发财集团】 🧧超狂钻石活动红包将于😄😄:😄😄发放! 💎 钻石福利限时放送 🎁 幸运惊喜持续掉落 🧧请于当日00:00前领取红包后联系 @ssll 领取活动钻石,过时不统计。 关注钻石官方 @zuanshi,每天预告发红包位置 关注钻石公群导航 @ZSGQ,最新做单情报,尽在这里! 😃😃😃😃😃😃 钻石久远,富贵永恒

25 Aug 2026, 04:16 UTC209 viewsread 25 August 2026
Video

😃😃😃😃 提醒您: 😃公群021 供押500U 12 代开会员 🧧 超狂钻石活动红包将于😄😄:😄😄发放! 😃公群8001 供押1000u 广纳集团回收手机卡 🧧超狂钻石活动红包将于😄😄:😄😄发放! 💎 钻石福利限时放送 🎁 幸运惊喜持续掉落 🧧请于当日00:00前领取红包后联系 @ssll 领取活动钻石,过时不统计。 关注钻石官方 @zuanshi,每天预告发红包位置 关注钻石公群导航 @ZSGQ,最新做单情报,尽在这里! 😃😃😃😃😃😃 钻石久远,富贵永恒

24 Aug 2026, 05:29 UTC167 viewsread 24 August 2026
Video

😃😃😃😃 提醒您: 😃公群031 供押500u 网页注册实名40一单秒结纯绿 🧧 超狂钻石活动红包将于😄😄:😄😄发放! 😃 公群3888 供押500u 枯萎电话通知 🧧超狂钻石活动红包将于😄😄:😄😄发放! 💎 钻石福利限时放送 🎁 幸运惊喜持续掉落 🧧请于当日00:00前领取红包后联系 @ssll 领取活动钻石,过时不统计。 关注钻石官方 @zuanshi,每天预告发红包位置 关注钻石公群导航 @ZSGQ,最新做单情报,尽在这里! 😃😃😃😃😃😃 钻石久远,富贵永恒

23 Aug 2026, 05:23 UTC193 viewsread 23 August 2026
Video

😃😃😃😃 提醒您: 😃公群8888 供押521u 小荔枝租咸鱼首选高价咸鱼代聊 租微信 🧧 超狂钻石活动红包将于😄😄:😄😄发放! 😃 公群123 供押500u 小呆白料手机口下课秒结账(下课1分钟内结账) 🧧超狂钻石活动红包将于😄😄:😄😄发放! 💎 钻石福利限时放送 🎁 幸运惊喜持续掉落 🧧请于当日00:00前领取红包后联系 @ssll 领取活动钻石,过时不统计。 关注钻石官方 @zuanshi,每天预告发红包位置 关注钻石公群导航 @ZSGQ,最新做单情报,尽在这里! 😃😃😃😃😃😃 钻石久远,富贵永恒

Showing the 12 most recent of 44 posts we hold for @zuanshi. 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

@zuanshi edited 1 post 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
26 September 2026
Most recent edit
26 September 2026

Posts recorded as deleted after publishing

We recorded 4 posts on @zuanshi as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
8 August 2026
Most recent seen missing
9 August 2026
Median time before seen missing
23 hours
Seen missing in the last 30 days
0

Mentions

Named by 5 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.

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

“钻石担保官方 @ZuanShi 💎” (@zuanshi), 24,376 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/zuanshi.

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.