19 Feb 2022, 04:53 UTC≈1,750 viewsread 31 August 2026
【通道编码】701微信IOS优涂电费 🔥 🔥【推荐】 【任意金额】：100-3000 （50的陪数） 认准iOS，安卓勿进成功率80（50的倍数） 全力冲冲冲
Signed 太阳
Channel
龙门科技-通知频道
@jinyuanpay
On this record: Growth · Engagement · Posts · Citations · Cite this entry
88subscribers
-1 since we began measuring on 31 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001479527267 |
|---|---|
| Type | Channel |
| Username | @jinyuanpay |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 31 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 17 September 2026 |
| On Telegram | t.me/jinyuanpay |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 14:57 | 88 | -1 |
| 31 Aug 2026, 14:57 | 89 | no change |
| 31 Aug 2026, 06:47 | 89 | first reading |
Engagement
20 posts held, back to 18 February 2022 — 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 19 February 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
19 Feb 2022, 04:45 UTC≈1,720 viewsread 31 August 2026
【支付类型】：iOS支付宝H5 话费 【通道编码】：606 【固定金额】：30 50 100 200 【 成 功 率】 ： 60+
Signed 太阳
19 Feb 2022, 03:34 UTC≈1,590 viewsread 31 August 2026
Photo
Photo, posted without a caption
Signed 太阳
19 Feb 2022, 03:13 UTC≈1,060 viewsread 31 August 2026
Video
Video, posted without a caption
Signed 太阳
19 Feb 2022, 03:12 UTC788 viewsread 31 August 2026
【通道编码】：801微信话费🔥🔥🔥 【固定金额】：50 100 200 抗诉，全层可开抗 无限并发 【通道编码】：802微信慢充🔥🔥🔥 【固定金额】：30 50 100 200 抗诉，全层可开抗 无限并发 【通道编码】701微信IOS优涂电费 🔥 🔥【推荐】 【任意金额】：100-3000 （50的陪数） 认准iOS，安卓勿进成功率80 【通道编码】：702中油优途IOS天然气 【任意金额】300-4500 🔥 🔥 认准iOS，安卓勿进成功率80 【通道编码】：703支付宝iOS-天然气 【任意金额】300-4500 🔥 🔥🔥 规则：全层上并发抗投诉 认准iOS，安卓勿进成功率60 【通道编码】902支付宝慢充【推荐】 【固定金额】 30|50|100|200🔥 🔥🔥 ：抗诉，全层可开抗 无限并发 【通道编码】912支付宝零花钱【推荐】 【固定金额】 200-300🔥 🔥🔥 ：抗诉，全层可开抗 无限并发 成功率…
Signed 太阳
19 Feb 2022, 02:15 UTC671 viewsread 31 August 2026
【通道编码】：801微信话费🔥🔥🔥 【固定金额】：50 100 200 抗诉，全层可开抗 无限并发 【通道编码】：802微信慢充🔥🔥🔥 【固定金额】：30 50 100 200 抗诉，全层可开抗 无限并发 【通道编码】701微信IOS优涂电费 🔥 🔥【推荐】 【任意金额】：100-3000 （50的陪数） 认准iOS，安卓勿进成功率80 【通道编码】：702中油优途IOS天然气 【任意金额】300-4500 🔥 🔥 认准iOS，安卓勿进成功率80 【通道编码】：703支付宝iOS-天然气 【任意金额】300-4500 🔥 🔥🔥 规则：全层上并发抗投诉 认准iOS，安卓勿进成功率60 【通道编码】912支付宝零花钱【推荐】 【固定金额】 200-300🔥 🔥🔥 ：抗诉，全层可开抗 无限并发 成功率40+ 【通道编码】：916支付宝口令红包 【任意金额】 2000-10000🔥🔥🔥 大额无忧，首选通道 🔥 抗投诉…
Signed 太阳
18 Feb 2022, 20:06 UTC542 viewsread 31 August 2026
【通道编码】：916支付宝口令红包。 切停。 切停。 切停
Signed only you
18 Feb 2022, 16:14 UTC544 viewsread 31 August 2026
Video
Video, posted without a caption
Signed only you
18 Feb 2022, 16:14 UTC508 viewsread 31 August 2026
【通道编码】：916支付宝口令红包 【任意金额】 2000-10000🔥🔥🔥 大额无忧，首选通道 🔥 抗投诉，抗并发，可全层 ‼️🔜温馨提示：口令红包（玩家支付流程） 1. 打开支付宝搜索“口令红包” 2.发送口令红包后，生成数字口令 3.将数字口令填入支付界面框内，秒到账 🅱️*玩家只要用过一次，就熟悉了，成功率非常好，玩家随意发包，不会前端风控‼️
Signed only you
18 Feb 2022, 16:10 UTC489 viewsread 31 August 2026
Video
Video, posted without a caption
Signed only you
18 Feb 2022, 16:10 UTC502 viewsread 31 August 2026
【通道编码】：801微信话费🔥🔥🔥 【固定金额】：50 100 200 抗诉，全层可开抗 无限并发 【通道编码】：802微信慢充🔥🔥🔥 【固定金额】：30 50 100 200 抗诉，全层可开抗 无限并发 【通道编码】701微信IOS优涂电费 🔥 🔥【推荐】 【任意金额】：100-3000 （50的陪数） 认准iOS，安卓勿进成功率80 【通道编码】：702中油优途IOS天然气 【任意金额】300-4500 🔥 🔥 认准iOS，安卓勿进成功率80 【通道编码】：703支付宝iOS-天然气 【任意金额】300-4500 🔥 🔥🔥 规则：全层上并发抗投诉 认准iOS，安卓勿进成功率60 【通道编码】912支付宝零花钱【推荐】 【固定金额】 200-300🔥 🔥🔥 ：抗诉，全层可开抗 无限并发 成功率40+
Signed only you
18 Feb 2022, 15:01 UTC530 viewsread 31 August 2026
Photo
Photo, posted without a caption
Signed only you
Showing the 12 most recent of 20 posts we hold for @jinyuanpay. 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 2 registered channels — 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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“龙门科技-通知频道” (@jinyuanpay), 88 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/jinyuanpay.
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.