Channel
@zhunze
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
297subscribers
+8 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001285086944 |
|---|---|
| Type | Channel |
| Username | @zhunze |
| Created | Between 1 April 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 24 August 2026 |
| On Telegram | t.me/zhunze |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 20:58 | 297 | +7 |
| 8 Aug 2026, 23:37 | 290 | +1 |
| 8 Aug 2026, 10:19 | 289 | first reading |
16 posts held, back to 17 April 2024 — 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 pageof 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 1 August 2026. An engagement rate over an empty window would be a number about nothing.
9 reactions across 7 posts, in 3 distinct kinds. The most used accounts for 55.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5 | 55.6% | |
| 👍 | 3 | 33.3% | |
| 💯 | 1 | 11.1% |
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 10 of the 16 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 9reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 17 April 2024 to 1 August 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.
🌈七彩仲裁规则 pinned «拉专群，开公群，发供需，办理七彩会员请联系七彩在线人工客服：@kefu888 请关注防骗频道 @fangpian 防骗全拼 公群交易员 1组 @abc1 电话 +88802496735 2组 @abc2 电话 +88802967345 3组 @abc3 电话 +88803964076 专群交易员 1组 @qcdb1 电话 +88807314626 2组 @qcdb2 电话 +88807435291 3组 @qcdb3 电话+88805738319 交易员助手 @qicaiaaa 电话 +88802754929…»
七彩工作人员名单 七彩支付工作人员名单 以上均为七彩担保工作人员.其他没有在这名单上的均不能代表七彩担保.切勿相信. 在七彩开任何公群无论押金大小，七彩只能担保群内交易和有效报备.脱离以上两点七彩概不担保.更不担保公群老板任何个人行为.请勿听信与担保方关系如何好，然后进行私下交易.被骗概不负责. （如果你在飞机上被骗，说明你智商不行，说明你还不懂人性、.不要因为贪图一时方便，不走担保交易，空放一时爽，被跑泪两行） 七彩担保频道 一键收藏 七彩资源交流群 一键收藏
❤1
七彩开群收费标准 关于车队跨夜留人头等解释 关于跨担保扣款和跨群解释 关于公群一进一拉相关解释 关于公群和挂钩群相关解释 关于三黑扣款等赔偿等解释 关于公群回错U，多下发解释 关于公群机器人加账问题解释 关于卡商公群纠纷说明 关于公群规则仲裁拉群等解释 关于担保纠纷类型等详细解释-以此条为准 以上相关解释，七彩有最终解释权
供需群广告 15U一次， 固定广告位开运福利价：1000u 连续包月三个月起每月价格：888 供需 一次性预存10次 免费送2次 15U 一次 供需 一次性预存20次 免费送5次 15U 一次 不能带任何频道链接， 供需上不能发图片. 发供需 联系 @kefu888
七彩仲裁在供需双方都按群规进行交易时遇到纠纷七彩尊重群规，如双方都按群规交易，七彩仲裁审核后，不拉纠纷群。请供需双方交易认真仔细阅读群规. —————————————————— 以下等仲裁会拉群进行仲裁调解 七彩担保仲裁等相关规则都是建立在公群群规上，结合实际情况判定供需双方纠纷对错，如果遇到供方未按自己公群规则和需方进行交易那么双方以当时聊天记录的为准，举例说明 1供方不接红酒 建材 江苏料的群规，需方报备后供方允许需方入金，那么在这个过程中，供方无论出现什么问题不以群规为准。以口头交易为准 供方无论在公群还是在私群内临时性的违背自己定的群规发生的纠纷请及时联系仲裁。
友情提示： 供方提醒车队或者供方本身就是车队没把握的情况下接附言脱算的料，不要答应维护 留人 取现，特别是在公群贴卡附言脱算了卡出现风控了，只需出一个风控卡的视频即可！如果留人头，人头看不住被人头钱离卡了会出现责任纠纷。
👍1
关于公群下发回u ，多回给料方，或者承兑多回给车队，请料方和车队及时回款，可以要求供方给红包或者奖励等方式适当的奖励。如遇到不肯退还的请联系担保方，如能在担保内拦截的范围内七彩都会拦截本款，大家都不容易请务互相为难。有一种可能无法拦截回该笔款，就是这个钱包地址确实很久没有使用，查公链未使用1个月的例外。 关于公群老板被车队跑路，可以追溯的七彩都无条件追溯，但是请公群老板保存好证据
七彩概不负责任何七彩以外的跨担保，跨私群的扣款业务，例如： 1：A在别的担保有公群跑路了，A在七彩有开公群需方来七彩要求扣A在七彩的押金，七彩概不划扣。 2：除三黑和报备料偷打可以允许在七彩跨群扣，但是需要A供方和B供方协商，A和B不认识七彩可以拉群协商同意后可以扣，如A群被偷打三黑，B群不愿意扣这料主的款，那么七彩也不能强扣。 3：如遇到A公群老板在B公群老板，打了三黑料，担保方扣A公群的金额给B
❤2
关于一进一拉的问题（车队超压问题解释） 1：一进一拉的卡，需方同时进卡相隔10秒内，车队超压跑路供方全责，不认供方任何理由，和车队聊天记录。 2：如果因为一进一拉，A需方先进卡，B需方进款时间和A需方相隔时间一致，供方拉停 ，供方贴卡时明确有和需方说，一进一拉，不是专卡，路上有类似字眼，需方还继续进卡说明需方有能力随时拉停如果没有及时拉停需方自己负责，供方无责。 3：如果一进一拉的卡和需说是专卡了，又一卡多贴，公群拉停后进的钱，钱又离卡了，供方全责。如是在几乎同一时间进钱导致金额超了，车队失联死钱供方全责。 4：如遇到在A需方进钱后供方在出二道或者三方出现了风控问题在前台拉停，不适用本条规则。 5.如搬砖的在不知情的情况下造成的损失看情况而定。 本条只针对 一拉一进，车队超压的问题。如车队押金3000U，你路上排了10+w需方同时进款导致车队跑路等类似这类问题。 冲锋卡，AA,三方额度卡降额度等，不受用此条规则…
关于近期【料性问题】的争议做以下几点说明： 一、三黑料：冒充公检法、冒充上下级、冒充财务，无论通过何种手段，关联到以上三种统称三黑。 二、盒饭料：如果料方喊卡未报备盒饭，如查出冒充主体军警类 一律按照三黑处理。其他公司，个人企业单位类 进大混，按照接料规则处理。 三、培训费，机票，建材，红酒类的接料方式 ： 1：建立在车队接这几种料并且知道料性的前提下，需不需要报备请供方规则内写清楚； 2：也提醒各位下料方该类料子（培训费，机票，红酒，熟人，建材）请主动报备，如料方报备供方贴卡入金，按照默认接受料性；如未报备入金，按照供方规则限定处理； 四、关于二道资金入一道公群供方已经下发，是否支持追溯的问题：（二道入金缩短冲锋卡的使用时效） 1:二道入金如果当下查出，且未下发，支持扣该笔二道入金； 2:二道入金供方已经下发的情况，如车队应该笔二道入金产生损失，请供方保存好记录，支持追溯； 3: 二道入金供方已经下发的情况，入车队并未因…
❤1
4.30新增一条 如遇到料不对版的恶性纠纷 没有报备的情况下可以保留好入款证据，可以联系 @abc9 在担保公群内都可以划扣。 如三黑，一系列不按群规资金，供方可以保留永久追溯全力
👍1
🔸：特殊情况：如遇到飞机无法联网、崩溃请及时各位及时拉停！飞机崩溃无法联系上即算拉停、请各位及时拉停！ 建议开群老板加一条规则！！！
Showing the 12 most recent of 16 posts we hold for @zhunze. 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 — 248,983 of 1,627,445entries 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.
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.
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.
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.
“🌈七彩仲裁规则” (@zhunze), 297 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/zhunze.
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.