兄弟们晚安 明天见
❤6👍1
Signed 服务哥•达利赌徒纠纷仲裁二组 @fuwu

Channel
@dldanbaozc
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
17,104subscribers
+3,978 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002535240889 |
|---|---|
| Type | Channel |
| Username | @dldanbaozc |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 15 November 2026 |
| Measurements held | 60 |
| Confirmed unchanged | 1 time, most recently 15 November 2026 |
| On Telegram | t.me/dldanbaozc |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Nov 2026, 09:11 | 17,104 | +43 |
| 12 Nov 2026, 03:19 | 17,061 | +60 |
| 10 Nov 2026, 06:45 | 17,001 | +51 |
| 8 Nov 2026, 17:57 | 16,950 | +68 |
| 7 Nov 2026, 13:36 | 16,882 | +40 |
| 6 Nov 2026, 15:59 | 16,842 | +40 |
| 5 Nov 2026, 18:45 | 16,802 | +63 |
| 4 Nov 2026, 19:26 | 16,739 | +58 |
| 3 Nov 2026, 15:54 | 16,681 | +42 |
| 2 Nov 2026, 13:09 | 16,639 | +36 |
| 1 Nov 2026, 11:28 | 16,603 | +27 |
| 31 Oct 2026, 13:46 | 16,576 | +19 |
| 30 Oct 2026, 17:06 | 16,557 | +28 |
| 29 Oct 2026, 15:56 | 16,529 | +5 |
| 28 Oct 2026, 18:01 | 16,524 | +56 |
| 27 Oct 2026, 14:55 | 16,468 | +55 |
| 26 Oct 2026, 12:37 | 16,413 | +20 |
| 25 Oct 2026, 15:57 | 16,393 | +68 |
| 24 Oct 2026, 17:36 | 16,325 | +56 |
| 23 Oct 2026, 14:36 | 16,269 | first reading |
34 posts held, back to 22 June 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 62 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 34 (22 June 2025 – 16 November 2026) |
| Views total | 19,190 |
| Reactions total | 424 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 05:53 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.
Lifetime counters from Telegram’s own channel header, read 17 November 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.
1,131 reactions across 31 posts, in 22 distinct kinds. The most used accounts for 67.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 760 | 67.2% | |
| 💩 | 74 | 6.54% | |
| 🤡 | 60 | 5.31% | |
| 👍 | 52 | 4.60% | |
| 👏 | 38 | 3.36% | |
| 🤣 | 32 | 2.83% | |
| 🖕 | 25 | 2.21% | |
| 👎 | 24 | 2.12% | |
| 🔥 | 11 | 0.973% | |
| 😘 | 8 | 0.707% | |
| 🐳 | 7 | 0.619% | |
| 🤷♀ | 7 | 0.619% | |
| 🍌 | 6 | 0.531% | |
| 👌 | 4 | 0.354% | |
| 🗿 | 4 | 0.354% | |
| 😁 | 4 | 0.354% | |
| 🤮 | 4 | 0.354% | |
| 👻 | 3 | 0.265% | |
| ☃ | 2 | 0.177% | |
| 🌭 | 2 | 0.177% | |
| 2 further kinds | 4 | 0.354% |
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 31 of the 34 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 1,131 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 34 most recent posts we hold, published 22 June 2025 to 16 November 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.
Telegram’s own ‘edited’ marker: 1 of 14 posts held from the last 30 days (7.14%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
兄弟们晚安 明天见
❤6👍1
Signed 服务哥•达利赌徒纠纷仲裁二组 @fuwu
1
❤25
Signed 服务哥•达利赌徒纠纷仲裁二组 @fuwu
@fuwu 服务哥的纠纷朋友圈 pinned «😀😀😀😀😀 @fuuw的朋友圈 【重磅】达利纠纷朋友圈正式启航! 达利公审群 达利纠纷频道 纠纷专属的群组跟频道(公审群乃达利活跃度和曝光度最高的群组含金量不用多说) 朋友圈频道直达:https://t.me/dldanbaozc (该频道为原达利官方纠纷频道,曝光度拉满) 绑定朋友圈讨论群:https://t.me/+NXChXn-xaIs1Yjk0 (该群组将在开业后开展1个月的引流活动) 这里曾是达利担保的官方纠纷频道,现在全面升级为「达利纠纷朋友圈」——全网曝光度最高、活跃度最强的纠纷阵地。…»
😀😀😀😀😀 @fuuw的朋友圈 【重磅】达利纠纷朋友圈正式启航! 达利公审群 达利纠纷频道 纠纷专属的群组跟频道(公审群乃达利活跃度和曝光度最高的群组含金量不用多说) 朋友圈频道直达:https://t.me/dldanbaozc (该频道为原达利官方纠纷频道,曝光度拉满) 绑定朋友圈讨论群:https://t.me/+NXChXn-xaIs1Yjk0 (该群组将在开业后开展1个月的引流活动) 这里曾是达利担保的官方纠纷频道,现在全面升级为「达利纠纷朋友圈」——全网曝光度最高、活跃度最强的纠纷阵地。 为什么一定要加入? 1. 不定时狂撒福利 现金红包、游戏彩金随手发免费领,真正做到“进群就有机会捡钱”。 2. 一手官方消息直达 达利所有规则更新、官方通知,第一时间在这里同步,让你比别人更早掌握主动权。 3. 纠纷一线真实故事 我亲身处理过的各种奇葩纠纷、反转剧情,定期分享,边看边学,边学边赚。 4. 真正的王炸…
❤7👌1👍1
Signed 服务哥•达利赌徒纠纷仲裁二组 @fuwu
我的朋友圈比他们高级!!!我决定同时开放公审群陪审员管理位
❤16👍5👎4🤡4😘1
Signed 服务哥•达利赌徒纠纷仲裁二组 @fuwu
我去看一下他们开的时候都是怎么说的
❤5🤡4👏3🔥3🖕3👍1🥰1😘1
Signed 服务哥•达利赌徒纠纷仲裁二组 @fuwu
他们开个人朋友圈的时候 大家都是祝福的 为什么我一开 就是挨骂的
❤10🤡8🖕5😘4🍌2
Signed 服务哥•达利赌徒纠纷仲裁二组 @fuwu
别骂我啊 不是我拉的
🤡20🖕6❤4👍1😘1
Signed 服务哥•达利赌徒纠纷仲裁二组 @fuwu
Photo, posted without a caption
🤡22🖕4❤3👍1👎1😘1
Signed 服务哥•达利赌徒纠纷仲裁二组 @fuwu
嗯差不多就是这样
❤18🖕3🔥1😁1
Signed 服务哥•达利赌徒纠纷仲裁二组 @fuwu
我今天很开心
❤16🖕4🔥3🤬2🤮2
Signed 服务哥•达利赌徒纠纷仲裁二组 @fuwu
让我想想
❤22💩5👏4😁1
Signed 服务哥•达利赌徒纠纷仲裁二组 @fuwu
Showing the 12 most recent of 34 posts we hold for @dldanbaozc. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“达利担保仲裁规则” (@dldanbaozc), 17,104 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/dldanbaozc.
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.