Telegram RegisterThe public register of Telegram
Telegram profile photo for 仲裁频道

Channel

仲裁频道

@zhongcai

On this record: Topic · Previous handles · Growth · Engagement · Reactions · Posts · Cite this entry

37,484subscribers

+1,482 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
TypeChannel
Username@zhongcai
CreatedBetween 1 March 2025 and 20 May 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live9 September 2026
Measurements held56
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/zhongcai

Topic

Gambling & betting — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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.

Previous handles

@zhongcai was previously reachable at these 2 handles, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@xbzcpd
held 6 August 20266 August 2026
@zhongcai
held 6 August 20266 August 2026

Growth

36,00237,48436,7436 August 2026 — 36,002 subscribers7 August 2026 — 36,027 subscribers7 August 2026 — 36,033 subscribers8 August 2026 — 36,035 subscribers8 August 2026 — 36,035 subscribers9 August 2026 — 36,026 subscribers9 August 2026 — 36,023 subscribers10 August 2026 — 36,062 subscribers11 August 2026 — 36,076 subscribers11 August 2026 — 36,102 subscribers12 August 2026 — 36,122 subscribers12 August 2026 — 36,136 subscribers12 August 2026 — 36,154 subscribers13 August 2026 — 36,122 subscribers14 August 2026 — 36,127 subscribers14 August 2026 — 36,162 subscribers15 August 2026 — 36,156 subscribers16 August 2026 — 36,221 subscribers16 August 2026 — 36,238 subscribers17 August 2026 — 36,231 subscribers17 August 2026 — 36,231 subscribers18 August 2026 — 36,232 subscribers18 August 2026 — 36,295 subscribers19 August 2026 — 36,348 subscribers19 August 2026 — 36,348 subscribers20 August 2026 — 36,397 subscribers20 August 2026 — 36,455 subscribers21 August 2026 — 36,520 subscribers21 August 2026 — 36,520 subscribers22 August 2026 — 36,595 subscribers23 August 2026 — 36,595 subscribers24 August 2026 — 36,695 subscribers25 August 2026 — 36,721 subscribers25 August 2026 — 36,745 subscribers26 August 2026 — 36,785 subscribers26 August 2026 — 36,766 subscribers27 August 2026 — 36,837 subscribers27 August 2026 — 36,837 subscribers28 August 2026 — 36,898 subscribers28 August 2026 — 36,898 subscribers29 August 2026 — 36,909 subscribers29 August 2026 — 36,909 subscribers30 August 2026 — 36,881 subscribers30 August 2026 — 36,881 subscribers31 August 2026 — 36,937 subscribers31 August 2026 — 36,925 subscribers1 September 2026 — 36,970 subscribers1 September 2026 — 37,008 subscribers2 September 2026 — 37,040 subscribers2 September 2026 — 37,051 subscribers3 September 2026 — 37,109 subscribers3 September 2026 — 37,159 subscribers5 September 2026 — 37,175 subscribers5 September 2026 — 37,204 subscribers8 September 2026 — 37,365 subscribers9 September 2026 — 37,484 subscribers6 August 20269 September 2026
56 measurements spanning 33 days, net +1,482. 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,780–37,706 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 56
Measured (UTC)SubscribersChange
9 Sept 2026, 06:3937,484+119
8 Sept 2026, 16:0237,365+161
5 Sept 2026, 21:2037,204+29
5 Sept 2026, 07:0037,175+16
3 Sept 2026, 21:1437,159+50
3 Sept 2026, 09:1637,109+58
2 Sept 2026, 14:0637,051+11
2 Sept 2026, 01:1537,040+32
1 Sept 2026, 14:0537,008+38
1 Sept 2026, 03:5836,970+45
31 Aug 2026, 11:1336,925-12
31 Aug 2026, 06:1736,937+56
30 Aug 2026, 09:2736,881no change
30 Aug 2026, 05:3636,881-28
29 Aug 2026, 10:5836,909no change
29 Aug 2026, 07:2336,909+11
28 Aug 2026, 13:3436,898no change
28 Aug 2026, 10:3836,898+61
27 Aug 2026, 13:3736,837no change
27 Aug 2026, 09:3936,837first reading

Engagement

