Channel
@sun8j
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,082subscribers
-28 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001620194274 |
|---|---|
| Type | Channel |
| Username | @sun8j |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/sun8j |
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 19 September 2026 and assigned it the closest of 31 fixed categories, at 35% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Oct 2026, 06:17 | 1,082 | +1 |
| 30 Sept 2026, 06:37 | 1,081 | +20 |
| 16 Sept 2026, 11:56 | 1,061 | -5 |
| 12 Sept 2026, 18:00 | 1,066 | +2 |
| 8 Sept 2026, 17:58 | 1,064 | -51 |
| 3 Sept 2026, 15:55 | 1,115 | -10 |
| 31 Aug 2026, 17:05 | 1,125 | +3 |
| 25 Aug 2026, 04:54 | 1,122 | -1 |
| 22 Aug 2026, 07:46 | 1,123 | +3 |
| 19 Aug 2026, 00:34 | 1,120 | +1 |
| 15 Aug 2026, 16:46 | 1,119 | +7 |
| 12 Aug 2026, 05:25 | 1,112 | +2 |
| 11 Aug 2026, 13:45 | 1,110 | first reading |
20 posts held, back to 15 July 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 20 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
通知！ 新招商户规则： 1.必须是直盘商户且要支持加白域名，而且支持金额必须只能是平台里有的产品金额。 2.四方VPN商户要对接通道的必须上压至少两千U用于保量；用于给通道保证一赔十外加1288U的巡查红包费用。 3.为了更好的管理商户，我们将定期定时上各个商户站点查看；我们在此保证，只要被混料，我们一律 一赔十外加1288U红包。 商户收多了难免会遇见想要薅羊毛的来开户，为了更好的避免这种情况，我们现在正在开发”HTML监控“，专门用于避免一些有机分子来开了户之后更换站点页面来薅羊毛。
Posted without readable text
收条微信通道1-1000的，纯VPN，日量百w+， 天价勿扰。 有意私 @bailiang (白量全拼)
没吃饭吗
成率85+，待支付是因为并发，用户还没付款
能扛并发，加量就完事了，稳定的。 多条轮询，24小时不间断
原生支付宝成率在线，稳定开启。1-1000，费率1.5。 申请上量
以下这些通道开启中： 【通道名称】：VPN专用 （支付宝原生拉起） 【通道编码】： 【通道金额】：1-1000 【通道成率】：85-95% 【通道规则】： 只可进VPN、机场 🈲禁止：发卡、AI（⚠️需配置其他通道）、 TV、博彩、楼凤、色敲、色刷、空降、直播、CSGO、私服、黄游、漫画、小说、纯视频、打赏、虚假商城、买A发B、诈骗、刷单、三黑、资金盘、棋牌…等一切非通道准入的VPN类都算混料。 正常投诉1:1退款，专投1:1赔付，涉及黄赌炸刷单字眼1:10赔付。 ⚠️涉黄涉赌涉炸一律按5万一户赔偿。全网放巡查混量需要给巡查1888u红包。 ✅开启默认接受以上规则不扯皮。 通道费率1.5% 【通道名称】：VPN专用 （支付宝原生拉起） 【通道编码】： 【通道金额】：1-1000 【通道成率】：85-95% 【通道规则】： 只可进VPN、机场 🈲禁止：发卡、AI（⚠️需配置其他通道）、 TV、博彩、楼凤、色敲…
支付宝大额通道晚点恢复
以下通道长期开启着的，欢迎实力商户来谈合作： 【通道名称】：VPN专用 （微信原生） 【通道编码】： 【通道金额】：1-1000 【通道成率】：70-90% 【通道规则】： 只可进VPN、机场 🈲禁止：发卡、AI（⚠️需配置其他通道）、 TV、博彩、楼凤、色敲、色刷、空降、直播、CSGO、私服、黄游、漫画、小说、纯视频、打赏、虚假商城、买A发B、诈骗、刷单、三黑、资金盘、棋牌…等一切非通道准入的VPN类都算混料。 正常投诉1:1退款，专投1:1赔付，涉及黄赌炸刷单字眼1:10赔付。 ⚠️涉黄涉赌涉炸一律按5万一户赔偿。全网放巡查混量需要给巡查1888u红包。 ✅开启默认接受以上规则不扯皮。 通道费率最低2%-3% （看量级） ------------------------------------------------------------------------------------------------…
后面根据市场行情我们会进行对应调整，目前成本下不去，成本能下去了我会放低价通道出来跑。
加量，额度无限
Showing the 12 most recent of 20 posts we hold for @sun8j. 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.
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 7 October 2026 — this entry's latest reading, not the date you are reading this.
“九九VPN支付通道（专注VPN）” (@sun8j), 1,082 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/sun8j.
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.