公群8550 押金2688u 云捷|个人|企业代实名|实卡接码|盖章签字认证 聚名网实名 西部数码实名 dcloud实名 外国人实名 阿里云实名 腾讯云实名 GMAME实名 国际KYC认证 紫云 快云 品赞 星灿 超云 酷盾 悍铭 联系人:@HHHYYY @HHHBBB https://t.me/+JRK7IEjptQQ4NmQ5 ⭐️交易必须走天成担保,所有业务联系 天成客服 @TCKF ⭐️
👍1

Channel
@JiuDingSAD
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
16,981subscribers
+420 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001784109041 |
|---|---|
| Type | Channel |
| Username | @JiuDingSAD |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 10 September 2026 |
| On Telegram | t.me/JiuDingSAD |
Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
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.
Posts published here appear word for word on 3 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @tdgx988/63957 Aug 2026, 11:31 UTC | @JiuDingSAD/9989 · this entry7 Aug 2026, 11:31 UTC | 1.00 | under a minute |
| @tdgx988/63967 Aug 2026, 11:33 UTC | @JiuDingSAD/9990 · this entry7 Aug 2026, 11:33 UTC | 1.00 | under a minute |
| @tdgx988/64017 Aug 2026, 13:05 UTC | @JiuDingSAD/9995 · this entry7 Aug 2026, 13:05 UTC | 1.00 | under a minute |
| @tdgx988/64027 Aug 2026, 13:13 UTC | @JiuDingSAD/9996 · this entry7 Aug 2026, 13:13 UTC | 1.00 | under a minute |
| @tdgx988/64047 Aug 2026, 13:18 UTC | @JiuDingSAD/9998 · this entry7 Aug 2026, 13:18 UTC | 1.00 | under a minute |
| @tdgx988/64087 Aug 2026, 14:14 UTC | @JiuDingSAD/10002 · this entry7 Aug 2026, 14:14 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @tdgx988 | 34 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @tdgx988 (33–1) |
| @tcdbgxpdd | 34 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @tcdbgxpdd (24–10) |
| @tcgx | 34 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @tcgx (33–1) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 90 of the 90 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 37 comparable posts for this entry, running 7 August 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 4, the earliest publisher we hold is @tcgx. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 7 August 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.
This channel’s posts match, word for word or near enough, posts on 3 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 06:59 | 16,981 | +120 |
| 7 Sept 2026, 01:17 | 16,861 | -61 |
| 4 Sept 2026, 07:20 | 16,922 | +48 |
| 2 Sept 2026, 20:04 | 16,874 | +44 |
| 1 Sept 2026, 16:54 | 16,830 | +34 |
| 31 Aug 2026, 18:54 | 16,796 | +58 |
| 30 Aug 2026, 17:54 | 16,738 | +17 |
| 29 Aug 2026, 17:17 | 16,721 | -153 |
| 28 Aug 2026, 17:04 | 16,874 | +37 |
| 27 Aug 2026, 15:29 | 16,837 | +24 |
| 26 Aug 2026, 18:06 | 16,813 | +16 |
| 25 Aug 2026, 17:22 | 16,797 | +17 |
| 24 Aug 2026, 14:13 | 16,780 | +26 |
| 22 Aug 2026, 22:18 | 16,754 | -27 |
| 21 Aug 2026, 12:05 | 16,781 | -16 |
| 20 Aug 2026, 12:23 | 16,797 | -16 |
| 18 Aug 2026, 14:42 | 16,813 | +18 |
| 17 Aug 2026, 12:32 | 16,795 | +46 |
| 16 Aug 2026, 05:25 | 16,749 | +63 |
| 14 Aug 2026, 12:59 | 16,686 | first reading |
702 posts held, back to 7 August 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 53 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. It is computed over the 22 of 521 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 3 September 2026 |
|---|---|
| Posts held | 702 (7 August 2026 – 3 September 2026) |
| Views total | 20,892 |
| Reactions total | 20 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 09:37 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.
20 reactions across 20 posts, in 3 distinct kinds. The most used accounts for 90.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 18 | 90.0% | |
| ❤ | 1 | 5.00% | |
| 😁 | 1 | 5.00% |
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 23 of the 702 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 20 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 702 most recent posts we hold, published 7 August 2026 to 3 September 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.
公群8550 押金2688u 云捷|个人|企业代实名|实卡接码|盖章签字认证 聚名网实名 西部数码实名 dcloud实名 外国人实名 阿里云实名 腾讯云实名 GMAME实名 国际KYC认证 紫云 快云 品赞 星灿 超云 酷盾 悍铭 联系人:@HHHYYY @HHHBBB https://t.me/+JRK7IEjptQQ4NmQ5 ⭐️交易必须走天成担保,所有业务联系 天成客服 @TCKF ⭐️
👍1
公群5685 押金3008u 隐藏IP-德国物理手机和电脑出租-国内做业务专用 国内做业务风险太高?在国内控制德国的电脑工作,本地电恼0记录,配置星链专用网络不使用掴内网络作业-完全无痕,不出国也可以在国外做业务。 联系人:@ipkkk @ipipfa @xoqqq https://t.me/+ZVWv8l2Chyo5NDE1 ⭐️交易必须走天成担保,所有业务联系 天成客服 @TCKF ⭐️
👍1
公群1880 押金10000u ULINX 专业APP跑分平台 USDT专业APP跑分,信誉老平台运营5年,只做纯体育内层料,安全稳定,有公群可担保,司法包赔付,欢迎咨询。 联系人:@fengyun7788 https://t.me/+KiiMxrZG5iMxM2M1 ⭐️交易必须走天成担保,所有业务联系 天成客服 @TCKF ⭐️
👍1
【需】 业务名称:快递代发 业务内容:国学引流,大量招快递代发,三通一达、极兔、京东、顺丰通通都可以,流程简单,目前快递类最安全绿色项目,新手友好,老手直接拉满价格,累计十万单奖励1888U!盘口稳定运营6年,效率高结账快 优势:全额上押,价格拉满,秒结帐 费用:18元/单 联系人:@baoma2233 ⭐️交易必须走天成担保,所有业务联系 天成客服 @TCKF ⭐️
👍1
公群3630 押金8888u 领先者·出售全行业/渗透/指定app精准数据公群 全球数据优势:(WPK/DPI/SDK/体彩/棋牌/菠菜/六合彩/3D福彩/各类游戏/贷款/助贷/催收/外贸/换汇/相亲/全球华侨华人/邮政内鬼) 联系人:@lxz87 https://t.me/+HeX0A6hJ6w5lZTE0 ⭐️交易必须走天成担保,所有业务联系 天成客服 @TCKF ⭐️
👍1
公群1618 押金1618.88u 澳博娱乐BC直盘招码卡车 诚招卡车/码车/公户车等丝滑通道,中介、散户均可咨询。车队点位置顶,中介茶水丰厚,信任是商业的基石 合作是成功的阶梯 真心换真心 联系人:@NINI166888 https://t.me/+eIqkq99IHd9jZDk9 ⭐️交易必须走天成担保,所有业务联系 天成客服 @TCKF ⭐️
👍1
【供】 【黑桃】全网最低价(欢迎比价),类目业务最全,源头极速出单 为回馈客户,推出以下特价: 民政婚姻记录 4U,人工每天稳定出单,17点截止 民政婚姻记录 5U(秒)1分钟极速回单。19点截止 假地址大头(身份证照片)秒单0.1U 无限秒,每天晚上19点截止 联系人: @y569888 ⭐️交易必须走天成担保,所有业务联系 天成客服 @TCKF ⭐️
👍1
【供】 业务名称:pos机代开,办理pos机,pos机业务 业务介绍:办理三方pos机,个人套现pos机,真商pos机,支付公司实力机构合作商,产品包含云音响,马牌,收银系统,pos机,多个支付公司pos品牌聚合,有需要产品的联系我。 代拍店铺照全套视频,资料,专业办理,合作共赢 联系人: @pos56789 ⭐️交易必须走天成担保,所有业务联系 天成客服 @TCKF ⭐️
👍1
公群5277 押金5888u 彩票分分彩挂机自动投注跟单 方案进行挂机自动投注,如有亏损包赔50%,最低本金得,5000RMB启动,日赚1000-2000RMB,切勿手痒乱下注,去玩百家乐等,只能跟我的方案 联系人:@Fc506666 https://t.me/+OBdEsMyOyxY4MzE8 ⭐️交易必须走天成担保,所有业务联系 天成客服 @TCKF ⭐️
👍1
【OK游戏中心】 9Y国际综合U台 🔥专业服务 超高限红 毫秒出款 📹视讯 — 索莱尔/DB/CQ9高限红 🎮电子 — PG/PP/CQ9 一注2000 🎱彩票 — 独家综艺28/哈希区块彩 OK游戏公群9 入驻300万U 官方小程序:@GF9Y 官方唯一客服:@KF9Y 官方唯一频道:@WWW9YCOM ⭐️交易必须走天成担保,所有业务联系 天成客服 @TCKF ⭐️
👍1
公群001 代客寻找海外多国支付通道 长期寻找一类BC海外一手源头实力支付通道,支持上押合作/通道稳定/成功率高/费率合理,实力盘口嘎嘎有量 联系人:@BCBC https://t.me/+SMSAA3fpwScyYzdl ⭐️交易必须走天成担保,所有业务联系 天成客服 @TCKF ⭐️
👍1
【OK游戏中心】 开元娱乐德州俱乐部 首冲200起就送100-2000u不等 1.平台高福利:首充奖励、转运红包, 签到奖励,大牌奖励,下午茶节日红包 2.放心娱乐,安全稳定: Web3 区块链技术去中心化发牌,每局牌路均可追溯查验 3.全真人低抽佣只撮合不做庄,小程序登录无需下载,秒充提 4:已在ok平台上押50万u,全网押金超500万u 现已入驻ok游戏平台,全网押金500万u 官方频道: @kydz8888 官方客服: @kydz9 @kydz6 ⭐️交易必须走天成担保,所有业务联系 天成客服 @TCKF ⭐️
👍1
Showing the 12 most recent of 702 posts we hold for @JiuDingSAD. 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.
@JiuDingSAD edited 5 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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.
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.
@JiuDingSAD named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“天成担保—供需广告” (@JiuDingSAD), 16,981 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/JiuDingSAD.
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.