4 Jun 2025, 15:48 UTCviews —
Channel name was changed to «王者担保 新闻（吃瓜爆料）仲裁 悬赏 投稿 曝光»
Channel
王者担保 新闻（吃瓜爆料）仲裁 悬赏 投稿 曝光
@wzdb11
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,249subscribers
-43 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001861331494 |
|---|---|
| Type | Channel |
| Username | @wzdb11 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/wzdb11 |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 62% 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 |
|---|---|---|
| 15 Sept 2026, 04:57 | 1,249 | -3 |
| 11 Sept 2026, 19:17 | 1,252 | -8 |
| 7 Sept 2026, 16:58 | 1,260 | -9 |
| 2 Sept 2026, 07:46 | 1,269 | -4 |
| 30 Aug 2026, 12:07 | 1,273 | -4 |
| 27 Aug 2026, 14:25 | 1,277 | -2 |
| 24 Aug 2026, 22:46 | 1,279 | -4 |
| 20 Aug 2026, 23:24 | 1,283 | -6 |
| 17 Aug 2026, 20:47 | 1,289 | -3 |
| 14 Aug 2026, 16:06 | 1,292 | no change |
| 14 Aug 2026, 01:34 | 1,292 | first reading |
Engagement
16 posts held, back to 13 May 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 16 posts for this entry, the most recent from 4 June 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
3 Jun 2025, 16:55 UTC319 viewsread 14 August 2026
担保仲裁原则001：仲裁必看说明 担保仲裁原则002：常见料性 担保仲裁原则003：交易模式 担保仲裁原则004：质疑料性 担保仲裁原则005：中介套路 担保仲裁原则006：超押跑路 担保仲裁原则007：金额不符 担保仲裁原则008：拉停入款 担保仲裁原则009：私下交易 担保仲裁原则010：一道二道 担保仲裁原则011：地推结算 担保仲裁原则012：专卡模式 担保仲裁原则013：进算规则
3 Jun 2025, 16:25 UTC318 viewsread 14 August 2026
担保仲裁原则：进算规则 1、进算规则任意收款模式，资金正常交易抵达收款账户并未违反其他规则，资金在收款账户出现任何问题与料方无关，料方如违反规则或协议，应承担相应责任。 2、收料方带有三方充值渠道的，要跟料方讲清楚，如未讲清楚导致资金卡三方充值渠道，收料方要承担相应的责任。 3、目前市场很多进算资金，保时司法的交易模式，此种交易只适合专群交易，收料方收到资金后立即回款，料方与收料方协商，上押保时司法的押金。 （2025年6月4日 更新）
3 Jun 2025, 16:25 UTC257 viewsread 14 August 2026
担保仲裁原则：专卡模式 1、公群或专群交易专卡模式，交易双方要明确约定好是否为专卡，约定内容包括保量、赔偿、卡费等协议规则（规则内必须明确表示为专卡交易，不得以其他不明确词语代替）。 2、交易前要约定好是否保量，如没有约定料方无需赔付卡费。约定好料方没有达到标准按照约定或协议好的规则赔付，因保时冻结没有达到保量料方需最低赔偿卡费+卡内余额。 3、专卡模式只能为自己协议好的交易客户排卡，车队如把此卡排给交易客户以外的料方所造成的后果车队需赔偿料方（双方约定好协议规则赔偿的按照协议规则处理，未协议的按照市场最低标准赔偿）。 （2025年6月4日 更新）
3 Jun 2025, 16:24 UTC196 viewsread 14 August 2026
担保仲裁原则：地推结算 1、双方交易是需审核投放量的，优先以客户的投放视频为准，公群可扣除有问题的单后结算正常部分，不可以找不正当理由全部不予结算。 2、双方交易需审核访问量/下载量的，优先以公群后台数据为准（公群应在后台直接刷掉同ip访问或下载量，不可找理由说刷假数据不予结算） （2025年6月4日 更新）
3 Jun 2025, 16:24 UTC185 viewsread 14 August 2026
担保仲裁原则：一道二道 禁止着急卸货乱入。 1、一道公群禁止进二道料，公群明确说明可以进料方无责，公群未同意进款料方全责。 2、二道公群禁止进一道料，公群明确说明可以进料方无责，公群未同意进款料方全责。 （2025年6月4日 更新）
3 Jun 2025, 16:23 UTC170 viewsread 14 August 2026
担保仲裁原则：私下交易 1、私下交易导致纠纷，本平台不予受理，私下交易导致群老板跑路，平台不予任何赔付，如有群老板诱导私下交易，请及时联系工作人员举报，证据确凿平台一律按诈骗处理，罚没公群押金。 2、私聊双向删除信息无法核实取证且无法证实哪方所为，交易双方需谨慎，交易期间卡号与地址一定要在公群内报备部分信息，防止一方恶意删除信息。 （2025年6月4日 更新
3 Jun 2025, 16:23 UTC156 viewsread 14 August 2026
担保仲裁原则：拉停入款/卡死 入款时车队叫停的情况分为多种，卡未死叫停比如预估额度将满、车队忙不过来需要等待或卡死叫停、卡风控叫停等视情况不同而定。 1、正常拉停后入款纠纷处理标准： 1）拉停5分钟（300秒）内入款资金冻结/未拖出，料方自行承担。 2）拉停5分钟（300秒）内入款资金正常拖出，车队方回款。 3）拉停5分钟（300秒）后入款，车队方可不查不认。 注解：拉停时间5分钟（如12:30:00叫停，12:34:59前都算，12:35:00之后属于超时入款） 2、卡死拉停车队方需第一时间提供卡状态，确定金额是否已拖出，搬砖如无法提供需查档。 3、对于恶意叫停以规则去侵吞客户入金的行为不予支持。 （2025年6月4日 更新）
3 Jun 2025, 16:23 UTC144 viewsread 14 August 2026
担保仲裁原则：金额不符 入多的、入少的、分笔入的、未按指定金额入的，全部包括在内。 1、一道可以少打不可以多打。少打的，但高于规则最低入款金额的进多少回多少，低于规则约定的最低入款金额的可以不查不认或只查不认。 2、特殊卡例如一道取现额度卡的，料方需要补偿叫卡金额跟实际入款金额之间的差值部分的利润，但不允许以金额不符明吃。 3、正常一道拼车卡，不允许以金额少打了为理由明吃，或者要求补偿利润。 4、一道多打的，叫卡金额部分按照规则内入金计算，超额部分按照私入算，可以不认（无需举证）。 5、二道需按照指定金额打款，未按照指定金额打款造成损失的视为全责。 （2025年6月4日 更新）
3 Jun 2025, 16:22 UTC134 viewsread 14 August 2026
担保仲裁原则：超押跑路 切记不要打超⚠️ 不要打超⚠️ 不要打超⚠️ 1、、公群跑路，仲裁人员会在收到消息时第一时间拉纠纷群，并在公群内通知相关用户处理，请在24小时内及时联系仲裁人员，群内业务无保时将会在3-7天内给出赔付方案，若有保时则需待最后一笔交易过保时后方可给出赔付方案（如有延期还请各位用户理解，仲裁人员会尽快给各位处理） （2025年6月4日 更新）
3 Jun 2025, 16:22 UTC127 viewsread 14 August 2026
担保仲裁原则：中介套路 专群交易一直有中介套路双方，造成一方损失中介拿钱跑路，为防止此类事件再次发生扯皮，王者在此声明，专群为一对一交易，群内只有交易双方人员和王者工作人员，拿钱跑路一方自行承担责任，押金下发需双方负责人确认清楚。 （2025年6月4日 更新）
3 Jun 2025, 16:22 UTC122 viewsread 14 August 2026
担保仲裁原则：质疑料性 1、入料不符，规则有约定的以规则为准（比如赔付单笔或者几倍赔付） 2、入料不符，规则未约定的默认扣除单笔（不包含三黑） 3、三黑【冒入】一直不可控，在收料方可以提供实质证据证明损失的情况下，优先按照当群规则处理，未明确写明规则，料方应赔偿收料方打款金额或卡内余额（哪个多赔付哪个）额外赔偿卡费（按照市场行情赔偿） 4、盒饭 红酒 建材规则外入款或不报备造成收料方损失一样按照三黑处理！ 5、料方有提供切客记录，供方质疑料性需自行查档取证，如收料方不愿意自行天眼查档并且料方不能提供料的证据，需双押天眼查档费用，最终以责任方负责，为另一方退回天眼查档费用。 6、料方无法给出证据表明料性，需等待天眼查档更新时间3个工作日，如需延时查料，按照第4个工作日开始每天1%的误工费与料方计算，查实料不符则不用给误工费，此期间纠纷金额与误工费必须上押担保方！【最长查料期限7个工作日】料符合收料方规则或仍是查空必须正…
Showing the 12 most recent of 16 posts we hold for @wzdb11. 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
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.
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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“王者担保 新闻（吃瓜爆料）仲裁 悬赏 投稿 曝光” (@wzdb11), 1,249 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/wzdb11.
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.