Channel

仲裁频道

@zhongcai

2 usernames

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

36,156subscribers

+154 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID	-1002598355975
Type	Channel
Usernames	@xbzcpd @zhongcai
Description	永不失联官网 xinbi.com 公群导航 @gqdh 备用: @xbdh 供需频道 @abcd 备用: @xbgx 公告频道 @gonggao 官方大群 @xbdb 新开公群 @gong 新彩娱乐 @xincai 新币招商 @xinbei 24小时在线客服 @xbkf 新币每日福利群 @zzzz 新币搜索机器人 @xbso
Created	Between 1 March 2025 and 20 May 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	6 August 2026
Last confirmed live	15 August 2026
Measurements held	17
Confirmed unchanged	1 time, most recently 15 August 2026
On Telegram	t.me/zhongcai

Growth

17 measurements spanning 8 days, net +154. 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 35,978–36,186 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
15 Aug 2026, 06:37	36,156	-6
14 Aug 2026, 19:14	36,162	+35
14 Aug 2026, 01:14	36,127	+5
13 Aug 2026, 09:47	36,122	-32
12 Aug 2026, 23:05	36,154	+18
12 Aug 2026, 13:05	36,136	+14
12 Aug 2026, 00:17	36,122	+20
11 Aug 2026, 13:46	36,102	+26
11 Aug 2026, 02:01	36,076	+14
10 Aug 2026, 12:31	36,062	+39
9 Aug 2026, 23:34	36,023	-3
9 Aug 2026, 14:14	36,026	-9
8 Aug 2026, 19:51	36,035	no change
8 Aug 2026, 16:28	36,035	+2
7 Aug 2026, 19:53	36,033	+6
7 Aug 2026, 16:20	36,027	+25
6 Aug 2026, 22:46	36,002	first reading

Engagement

20 posts held, back to 20 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 11 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 4 March 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links: 2

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

351 reactions across 19 posts, in 12 distinct kinds. The most used accounts for 85.2% of them.

Every reaction kind recorded on the sample, most used first
Reaction	Count	Share
❤	299	85.2%
👍	28	7.98%
😁	6	1.71%
🥰	6	1.71%
🔥	2	0.57%
😇	2	0.57%
😎	2	0.57%
🤯	2	0.57%
🎃	1	0.285%
👌	1	0.285%
👎	1	0.285%
👏	1	0.285%

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 19 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 351reactions 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 20 May 2025 to 4 March 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

4 Mar 2026, 01:19 UTC≈48,100 views59 reactionsread 15 August 2026

