Telegram RegisterThe public register of Telegram
Telegram profile photo for 太子担保-仲裁规则

Channel

太子担保-仲裁规则

@tzdbgz

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

12,917subscribers

+0 since we began measuring on 27 September 2026

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

Register entry

Telegram ID-1002158277837
TypeChannel
Username@tzdbgz
Description交易走担保-验证真假群,输入查+群编号 担保机器人 @tzdbxx 太子担保 @TZDB 公群导航 @TZGQ 供需信息 @TZGX 官方大群 @tzdbhh 官方公告 @tzdbgg 仲裁规则 @tzdbgz 海外交流 @tzdbzz 通缉曝光 @tzdbhh 担保流程 @tzdbliucheng 担保官方作业人员 @tzdb 负责人 @tzdbaa 公群aa @tzdbbb 专群bb @tzdbcc 仲裁cc @tzdbdd 供需dd
First recorded27 September 2026
Last confirmed live27 September 2026
Measurements held2
On Telegramt.me/tzdbgz

Topic

Other / unclassifiable — 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 27 September 2026 and assigned it the closest of 31 fixed categories, at 48% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Views per post sit far above this size band

7,100 average views per post against 12,917 subscribers — an engagement rate of 55.0%. Across the 1,320 registered channels in the same cohort — 10,026–31,615 subscribers, posting mainly in Chinese — the middle half sit between 1.50% and 7.82%, with a median of 3.40%.

What this was computed from
Window30 days (28 August 2026 – 27 September 2026)
Posts measured20 of 20 published in the window (0 exact, 20 rounded by Telegram)
Views totalled141,980
Mature posts only55.0% over 20 posts read at least 24h after publication
Subscribers12,917 measured 27 September 2026
Cohortb10000:zho · 1,320 channels · p10 0.453% · p25 1.50% · p50 3.40% · p75 7.82% · p90 14.7%
Position in cohort99.166th percentile · 16.2× the cohort median
Uncertainty±0.009% of the figure, from Telegram’s rounding
Post languageChinese · 100.0% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_high, last confirmed 27 September 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

12,91727 Sept 2026, 06:49 — 12,917 subscribers27 Sept 2026, 07:22 — 12,917 subscribers27 Sept 2026, 06:4927 Sept 2026, 07:22
2 measurements taken within a single day. 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 12,904–12,930 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Sept 2026, 07:2212,917no change
27 Sept 2026, 06:4912,917first reading

Engagement

20 posts held, back to 18 September 2026 — 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
55.0%
avg views ÷ 12,917 subscribers
Avg views / post
7,100
20 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
20
of 20 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. It is computed over the 1 of 20 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 22 September 2026
Posts held20 (18 September 2026 – 22 September 2026)
Views total141,980
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 07:22 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
1
Videos
1
Links
5

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

Recent posts

22 Sept 2026, 09:50 UTC≈6,600 viewsread 27 September 2026

🐋 新开公群列表 | 🐋 公群招租列表 | 🐋 公群暂停列表 防伪验证:@TZDB 太子供需:@TZGX 太子公群:@TZGQ 报备群管:@TZDBXX 1⃣1⃣🐋🐋1⃣1⃣1⃣1⃣1⃣1⃣1⃣1⃣ 😎 😎😎😎😎😎 太子工作人员名单 😎 😎😎😎😎😎 一键收藏太子集团

18 Sept 2026, 12:36 UTC≈6,600 views0 reactionsread 27 September 2026

⚡️😎😎😎😎😎 »»»太子担保公群导航业务列表««« [太子仲裁规则1-公群打超跑路] [太子仲裁规则2-上押退押规则] [太子仲裁规则3-中间人套路] [太子仲裁规则4-担保佣金] [太子仲裁规则5-专群拉多个料主] [太子仲裁规则6-公审] [太子仲裁规则7-回错u] [太子仲裁规则8-通道小群作业流程] [太子仲裁规则9-料规则问题] [太子仲裁规则10-纯bc类规则问题] [太子仲裁规则11-车队非柜问题] [太子仲裁规则12-打超问题] [太子仲裁规则13-打超查料扯皮等问题] [太子仲裁规则14-私聊回帐回款等问题] [太子仲裁规则15-关于订单取消 料方回复1 的问题] [太子仲裁规则16-关于入金金额不符的问题] [太子仲裁规则17-关于保料司法24、48、72小时的问题] [太子仲裁规则18-卡商/娱乐公群跑路] [太子仲裁规则19-冒充银监会征信为由的贷款] [太子仲裁规则20-关于飘帐问题] [太子仲裁…

Showing the 12 most recent of 20 posts we hold for @tzdbgz. 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.

Mentions

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.

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

“太子担保-仲裁规则” (@tzdbgz), 12,917 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/tzdbgz.

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.