😀😃😀😃😀😃牛逼项目看这里 🔥 没有套路 实在价格💥 💸视频验货 质量保障💸 💸出售 贾抄 精仿贾抄📣 💵包过B.C类验抄机,可线下交易 🎉 先验货后打款 一手交钱一手交货! 在线客服:@wcsjcs 双向客服:@@WCSRMB_bot
Channel
财神
@csgg889
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Cite this entry
52subscribers
+13 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003961387012 |
|---|---|
| Type | Channel |
| Username | @csgg889 |
| Created | 12 June 2026 — measured — dated from the channel’s first post |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/csgg889 |
Topic
Hacking & security — 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 29 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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 |
|---|---|---|
| 10 Oct 2026, 20:21 | 52 | -1 |
| 30 Sept 2026, 23:37 | 53 | -2 |
| 15 Sept 2026, 23:01 | 55 | +3 |
| 8 Sept 2026, 04:35 | 52 | +4 |
| 29 Aug 2026, 19:02 | 48 | +1 |
| 23 Aug 2026, 11:25 | 47 | +7 |
| 16 Aug 2026, 21:58 | 40 | +1 |
| 10 Aug 2026, 20:17 | 39 | no change |
| 7 Aug 2026, 19:31 | 39 | first reading |
Engagement
5 posts held, back to 12 June 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 5 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 22s
- Average length
- 22s
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
还有那么多人被骗,特别是私信问你要不要的,百分之一万是骗子,还有的说有担保,他妈的假钞哪里来的担保,任何真担保不担保假钞业务,你自己去问问 @XBKF 问下TG第一大担保,有这些被骗的钱不好孝顺一下家里人么?别傻了......被骗了不要来找我诉苦,我不想天天听祥林嫂一样的故事; 直接来找我面交即可,保证你拿到高质量的货,全部验完每一张货,满意付款。 在线客服:@wcsjcs 双向客服:@WCSRMB_bot
Photo, posted without a caption
😀😃😀😃😀😃牛逼项目看这里 🔥 没有套路 实在价格💥 💸视频验货 质量保障💸 💸出售 贾抄 精仿贾抄📣 💵包过B.C类验抄机,可线下交易 🎉 先验货后打款 一手交钱一手交货! 在线客服:@wcsjcs 双向客服:@@WCSRMB_bot
Channel created
Showing the 5 most recent of 5 posts we hold for @csgg889. 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.
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 10 October 2026 — this entry's latest reading, not the date you are reading this.
“财神” (@csgg889), 52 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/csgg889.
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.