[仲裁规则001——公群打超跑路] [仲裁规则002——上押退押规则] [仲裁规则003-中间人套路] [仲裁规则004-车队跑路] [仲裁规则005-担保佣金] [仲裁规则006——专群拉多个料主] [仲裁规则007-公审] [仲裁规则008-回错u] [仲裁规则009-专卡专用及一笔一卡相关纠纷解释] [仲裁规则010-料规则问题] [仲裁规则011-纯bc类规则问题] [仲裁规则012-车队非柜问题] [仲裁规则013-打超问题] [仲裁规则014-打超查料扯皮等问题] [仲裁规则015-私聊回帐回款等问题] [仲裁规则016-关于订单取消料方回复1 的问题] [仲裁规则017-关于入金金额不符的问题] [仲裁规则018-关于保料司法24、48、72小时的问题] [仲裁规则019-人头卡商公群中介诉求卡费等问题] [仲裁规则020-冒充银监会征信为由的贷款] [仲裁规则021-关于飘帐问题] [仲裁规则022-资金盘和配…

❤44🥰6😁4👍2🤯2👎1

Signed 新币仲裁kk

20 Nov 2025, 06:06 UTC≈51,500 views44 reactionsread 15 August 2026

[仲裁规则043——关于会议车、引导车等常见责任划分问题] 针对会议车、引导车等纠纷，为保证双方利益，减少此类偷鱼或杀车的恶意行为，即日起： 1/引导出金方式及限额：要以公群报备时或专群对接时的引导方式为准。出金方式是实物产品、京东、店铺、微信或综合出金，都应在报备时注明限额和出金方式；以免因引导方式不同多吃汇率差而导致不必要的纠纷。因出金方式或出金的限额大小而出的纠纷，以双方实际对接和约定判定责任。出金方式与报备方式不符，最低罚款500u，最高没收全部押金。 2/建议要有完善的规则：车队押金加到5000u以上，提升作案成本；且规则中可以附加上：善后还必须要录视频，没有善后或引退视频就是偷鱼，就可以直接定责，车方全责。另规则中要有料性的约定。 3/车方引导时，当鱼出金了多少，云客服里要先跟鱼确认出了多少，并截图反馈给料方，然后再善后删记录。即使删除后要先截图给前台，或教会鱼录制这些删除的视频，更方便找到问题所在；另，料…

❤41🔥2👏1

Signed 新币仲裁vv

20 Nov 2025, 06:06 UTC≈38,200 views22 reactionsread 15 August 2026

[仲裁规则042——关于二道保时司法情况说明] 1，二道作业时双方约定保时方式例如保双向司法或以头卡等为主，及赔付约定卡余不大于单笔等等。处理按照双方约定保时方式及赔付规则处理。没有所谓只看第一司法，只对自己入款的资金有无保住司法负责。 2，在未保住司法时，如有不同头卡但同鱼入款头卡且该头卡也司法，看二道是否有该鱼问题司法。如有，即可都按照未保住处理，因为同鱼司法也不会在二道中重复去录入，所以不限于天眼上反馈的某一笔问题流水司法。 3，公交卡/商家卡中常出现存在多笔未保住情况，若未保住赔付卡余部分不超过单笔时，应按照未保住部分入款先后顺序从后往前依次分配赔付不超过卡余部分。（例如卡余10万，分别有3笔8万金额未保住，应从最后一笔开始减卡余部分依次往前计算。总赔付不应超过卡余部分） 5，考虑二道作业方式保时周期长，对于先下发的不受未约定先下发不处理限制，可正常按照追溯制度处理。或亦可风控押金等待过保下发。 6，该规则不包…

❤18👍2😁2

Signed 新币仲裁vv

3 Sept 2025, 17:50 UTC≈42,500 views28 reactionsread 15 August 2026

[仲裁规则041——关于专群邮寄卡取现卡遗失赔付问题] 因可能存在不安全或不可控的外部因素，需方每次邮寄卡前，均须与供方共同确认收货地址、发货数量，注明邮寄XX银行的卡XX张等。需方不得在供方不知情的情况下擅自将卡片寄至供方地址。 1，若未提前通知供方确认即自行邮寄的，供方有权拒收快递并不计入赔付。 2，快递以实际收到为准，供方应在拆包时录制一镜到底的开箱视频作为验货凭证。运输途中如出现快递丢失、货品不符等情况，相关责任由需方承担。 3，正常情况下对于卡片的遗失赔付标准为：对于未使用卡片的丢失赔付不超过300U/张，已使用但卡态正常的情况下赔付不超过200U/张。已使用且卡死或未使用前卡已死的情况下不计入赔付。 4，如因车方自身原因导致取件时被摁遗失，赔付不超过100U/张。

❤23👍4🎃1

Signed 新币仲裁vv

5 Jul 2025, 12:58 UTC≈38,500 views30 reactionsread 15 August 2026

[仲裁规则040——关于近期支付宝付款方开启保护的问题] 因近期支付宝风控让付款方开启资金保护，导致收款方需等24小时资金解冻才可使用，统一如下处理规则：供方发现保护冻结，应及时告知需方并提供凭证。双方协商处理：可以沟通叫鱼撤回，或维护24小时等到账按拖算处理。如期间鱼死则不需要回款，钱死提供完整的视频证明。另：如果双方作业无视24保护，应单独列出来双方确认，可不按该条担保规则处理。

❤20👍10

Signed 新币仲裁vv

20 May 2025, 07:30 UTCviews —

仲裁频道 pinned «新币官方公示名单： https://t.me/guanfangxb/45»

20 May 2025, 07:28 UTC≈37,100 views5 reactionsread 15 August 2026

[仲裁规则039——娱乐类专群打超赔付规则] 押金内作业，切勿超押作业。此类作业不受理追溯！ 1，供方押金小于多需方总下注金额时，按照需方下注的先后顺序计算，超出外的不计入输赢！ 2，供方押金大于多需方总下注金额时，需方不能超出自身押金下注如超出或最后交收超过自身押金，按自身押金封顶计算！ 3，该规则于5月17日起执行。

❤5

Signed 新币仲裁w

20 May 2025, 07:28 UTC≈21,500 views8 reactionsread 15 August 2026

[仲裁规则036-关于保当天保24小时等反馈司法问题] 近期多发保时内先行下发后反馈未保住反馈的问题。现将该问题制定如下规则： 1，保当天或24小时司法等，反馈时间延迟至保时后约定XX小时内反馈有效，没有约定时间的，一律延迟至保时后12小时内反馈，由于查司法时间的特殊性，有些需要隔天才能查出并在时效内反馈。 2，对于先行下发后反馈的，下发之前应提前对接说明多久时间反馈内有效，并可追溯（请在担保群内双方确认，避免私聊删除记录） 3.如保时内先行下发且未沟通确认后期多久反馈有效时，供方自行承担损失。警示；进款后等待保时后下发的，应及时联系担保风控该笔资金或找担保拉小群上押等待，避免超押跑路

❤8

Signed 新币仲裁w

20 May 2025, 07:28 UTC≈19,300 views7 reactionsread 15 August 2026

[仲裁规则027-关于新币纠纷追溯问题] 所有新币担保用户都知道有追溯机制，纠纷，跑路，等问题担保收取追溯金额的30%追溯费用。由于业务量激增，有很多纠纷追溯时间过长，有的甚至半年一年多，第一不好核实，第二记录如果不在容易扯皮。现规定追溯期时间时限为60天，超过60天的不予追溯。

❤7

Signed 新币仲裁w

20 May 2025, 07:28 UTC≈19,400 views8 reactionsread 15 August 2026

[仲裁规则026-关于料不对版时间查询问题] 1.料方需方打料给车队供方查司法空时最高时间给7天时间查料，料方打款时间算起。如果7天时间到查询司法还是空车队供方回款 2.白资群现存受害人现存款一道直流查询核实给最高15天这种全扣人头卡取款现金存买U A取A存最高给于15天查询卡无司法回款有冻结风控止付配合解除后给适当补偿 3.料方打款时间算起【最长查料期限7天】。3天查询时间内司法还是空，3天后如继续查询按照计算纠纷款1%的误工费与料方计算，查实料不符则不用给误工费，此期间纠纷金额与误工费必须上押担保方！（白资群除外）

❤8

Signed 新币仲裁w

20 May 2025, 07:28 UTC≈34,100 views41 reactionsread 15 August 2026

[仲裁规则038-关于拿现/丢包/邮寄等线下交易问题] 一、料方须留存证据 1. 完整切客记录 + 现场放货视频/照片（1小时内） 2. 取款证明 + 打包视频（24小时内） 3. 鱼个人信息（48小时内私发当值仲裁） ⚠️料方无法提供相关有效切客和鱼的身份信息，导致纠纷无法进一步核实处理，按实际情况判定承担相关责任并进行处罚二、车方须留存证据（1小时内） 1. 车头引导鱼的对接记录录屏 2. 多角度现场监控视频 3. 一镜到底的鱼走鱼放完整视频 4. 一镜到底的取手拿货验货视频 • 取手被摁：4小时内提供身份信息，5日内提供纸质证明 • 大病情况：48小时内出具相关病例 ⚠️车队方无法提供相关有效监控视频和取手相关身份信息，导致纠纷无法进一步核实处理，按实际情况判定承担相关责任并进行处罚三、车方建议预防措施 • 无人机录制现场全程 • 夜间交易配备夜视摄像头 • 丢包模式放货地点加装带锁铁箱，鱼放包后上锁离开，附近隐…

❤33👍5😇2👌1

Signed 新币仲裁w

20 May 2025, 07:28 UTC≈24,400 views21 reactionsread 15 August 2026

[仲裁规则037-关于一进一拉的问题（车队超压问题解释）] 1：一进一拉的卡，需方同时进卡相隔10秒内，车队超压跑路供方全责，不认供方任何理由，和车队聊天记录。 2：如果因为一进一拉，A需方先进卡，B需方进款时间和A需方相隔时间一致，供方拉停，供方贴卡时明确有和需方说，一进一拉，不是专卡，路上有类似字眼，需方还继续进卡说明需方有能力随时拉停如果没有及时拉停需方自己负责，供方无责。如01进了5万 03进了4万按照进款的顺序拖出多少回多少 3：如果一进一拉的卡和料方说是专卡，又一卡多贴，公群拉停后进的钱，钱离卡了，供方全责，钱死最少认一半，拖出全回。 4：本条规则只适用于打一笔的取现卡不适用于一道二道等。另补充一点打拖算的规则只要是钱不离卡不管是什么原因导致出不去的只要不离卡那就不赔付。进算规则，拉停后进款附言或多打了金额双方沟通确认拖算的情况下只要钱不离开人头名下一律按照没有拖出算

❤16👍3😎2

Signed 新币仲裁w

Showing the 12 most recent of 20 posts we hold for @zhongcai. 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 — 243,847 of 1,480,688entries 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 3 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.

Named by

Channels on the register whose posts name this channel's handle.

新币官方频道 @xinb
@xinb · 216,57719 posts 公群商户培训
@xbgqsh · 46,06114 posts 专群流程频道
@zhuanqunxb · 58,2434 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 August 2026 — this entry's latest reading, not the date you are reading this.

“仲裁频道” (@zhongcai), 36,156 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/zhongcai.

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.