微信通道暂时维护 可用后会第一时间通知

Channel
池雨支付
@chiyu_pay
On this record: Growth · Engagement · Posts · Citations · Cite this entry
89subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002384873483 |
|---|---|
| Type | Channel |
| Username | @chiyu_pay |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 10 September 2026 |
| On Telegram | t.me/chiyu_pay |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 12:03 | 89 | -1 |
| 17 Aug 2026, 18:36 | 90 | +1 |
| 9 Aug 2026, 21:30 | 89 | no change |
| 9 Aug 2026, 21:17 | 89 | first reading |
Engagement
20 posts held, back to 5 February 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 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
凌晨出现了网站无法访问,现已解决
很抱歉凌晨出现了CDN故障 现已恢复 您现在无需做任何操作
抱歉今天结算出现延迟 正在结算
我们承诺凡是由我们这边掉单的订单出现的投诉,由我们承担损失不会扣您的余额 过去我们也一直这样践行,保障各位不遭受损失,感谢各位客户的持久陪伴
pay前缀的域名被多地屏蔽 请各位没有使用备案域名(前缀为api)的用户更换域名 登录网站在接口信息中查看,也可联系 @lucaoly
已完成
停机更新中 预计五分钟内完成
请所有使用v2board及其衍生面板(xboard xiaov2b等)的老板注意 v2b等面板出现漏洞,部分用户的账号可以被盗,并冒充用户发起工单提现佣金 各位老板如有遇到用户工单提现佣金务必先与用户联系核实
出于安全考虑,前台订单记录/结算记录只显示近一个月,首页总结算金额和总订单数将不显示 但数据仍然有保留,如果您需要查询一个月以外的订单,请联系 @lucaoly
已恢复
正在紧急扩容服务器中 预计中断时间5分钟
Showing the 12 most recent of 20 posts we hold for @chiyu_pay. 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.
Mentions
Named by 1 registered channel — 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.
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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“池雨支付” (@chiyu_pay), 89 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/chiyu_pay.
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.