20 posts held, back to 20 May 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 53 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 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.

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
31485.8%
👍287.65%
😁61.64%
🥰61.64%
🔥20.546%
😇20.546%
😎20.546%
🤯20.546%
🎃10.273%
👌10.273%
👎10.273%
👏10.273%

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 366 reactions 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≈54,100 views63 reactionsread 9 September 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-资金盘和配

48🥰6😁4👍2🤯2👎1

Signed 新币仲裁kk

20 Nov 2025, 06:06 UTC≈55,200 views45 reactionsread 9 September 2026

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

42🔥2👏1

Signed 新币仲裁vv

20 Nov 2025, 06:06 UTC≈40,600 views22 reactionsread 9 September 2026

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

18👍2😁2

Signed 新币仲裁vv

3 Sept 2025, 17:50 UTC≈44,400 views28 reactionsread 9 September 2026

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

23👍4🎃1

Signed 新币仲裁vv

5 Jul 2025, 12:58 UTC≈40,200 views31 reactionsread 9 September 2026

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

21👍10

Signed 新币仲裁vv

20 May 2025, 07:30 UTCviews —

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

20 May 2025, 07:28 UTC≈38,500 views5 reactionsread 9 September 2026

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

5

Signed 新币仲裁w

20 May 2025, 07:28 UTC≈35,600 views43 reactionsread 9 September 2026

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

35👍5😇2👌1

Signed 新币仲裁w

20 May 2025, 07:28 UTC≈20,300 views12 reactionsread 9 September 2026

[仲裁规则031-关于打司法保时提前司法冻结问题] 1.保24小时或当天期间内出现司法,保时多久需在规则内写明司法反馈时间,规则内未约定反馈时间的默认反馈不限时,双方规则必须严明 《白资除外》 2.如保时内提前出现司法,料方能够提供鱼配合复转 ,以及证实鱼还在并无报警,并天眼查出报案地与受害者归属地不相同。那就不存在跨省份报案的说法。款都安全拖出,必须予以回款。款死卡内,那就上押担保,以鱼口供详情为准。 3.abcd 保时卡以入款回单时间开始计算,一道卡只保一道 没有保二道之说 规则标明保二 保当天除外 4.资金盘尾盘 纯精聊说尾刀客户导致司法 双方确定好对于尾刀的定义 如果没有定义则不认可尾刀

12

Signed 新币仲裁w

20 May 2025, 07:28 UTC≈22,500 views8 reactionsread 9 September 2026

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

8

Signed 新币仲裁w

20 May 2025, 07:28 UTC≈20,300 views11 reactionsread 9 September 2026

[仲裁规则032-关于料性的区分点问题] 1,冒充现(退)役军人身份或公务员身份的精聊谈恋爱杀鱼的。如只接纯精料双方精聊里面有冒充军人的需要规则报备提前说清, 规则明确不接的按三黑处理。 2,对于常规+色料的,常规及色料都可以接。常规色料的只接受色料。 3,在合作色料业务中,因考虑不管什么方式都是需要任务杀鱼。对于性质、方式,手法都是基本相同,本质上毒性上并无差异。 所以在料的区分时,不应该区别于色刷、空降,上门,色退 等。 但以敲诈形式可单独列出,对接清楚接与不接,否则视为全接。

11

Signed 新币仲裁w

20 May 2025, 07:28 UTC≈21,300 views13 reactionsread 9 September 2026

[仲裁规则035-关于收款卡出现二次认证问题] 近期出现不少需要出款方二次认证才能可用该笔进款情况。这种情况是资金能入账,但属于不可用状态,需要出款方二次认证。该概率问题,也属人为不可控,所以出现该类问题时按下列处理; 1,作业中出现二次认证料方与车方事先有约定能配合的情况下,料方引导鱼配合确认了,不管资金出没出,车方责任。 2,料方事先答应车方能配合,但料方又引导不了鱼配合确认,双方可约定保留该卡等待解除,未自动解除 钱死,料方责任。 3,料方与车方未事先告知约定要配合,但鱼能配合确认,正常回款。鱼不能配合确认,可保留自动解除(保留时间不超过48小时),未解开,钱死,车与料都承担一半责任。 上列规则不适用于拖算且只针对于二次认证问题,应及时第一时间反馈对接认证。拖算单独能配合否看资金处理情况。非全拖回保的部分。

12👍1

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.

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

“仲裁频道” (@zhongcai), 37,484 subscribers as measured 9 September 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.