Telegram RegisterThe public register of Telegram

Channel

纠纷频道

@jiufen

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

32,065subscribers

+40 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-1002613669668
TypeChannel
Username@jiufen
Description永不失联官网 xinbi.com 公群导航 @gqdh 备用: @xbdh 供需频道 @abcd 备用: @xbgx 公告频道 @gonggao 官方大群 @xbdb 新开公群 @gong 新彩娱乐 @xincai 新币招商 @xinbei 24小时在线客服 @xbkf 新币每日福利群 @zzzz 新币搜索机器人 @xbso
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/jiufen

Growth

32,01832,06532,041.56 August 2026 — 32,025 subscribers7 August 2026 — 32,041 subscribers8 August 2026 — 32,036 subscribers9 August 2026 — 32,032 subscribers10 August 2026 — 32,018 subscribers11 August 2026 — 32,061 subscribers12 August 2026 — 32,065 subscribers6 August 202612 August 2026
7 measurements spanning 6 days, net +40. 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 32,011–32,072 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 19:3232,065+4
11 Aug 2026, 17:2632,061+43
10 Aug 2026, 14:1232,018-14
9 Aug 2026, 10:0832,032-4
8 Aug 2026, 08:0132,036-5
7 Aug 2026, 11:2632,041+16
6 Aug 2026, 22:4632,025first reading

Engagement

21 posts held, back to 12 March 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 18 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
19.2%
avg views ÷ 32,065 subscribers
Avg views / post
6,160
6 posts measured
Reaction rate
0.23%
reactions ÷ views · ER floor
Posts in window
6
of 21 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 August 2026
Posts held21 (12 March 202611 August 2026)
Views total36,930
Reactions total85
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 10:00 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
7
Videos
2
Links
1

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

629 reactions across 21 posts, in 13 distinct kinds. The most used accounts for 66.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
41666.1%
👍7712.2%
👎558.74%
🤣314.93%
💩111.75%
👏101.59%
😱81.27%
🫡60.954%
40.636%
🔥40.636%
🆒30.477%
😁30.477%
🥰10.159%

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 21 of the 21 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 629reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 21 most recent posts we hold, published 12 March 2026 to 11 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.

Recent posts

11 Aug 2026, 12:19 UTC≈2,000 views5 reactionsread 13 August 2026

日期: 2026年8月11日 纠纷群: E组61667群 纠纷双方: @*****s644供方 @***m1需方 纠纷事由:搭建盗U产品,供方交货时被担保员及时发现并提醒后,需方以产品没有交付,要求退回押金。 处理结果:双方不发规则未找担保确认直接作业,作业无效;相关盗u的作业予以没收押金 处理思路: ①为维护市场相关权益,担保平台严禁盗U、盗飞机等病毒木马项目。一旦触碰,重罚。 ②需方试图以“未完成交货”来辩解,但在双方对接记录中,有源码也有登陆的上鱼后台;行为本身已经构成了违规 经验总结: 涉嫌盗U程序木马等搭建交易,只要被发现即重罚。另,遵守担保规则双方规则确认后@担保再作业,以免有些违规作业或假作业给双方带来利益受损。

5

Signed 新币仲裁kk @xbkkk

6 Aug 2026, 10:36 UTC≈4,520 views28 reactionsread 13 August 2026

2026年8月6日 纠纷群:F 981 纠纷双方:供方:***** 需方:***** 纠纷事由:公群以招收业务员为由私下收取押金,收完后双删对接记录。 处理结果:公群罚款3000U 处理思路: 1,核实对接记录 2,核实转U收U地址 3,核实对接方是否为公群人员 经验总结:公群不能做与公群报备业务不符业务,更不能以公群名义招收业务员私下收取客户押金,有需要可以拉专群对接。 在这里提醒在开公群切勿触碰担保红线,提醒客户想做公群业务员需要交押金可以拉专群对接,以免产生不必要的纠纷。 担保存在的意义是保证交易双方的利益,杜绝一切吃钱行为。

14👍8🫡6

Signed 新币仲裁w

31 Jul 2026, 12:12 UTC≈6,450 views15 reactionsread 13 August 2026

日期: 2026年7月31日 纠纷群:专群B组74573 纠纷双方: @****供方 @** 需方 纠纷事由:过保以后鱼带人拦截取手 处理结果:车队无责,需方赔付放空费用 处理思路: 1:供方视频完整,对接记录录入鱼的身影和拦截视频上鱼的身影。 2:需方提供不出切客,任何证明。 3:本群车队无下发需方,需方已经下发上游,需方自行承担后果。 4:新币担保有拿现类延时三小时通告(只保抢劫),车队无责。 总结经验:此纠纷简单明确,发出的意义是提醒各位车队、中介,新币担保提出的拿现类三小时下发是为了保护各位的利益。

