8 Jan 2026, 09:27 UTC≈1,100 viewsread 7 August 2026
跳转导航
Channel
仲裁规则
@zhongcaixm
2 usernames
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,441subscribers
+56 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002992068775 |
|---|---|
| Type | Channel |
| Usernames | @xmzc668 @zhongcaixm |
| Created | Between 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/zhongcaixm |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 03:06 | 1,441 | +2 |
| 14 Aug 2026, 08:16 | 1,439 | +16 |
| 11 Aug 2026, 11:22 | 1,423 | no change |
| 11 Aug 2026, 08:23 | 1,423 | +31 |
| 8 Aug 2026, 01:21 | 1,392 | no change |
| 7 Aug 2026, 22:53 | 1,392 | +7 |
| 7 Aug 2026, 10:16 | 1,385 | no change |
| 7 Aug 2026, 10:03 | 1,385 | first reading |
Engagement
20 posts held, back to 8 January 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 2 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 20 posts for this entry, the most recent from 8 January 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
4 reactions across 4 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 100.0% |
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 9 of the 20 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 4reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 8 January 2026 to 8 January 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
8 Jan 2026, 09:26 UTC≈1,060 viewsread 7 August 2026
仲裁原则028：纠纷期间单方失联 为保障纠纷处理的及时性与交易安全，交易双方在处理期间需持续关注群内消息并积极配合。若一方在规定时间内无响应，将被视为失联，并启动如下处理机制： 1、超押失联 若纠纷中上押方存在超押且失联，自平台发出“限时处理通知”起计算，最多等待24小时。超时仍未响应或配合的，平台将视其为主动放弃纠纷权利或涉嫌跑路，并接管押金处理。 2、不明原因失联 若纠纷中一方失联，如失联方无押金上押视情况最少等待3天最多等待7天，如失联方有押金上押或冻结的最多等待37天，超时未配合处理则视为放弃纠纷。在等待期届满后仍未配合，平台将视为自动放弃纠纷，进入押金接管程序。 3、接管处理 当一方失联超出等待时限后，平台将根据群内现有记录和证据，代为决定交易走向。双方应在等待期内积极提交相关证据。如因失联方未及时举证、配合或信息不全，导致平台接管后判断有误，由失联方自行承担后果。 （2026年1月8日 更新）
8 Jan 2026, 09:26 UTC707 views1 reactionsread 7 August 2026
担保仲裁原则027：收售手机卡业务 1、发货方和收货方都应录制好完整的一镜到底发货/收货视频 2、公群方有义务提醒客户在报备模板中备注好结算信息，如收件人号码、收件人地址、快递单号、结算钱包地址等信息，涉及隐私的信息，可部分用【***】代替，防止出现纠纷后，私下记录被删除或货物被第三方领取，双方无法举证核实。 3、交易双方有义务按照群规提供相应的证据，如拆包视频、测卡视频、快递面单信息、卡板信息等。 4、发货方货不对版，发货方全责；双方对于退款或是重新发货可自行协商。 5、收货方测卡不能使用，双方协商退回货物的，双方依旧要按照发货要求，准备好打包/发货/收货/拆包视频证据，以免出现后续纠纷，证据不足的一方占大部分责任。 5.1）公群收手机卡业务： 公群方给客户退回货物后，客户测卡反馈能正常使用，公群给予客户正常结算；反之无需结算。 5.2）公群售手机卡业务： 客户给公群方退回货物后，公群测卡反馈能正常使用，公群无需…
❤1
8 Jan 2026, 09:25 UTC466 views0 reactionsread 7 August 2026
担保仲裁原则026：手机口业务 严禁利用规则规避自身责任 1、客户上课时长不满足公群结算最低时长的，如果不是客户原因导致，公群需正常结算。 2、当客户存在违规行为的情况下，如若盘口给公群结算的，应给客户结算部分，不得以客户违规为由不给客户结算。 3、客户联系公群方申请结算时，公群方有义务提醒客户保存并提供相应的做工证明作为结算依据，不得以“晚点结算”、“统一结算”为由拖延结算时间，届时以客户没有在规则时限内提供结算依据为由不给客户结算。 4、认为客户炸鱼、转接等违规行为，公群方应给予相应的违规证据，不得以盘口不给证据为由利用规则不给客户结算。 5、在纠纷处理期间，客户有义务配合公群提供公群需要的运营商详单等证据，客户如无法提供应在交易前提前告知公群，双方确定风险后再交易。 （2026年1月8日 更新）
8 Jan 2026, 09:25 UTC407 viewsread 7 August 2026
担保仲裁原则025：公群商户群内广告 公群需要正常推广和运营，公群内常有优惠广告、福利任务等活动，平台不禁止，在此提醒客户谨慎交易。 1、公群内交易请认准公群置顶规则，平台按照公群规则为各位客户担保交易。 2、公群内广告为公群方推出的活动，不受平台担保，因广告或活动问题出现的纠纷不在担保范围。 3、平台不担保公群或个人的信誉，请大家遵守交易规则，按平台交易流程进行交易。若发现公群方利用广告欺诈客户的，可以收集好相关视频证据，联系平台工作人员举报。 （2026年1月8日 更新）
8 Jan 2026, 09:24 UTC354 viewsread 7 August 2026
担保仲裁原则 024： 搬砖/关联纠纷 1、纠纷案件一案一结。有关联群或关联纠纷，客户需提前告知仲裁人员相关联案件单独处理或关联处理。 2、关联案件只关联证据，不关联结果。因客户描述不清晰或证据提供不充足，导致关联案件仲裁/公审结果不一致，搬砖客户自行承担责任。 （2026年1月8日 更新）
8 Jan 2026, 09:24 UTC333 views1 reactionsread 7 August 2026
担保仲裁原则023：线下取现回U业务 上押金额与实际交易内容不符，群内规则视为无效规则，平台只处理上押金额与之匹配的交易内容纠纷，其他一概不处理。 1、对于双方只担保鸽子费的，平台仅担保双方是否见面，双方见面之后产生的一切交易纠纷不在担保范围内，且双方没有互相追溯的权利。 2、建议双方在协商的交易规则内，增加双方当面交易的时限，鱼和取手在规定好的交易时限内完成交易。因线下交易不可控的因素问题，双方从交易到结束，应自行保存相关交易的证据证明，出现纠纷时以双方提供的证据为判定依据。 3、取手信息必须提前群内公示（担心涉及隐私可以隐藏部分，完整信息需要私发交易员报备，出现纠纷以该取手天眼为准，请勿提供虚假信息）。 4、取手或鱼被按且无明确证据的，需双押查天眼，查档最长取证时间为37天。超出37天未更新证据，按群内现有证据给予处理结果。 5、因鱼醒的时间不确定，且鱼真假难以立即判定，因此与“鱼”相关的查档（如鱼口供）可根据以…
❤1
8 Jan 2026, 09:23 UTC293 views1 reactionsread 7 August 2026
担保仲裁原则022：进算规则 1、进算规则：资金正常交易抵达收款账户并未违反其他规则，资金在收款账户出现任何问题与料方无关，料方如违反规则或协议，应承担相应责任。 2、因付款方开启“支付保护”或类似资金到账后无法转出的限制，导致资金抵达收款账户就被冻结的，由料方承担相应责任。 3、使用鱼的资金代买实物等线下模式进算规则需保到货，代买的实物正常到货后收料方需正常回款。 ·如因鱼醒导致货物在运输或配送期间被退回，由料方承担相应责任。 ·如因收料方账号封控冻结，导致平台无法发货，由收料方承担相应责任。 4、收料方带有三方充值渠道的，要跟料方讲清楚满足进算的条件，如未讲清楚导致资金卡三方充值渠道等情况，由收料方承担相应的责任。 5、目前部分进算规则存在双方另行约定保时司法的情况，此种交易只适合专群交易，收料方可在交易前与料方协商上押保时司法的押金。 ·如料方押金不足赔付的，收料方可暂不回款，等待纠纷处理结束。 （2026年1…
❤1
8 Jan 2026, 09:19 UTC278 views0 reactionsread 7 August 2026
担保仲裁原则021：专卡模式 1、公群或专群交易专卡模式，交易双方要明确约定好是否为专卡，约定内容包括保量、赔偿、卡费等协议规则（规则内必须明确表示为专卡交易，不得以其他不明确词语代替）。 2、交易前要约定好是否保量，如没有约定料方无需赔付卡费。约定好料方没有达到标准按照约定或协议好的规则赔付，因保时冻结没有达到保量料方需最低赔偿卡费+卡内余额。 3、专卡模式只能为自己协议好的交易客户排卡，车队如把此卡排给交易客户以外的料方所造成的后果车队需赔偿料方（双方约定好协议规则赔偿的按照协议规则处理，未协议的按照市场最低标准赔偿）。 （2026年1月8日 更新）
8 Jan 2026, 09:04 UTC263 viewsread 7 August 2026
担保仲裁原则020：过桥资金 属于一种交易模式，鱼A给鱼B转账后取现再存给车，鱼B就属于桥（这种行为叫过桥） 搭桥模式： 1、一道：鱼A转账给鱼B，鱼B取现存款给车，并且鱼B自己的钱也会被盘口骗走的，不区分鱼B自己的钱是在做桥前被骗还是做桥后被骗，只要涉及鱼B自己的钱也被骗的都归于此类。 2、二道：鱼A转给鱼B，鱼B帮忙取现后存款给车，从始至终鱼B自己的钱没被骗的归于此类。 判定标准： 1、目前市场过桥资金基本都是鱼A转鱼B，鱼B取款后再存给车，交易双方应在规则写明保时多久。 2、过桥资金保时内鱼A或鱼B报警司法料方全责，过保时后鱼B报警收料方质疑一道直流料方提供搭桥证明后无需承担责任。 3、料方应跟收料方明确说清楚搭桥模式，不可隐瞒或误导进行交易。 （2026年1月8日 更新）
8 Jan 2026, 09:03 UTC249 views0 reactionsread 7 August 2026
担保仲裁原则019：无视料性 1、无视料包含：市场上常见的三黑料、红酒建材盒饭、大混+、大混、常规、大区、精聊、资金盘、bc、白资！ ⚠️注：（军火、毒资、绑架、涉恐资金不在无视料范围） 2、如群名群规出现无视料的字眼那么此群不可出现禁止料以及需要报备的料来诱导客户入金后不回款。 3、无视料不该出现禁止地区的限制，三黑料性已经是行业目前毒性最高的料性更不该有地区限制。 （2026年1月8日 更新）
8 Jan 2026, 09:03 UTC240 viewsread 7 August 2026
担保仲裁原则018：拖算规则 1、收料方必须在规则内写明脱出时间标准，并在交易前和料方定好脱出时间。 2、收料方如果卡限额或风控解除状态后，应立即脱出并回款（如在此期间卡死未拖出料方自行承担）。 3、拖算的汇率对比其他交易模式偏低，所以在选择此交易模式时料方应做好承担风险的准备，收料方也必须提醒料方各种风险提示。 4、因收料方不积极卸货导致拖出失败，收料方应承担相应责任（交易双方需提供相应的证据给予仲裁或公审判断）。 （2026年1月8日 更新）
Showing the 12 most recent of 20 posts we hold for @zhongcaixm. 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.
Citation-graph rank
Citation-graph rank — 759,322 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“仲裁规则” (@zhongcaixm), 1,441 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/zhongcaixm.
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.