Channel
@ksdk132
On this record: Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry
28,975subscribers
-1,104 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002621274172 |
|---|---|
| Type | Channel |
| Username | @ksdk132 |
| Created | 4 June 2025 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/ksdk132 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 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 | -27 |
| 20 Aug 2026, 15:16 | 29,588 | -15 |
| 19 Aug 2026, 15:43 | 29,603 | -56 |
| 18 Aug 2026, 13:54 | 29,659 | -40 |
| 17 Aug 2026, 15:06 | 29,699 | -58 |
| 16 Aug 2026, 07:37 | 29,757 | -38 |
| 14 Aug 2026, 16:05 | 29,795 | first reading |
2 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 58 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 2 posts for this entry, the most recent from 22 February 2026. An engagement rate over an empty window would be a number about nothing.
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.
😀 必安担保｜稳市护航专项行动 近期陆续有公群老板咨询：被其他担保平台跑路或者倒闭了，转入必安担保是否享有专项扶持。 据悉近期已跑路或倒闭担保如下： 好旺担保、土豆担保、超乖担保、火狐担保 、永盛担保、汇金担保、大爷担保、长安担保、海外担保、旺旺担保、索隆担保、顶尖担保、柬埔寨担保、无忧担保、新币旗下万邦海外... 为帮助受影响公群尽快恢复运营，提振行业信心，必安担保决定推出以下扶持政策： 🔥 受影响公群转入必安担保，可享： ✅ 开群首月免租 ✅ 赠送3条供需 @BAGX @USDD 广告扶持 ✅ 赠送 @CPDD 资源广场管理席位 ✅ 赠送 @BAGQ 公群新秀榜曝光位 点击继续查看更多详情... 📌担保赞助商固定置顶广告
Channel created
Showing the 2 most recent of 2 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.
@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.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“卡商卡盾频道” (@ksdk132), 28,975 subscribers as measured 8 September 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.