15

Signed 新币仲裁vv

25 Jul 2026, 13:12 UTC≈8,270 views14 reactionsread 13 August 2026

日期: 2026年7月25日 纠纷群:最近已发生多起 纠纷双方: @****供方 @** 需方 纠纷事由:交易后被踢出对接群没结算 处理结果:公群补偿受害者部分,中间人拉黑标记骗子 处理思路: ①中间人两头对接,先是找公群报备,之后找公群不在线的人员强拉进群,群组修改头像和名字跟公群人员一致 ②私群修改群组信息,群主匿名,给公群人员上群主头衔,真正的群主是紫色的,这里是给公群人员上的是管理员头衔,是绿色的“群主” ③再发群链接给需方,需方进群后,跟需方对接的是匿名群主发的信息头衔显示是“管理员”交易之后飞出群 经验总结:作业人员认清楚头衔,隐私里面群组与频道修改成联系人或者不允许任何人,以免不在线时被强拉进群

14

Signed 新币仲裁hh

21 Jul 2026, 16:13 UTC≈7,930 views12 reactionsread 13 August 2026

日期: 2026年7月22日 纠纷群:专群C组58930 纠纷双方: @****供方 @** 需方 纠纷事由:地址多贴导致上单鱼醒拿走第二单包裹 处理结果:料方承担40%、中介承担30%、车队承担30% 处理思路: 1:第一单鱼交易完成以后车队已经验货加账,第二单鱼放完包裹以后第一单鱼返回现场拿走第二单鱼的包裹。 2:中介、车队是知情地址多贴,料方不知。但是确实是鱼醒以后返回布控现场拿走包裹,现场视频证明清晰。 总结经验:鱼醒后行为无法控制,地址严禁多贴。同一地址同时接多单极易撞车,风险巨大,必须杜绝此类操作。

👍7😁32

Signed 新币仲裁vv

20 Jul 2026, 06:39 UTC≈7,760 views11 reactionsread 13 August 2026

2026年7月20日 纠纷群:**** 纠纷双方:供方:**** 需方:**** 纠纷事由:中间人套路,中介一边对接料方一边对接公群,中介把料方的用户名发给公群报备,公群发对接群链接给中介,中介强拉公群不在线人员进另外群开启匿名冒充供方人员在群内跟料方对接。作业完未回款料方,供方不知情,中介得利,双方受骗。 骗局特征: 1.群名,群头像跟某个群成员完全一致 2.群内看不到管理员标签混乱,开启匿名管理员 3.中介全程在对接群无发言(不排除后续多账号团伙作案) 处理思路: 1,供方提供跟对接人的完整对接记录 2,需方提供跟对接人的完整对接记录 3,供需双方录制作业群完整作业记录连带群内成员和用户名一镜到底 4,核对群名,群主和群管理(群主两字显示为紫色并非绿色,绿色为假) 经验总结:骗子套路层出不穷,为针对此类情况发生,建议飞机上邀请权限全部关掉了,避免不在线时被陌生人强拉进群上头衔,冒充公群人员作业,另外公群报备时,

11

Signed 新币仲裁w

13 Jul 2026, 14:56 UTC≈8,540 views32 reactionsread 13 August 2026

2026年7月13日 纠纷群:B组74935 纠纷双方:供方:@m**8 需方:@aabbcc6889 纠纷事由:现金承兑,取手到场后被需方控制,需方拿取手手机回复车队负责人已拿钱离开可以下发,专群内下发后需方放人,为时已晚。 处理结果:未追溯到需方其他押金,标记拉黑需方。 处理思路: 1.核实供方所反馈问题的真实性 2.核实需方以往在新币作业记录 经验总结:针对此类情况,车队负责人可以和取手约定对接暗号以方便核实取手情况,暗号不对及时反馈以确保自身利益不受损。

15😱8💩6🆒3

Signed 新币仲裁w

11 Jul 2026, 17:15 UTC≈9,030 views31 reactionsread 13 August 2026

日期: 2026年7月2日 纠纷群:K260纠纷群 纠纷双方:举报人: @nxkcmcb 公群: @ygnnbb 纠纷事由: ① 举报人举报机器人搭建公群搭建的机器人留有后门且出售后门后台导致其他商户交易信息泄露,造成极大影响(被点鱼,抢包)。经核实为真。开启公审广邀新币在押商户了解此套路,给所有客户敲响警钟。 ② 在给予奖励后,威胁公群方,索要巨额资金,后又收到反馈,举报人也是购买后门后台搞事的人。同时举报人贪得无厌继续威胁新币无止境索要奖励。私下联系公审内其他人声称出售此类资源,包括此人之前购买后台获取到的其他交易方,并索要巨额费用。 ③ 在担保开启赔付流程后,经核查发现,该公群存在制作及使用假担保机器人、假群机器人以及冒充官方机器人的违规欺诈行为。 处理结果: 1、链上和账号追踪发现,K260关联K2077、F239两个公群,强关联(同一上押地址,同一负责人账号)涉事3个公群全额没收。 2、三个公群近1个月所有报备订

