Posted without readable text

Channel
赌牌 @DuPai
@ksdk132
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry
45,170subscribers
+15,091 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1002621274172 |
|---|---|
| Type | Channel |
| Username | @ksdk132 |
| Description | 玩游戏 · 认赌牌 | 有必安 · 心必安! |
| Created | 4 June 2025 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 2 October 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 2 October 2026 |
| On Telegram | t.me/ksdk132 |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Oct 2026, 09:41 | 45,170 | +16,624 |
| 18 Sept 2026, 15:57 | 28,546 | -111 |
| 16 Sept 2026, 06:22 | 28,657 | -52 |
| 14 Sept 2026, 14:00 | 28,709 | -44 |
| 13 Sept 2026, 03:36 | 28,753 | -74 |
| 11 Sept 2026, 07:01 | 28,827 | -148 |
| 8 Sept 2026, 12:57 | 28,975 | -95 |
| 5 Sept 2026, 03:40 | 29,070 | -56 |
| 3 Sept 2026, 07:03 | 29,126 | -35 |
| 1 Sept 2026, 23:57 | 29,161 | -39 |
| 1 Sept 2026, 01:35 | 29,200 | -47 |
| 31 Aug 2026, 00:38 | 29,247 | -41 |
| 30 Aug 2026, 00:13 | 29,288 | -21 |
| 28 Aug 2026, 21:14 | 29,309 | -39 |
| 27 Aug 2026, 17:54 | 29,348 | -17 |
| 26 Aug 2026, 15:15 | 29,365 | -59 |
| 25 Aug 2026, 12:09 | 29,424 | -21 |
| 24 Aug 2026, 15:34 | 29,445 | -68 |
| 22 Aug 2026, 20:13 | 29,513 | -48 |
| 21 Aug 2026, 12:16 | 29,561 | first reading |
Engagement
5 posts held, back to 4 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 81 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 2.54%
- avg views ÷ 45,170 subscribers
- Avg views / post
- 1,150
- 3 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 3
- of 5 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.
| Window | Rolling 30 days · latest post in window 18 September 2026 |
|---|---|
| Posts held | 5 (4 June 2025 – 18 September 2026) |
| Views total | 3,440 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 20 Sept 2026, 08: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
- 5
- Videos
- 4
- Links
- 25
Lifetime counters from Telegram’s own channel header, read 3 October 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.
- Video runtime
- 7m 06s
- Average length
- 7m 06s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
😀😃😀😄😃😃😀 💰资金类 • 码接回U公群 • 卡接回U公群 • 白资收出U代付/送存现金承兑/三方支付 • 人头卡商: 银行卡 公户 取现等 • 支付宝/微信|下载付/设置码 • 资金窗口:招车/找料/跑分/红包 • 核销/回收:香烟 礼品卡 /话费
🔥 《担保风云之我在必安重生》
😀 必安担保|稳市护航专项行动 近期陆续有公群老板咨询:被其他担保平台跑路或者倒闭了,转入必安担保是否享有专项扶持。 据悉近期已跑路或倒闭担保如下: 好旺担保、土豆担保、超乖担保、火狐担保 、永盛担保、汇金担保、大爷担保、长安担保、海外担保、旺旺担保、索隆担保、顶尖担保、柬埔寨担保、无忧担保、新币旗下万邦海外... 为帮助受影响公群尽快恢复运营,提振行业信心,必安担保决定推出以下扶持政策: 🔥 受影响公群转入必安担保,可享: ✅ 开群首月免租 ✅ 赠送3条供需 @BAGX @USDD 广告扶持 ✅ 赠送 @CPDD 资源广场管理席位 ✅ 赠送 @BAGQ 公群新秀榜曝光位 点击继续查看更多详情... 📌担保赞助商固定置顶广告
Channel created
Showing the 5 most recent of 5 posts we hold for @ksdk132. 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.
Posts edited after publishing
@ksdk132 edited 1 post 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.
- First edit seen
- 28 August 2026
- Most recent edit
- 28 August 2026
Mentions
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 2 October 2026 — this entry's latest reading, not the date you are reading this.
“赌牌 @DuPai” (@ksdk132), 45,170 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/ksdk132.
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.