Channel
@jiuyunzhongcai
On this record: Growth · Engagement · Posts · Citations · Cite this entry
19subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001901561883 |
|---|---|
| Type | Channel |
| Usernames | @f_8888 @jiuyunzhongcai |
| Created | Between 1 March 2023 and 22 May 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 8 times, most recently 15 September 2026 |
| On Telegram | t.me/jiuyunzhongcai |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Aug 2026, 03:44 | 19 | no change |
| 15 Aug 2026, 20:47 | 19 | -1 |
| 11 Aug 2026, 16:16 | 20 | no change |
| 11 Aug 2026, 15:58 | 20 | -1 |
| 11 Aug 2026, 14:46 | 21 | no change |
| 7 Aug 2026, 14:44 | 21 | first reading |
20 posts held, back to 22 May 2023 — 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 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 3 June 2023. An engagement rate over an empty window would be a number about nothing.
仲裁规则001—上押退押规则 仲裁规则002—公群打超跑路 仲裁规则003—中间人套路 仲裁规则004—车队跑路 仲裁规则006—专群拉多个料主 仲裁规则007—公审 仲裁规则008—群老板及料主方回错U 仲裁规则009—小群作业流程 仲裁规则010—料性规则问题 仲裁规则011—纯bc类规则问题 仲裁规则012—车队非柜问题 仲裁规则013—私聊回帐回款等问题 仲裁规则014—关于订单取消 料方回复1 的问题 仲裁规则015—关于固定金额打超的问题 仲裁规则016—关于保料司法24、48、72小时的问题 仲裁规则017—人头公群跑路 仲裁规则018—关于飘帐问题 仲裁规则019—几种料的接料方式 仲裁规则020—冒充银监会征信为由的贷款 仲裁规则021—关于料不对版时间查询问题 仲裁规则022—关于虚拟公户打料问题 仲裁规则023—关于白资群现存问题
[仲裁规则023-关于白资群现存问题] 关于白资群现存 受害人现存款一道直流查询核实给最高15天这种全扣 人头卡取款 现金存买U A取A存最高给于15天查询卡无司法回款 有冻结 风控 止付配合解除后给适当补偿
[仲裁规则022-关于虚拟公户打料问题] 最近市场出现很多虚拟公户纠纷，因为虚拟公户有天眼不可查的问题，但鉴于虚拟户截图，视频都可造假删除记录属性，现制定以下规则。 1:虚拟公户查料，以料方出款卡天眼流水为准，料方卡出款如果一直未退回 则默认到帐. 2:供方如可提供全程不间断录屏，确实没到，则按照虚拟户客服提供的时间处理，退回时间为虚拟户官方回复的7个工作日起，至半个月或者更长 双方可以协商。 3.所有360，微信，拼多多等各种虚拟公户类纠纷处理遵循同上规则。
[仲裁规则021-关于料不对版时间查询问题] 料方需方打料给车队供方查司法空时 最高时间给7天时间查料，料方打款时间算起。如果7天时间到查询司法还是空 车队供方回款
[仲裁规则020-冒充银监会征信为由的贷款] 由于大陆官方，本次两会之后已取消银保监会编制，所以此条规则即日起取消，小贷类不管是，银联，结算中心，还是银行工作人员，都归属于大混类。
[仲裁规则019-几种料的接料方式] 盒饭，建材，红酒 接料方式 ： 1：建立在车队接这几种料并且知道料性的前提下，要不要报备规则内写清楚 2：如果不接盒饭料 或者不接 军警类 直接写清楚 不写清楚代表都接 3：如果供方写明不要盒饭，建材，红酒。那查出冒充主体军警类 一律按照三黑处理。其他公司，个人企业单位类 进大混，按照接料规则处理。
[仲裁规则018-关于飘帐问题] 在卡类跑分业务上，有小概率会出现飘帐问题。 1.当出现飘帐问题，以实际到帐为准。 2.钱没到钱死钱出不来，不回。 3.钱到钱没死钱出来，回。 4.当供方卡号信息发错导致飘帐，钱退回，钱死，供方全责。 5.当料方卡号信息自己打错，导致飘帐，钱死，料方全责
[仲裁规则017-人头公群跑路] 久运人头公群跑路赔付不按普通公群赔付标准,具体赔付看实际情况,目前未出现过一起人头公群跑路问题!暂时也没有想到好的解决方案!只能以实际情况来处理。
[仲裁规则016-关于保料司法24、48、72小时的问题] 保时内出现司法,不管钱有没有出去,仲裁规则: 1.协商处理! 2.赔付保时内司法的该笔资金!不是赔付卡费请注意!
[仲裁规则015-关于固定金额打超的问题] 在作业操作过程中,经常发生报五万卡进十万的类似问题! 在实际过程中,很多人连五万都不想认,我们的规则是 报五万进十万,最少要认五万不用扯皮!无需仲裁!
[仲裁规则014-关于订单取消 料方回复1 的问题] 在订单取消的问题上,有时候料方回复太随意,会造成供方订单钱追不回的情况. 1.人头卡双方确认取消的订单 卡死风控钱出不来不回 ! 2.交易所等订单类型通道,钱追回来回,追不回不回 但要提供完整证据 ! 3.提供不了完整的交易追不回的证据,供方最少要认一半! 4.不允许单方面取消订单,除非超时!!! 5.以上规则只保障双方的权益 不允许吃钱 追不回卡死等情况需要提供完整证据 ! 注意: 订单双方取消 再进的话 责任在料方!!!钱追不回来不回! 这种情况下回复1,代表确认的意思!请大家操作要谨慎! 另外取消和卡死、卡停是两个概念
[仲裁规则013-私聊回帐回款等问题] 担保作业群私聊发地址回款回u的都是骗子 担保作业群都是群内回款! 1.私聊回款对方删除消息没法核实! 2.除非提供完整视频分析,才有可能追回! 3.私聊回款回u出现损失自己负责!
Showing the 12 most recent of 20 posts we hold for @jiuyunzhongcai. 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.
Named by 2 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.
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.
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 19 August 2026 — this entry's latest reading, not the date you are reading this.
“久运担保-仲裁频道 @f_8888” (@jiuyunzhongcai), 19 subscribers as measured 19 August 2026. Telegram Register, tgregister.com/channel/jiuyunzhongcai.
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.