23💩3🔥3👍1🥰1

Signed 新币仲裁yy

11 Jul 2026, 16:17 UTC≈7,350 views15 reactionsread 13 August 2026

日期:7月11日 纠纷群:S5 6793,关联 D 63174、D 63173 纠纷双方:@****(供方)、@**(需方) 纠纷事由: 在约定保时内,鱼带人尾随并实施拦截、抢夺,导致车队产生损失。 处理结果: 经对关联群聊天记录、转发时间、对接链路及现场录像等材料逐层核查,现有证据显示,源头中介对接的料方群在没过安全时间的情况下,提前下发;随后即发生人员尾随、拦截事件。依据现有证据及相关规则,对需方骗子标记拉黑处理;车队损失按照放空赔付。 处理思路: 源头车队此前已遭遇过一次类似事件,因此本次交易前进行了较为严格的核验,曾询问对方是否为熟人,并对全程进行录像留证。此次事件发生时仍处于保时内。经对多个关联群及上下游对接记录逐层核实,确认相关信息在保障时限内被提前下发,且信息下发后不久即发生尾随、拦截,时间线及证据链能够相互印证。 经验总结: 近期类似尾随、拦截及恶意制造损失的事件频发,各中介及车队应进一步加强风险核验。对

15

Signed 新币仲裁hh

8 Jul 2026, 06:01 UTC≈8,030 views20 reactionsread 13 August 2026

日期: 2026年7月8日 纠纷群:专群B组71401 纠纷双方:@***ishen777 供方 @*889 需方 纠纷事由:包裹丢失 处理结果:供方无责,无需回款 处理思路: 1:第一次炸鱼,鱼所述5号已经报警,但是6号继续送出12万。 2:查受害人立案,立案时间为7号,受骗金额为79998元。 3:后续鱼继续有开刀有入款,但是根据供方提供的所有视频看出现场有几名着装异常人员。 4:后续再次炸鱼,鱼所诉报警以后12万是由条子给鱼让鱼继续送,条子蹲守。 5:结合视频、炸鱼、立案,本单纠纷供方无责。 总结经验:清者自清,无需争辩,鱼后续入款是有利的证明,但是条子蹲守也是不争的事实。

12👏3👍2💩2🔥1

Signed 新币仲裁vv

6 Jul 2026, 11:47 UTC≈8,520 views13 reactionsread 13 August 2026

日期: 2026年7月6日 纠纷群:S5 6504 纠纷双方: @****供方 @** 需方 纠纷事由:下发后取手反馈抢劫 处理结果: 需方标记骗子,押金下发供方 处理思路: ①取手交易离开后一个小时被抢,反馈有车在跟一起上高速,一起下高速,已经不正常了,取手也没有进行及时反馈。 ②需方提供不了切客,且收款地址还是新的,也是新面孔 ③从需方上一个群内车队反馈现场也是被跟,后取手有人接应才没造成损失 经验总结:杀不到鱼就开始杀车,近期下发后杀车已出现多例,下发前先看一下收款地址是否正常,核实取手是否安全后再进行处理。尤其是中介

10👎2👍1

Signed 新币仲裁hh

3 Jul 2026, 12:29 UTC≈9,560 views31 reactionsread 13 August 2026

日期: 7月2日 纠纷群: s5-6381关联s5-6383,h2811公群 纠纷双方: @ji***9 供方 @XHTD8888 @XHTD8765 需方 纠纷事由:拿现济南22万,s5-6381作业下发后,车队被抢 处理结果:公群h2811杀车,公群人员全部拉黑 处理思路: ①车队被抢,录制抢劫人的视频; ②从链上交互的佐证:公群h2811上押地址的关联性 ③又从频道发单记录也证实本h2811公群杀车 经验总结:以窗口公群引流,再拉专群作业换小号以逃脱罪名?是狐狸总是要露出尾巴的

👍14134

Signed 新币仲裁kk @xbkkk

Showing the 12 most recent of 21 posts we hold for @jiufen. 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 — 646,783 of 1,169,250entries 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 4 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.

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.

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

“纠纷频道” (@jiufen), 32,065 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/jiufen.

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.