😳通道编码:8080 微信 双端 淘宝固额100 【1️⃣0️⃣❤️8️⃣】 😳通道编码:8081 微信 IOS 淘宝固额200 【9️⃣❤️8️⃣】 注意费率上调!!注意费率上调!!
Signed 史迪仔 PAYYOV

Channel
@nfpay
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
2,311subscribers
+102 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002688995102 |
|---|---|
| Type | Channel |
| Usernames | @mrrra @nfpay @payyov |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 41 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/nfpay |
Other / unclassifiable — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 39% 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 |
|---|---|---|
| 19 Sept 2026, 09:37 | 2,311 | +2 |
| 18 Sept 2026, 16:40 | 2,309 | +1 |
| 18 Sept 2026, 11:17 | 2,308 | +11 |
| 15 Sept 2026, 05:39 | 2,297 | +2 |
| 13 Sept 2026, 22:19 | 2,295 | -1 |
| 13 Sept 2026, 18:22 | 2,296 | -3 |
| 11 Sept 2026, 05:18 | 2,299 | +3 |
| 10 Sept 2026, 08:59 | 2,296 | -2 |
| 10 Sept 2026, 01:56 | 2,298 | -8 |
| 6 Sept 2026, 08:59 | 2,306 | +7 |
| 5 Sept 2026, 07:59 | 2,299 | +4 |
| 4 Sept 2026, 15:00 | 2,295 | +9 |
| 1 Sept 2026, 23:46 | 2,286 | +6 |
| 1 Sept 2026, 09:27 | 2,280 | +3 |
| 1 Sept 2026, 04:18 | 2,277 | +6 |
| 30 Aug 2026, 01:26 | 2,271 | +1 |
| 29 Aug 2026, 19:37 | 2,270 | +1 |
| 28 Aug 2026, 23:49 | 2,269 | +5 |
| 27 Aug 2026, 00:29 | 2,264 | no change |
| 26 Aug 2026, 23:15 | 2,264 | first reading |
20 posts held, back to 7 August 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 3 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 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
😳通道编码:8080 微信 双端 淘宝固额100 【1️⃣0️⃣❤️8️⃣】 😳通道编码:8081 微信 IOS 淘宝固额200 【9️⃣❤️8️⃣】 注意费率上调!!注意费率上调!!
Signed 史迪仔 PAYYOV
🫧:支付宝 抖音原生固额30 【双端】 通道编码:8170 通道金额:30 即刻起通道费率上调为【⚡️7️⃣❤️0️⃣】 即刻起通道费率上调为【⚡️7️⃣❤️0️⃣】 注意费率上调!!注意费率上调!!注意费率上调!!
Signed 史迪仔 PAYYOV
❌通道编码:8066 支付宝 小小额 原生 1-9 |切停 ❌❌❌ ❌通道编码:8066 支付宝 小小额 原生 1-9 |切停 ❌❌❌
Signed 史迪仔 PAYYOV
🫧:支付宝 H5 高端 GMM【双端 or PC】 通道编码:8028 😳 通道金额:300-450 注意限额 即刻起通道费率下调为【1️⃣3️⃣❤️0️⃣】 即刻起通道费率下调为【1️⃣3️⃣❤️0️⃣】
Signed 史迪仔 PAYYOV
❌通道编码:8170 支付宝抖音原生固额30 |切停 ❌❌❌ ❌通道编码:8170 支付宝抖音原生固额30 |切停 ❌❌❌
Signed 史迪仔 PAYYOV
🫧:支付宝旗舰固额话费50|100 【双端】 通道编码:8016 通道金额:50|100 即刻起通道费率为【9️⃣❤️3️⃣】 即刻起通道费率为【9️⃣❤️3️⃣】
Signed 史迪仔 PAYYOV
❌通道编码:8182 支付宝 代付 200 |切停 ❌❌❌ ❌通道编码:8182 支付宝 代付 200 |切停 ❌❌❌ 额度已满
Signed 史迪仔 PAYYOV
🫧:支付宝 抖音原生固额30 【双端】 通道编码:8170 通道金额:30 即刻起通道费率上调为【⚡️6️⃣❤️5️⃣】 即刻起通道费率上调为【⚡️6️⃣❤️5️⃣】 注意费率上调!!注意费率上调!!注意费率上调!!
Signed 史迪仔 PAYYOV
🫧: 支付宝 小小额 纯原生【双端】 通道编码:8066😳 通道金额:1-9 即刻起通道费率下调为:【⚡️3️⃣❤️7️⃣】 即刻起通道费率下调为:【⚡️3️⃣❤️7️⃣】
Signed 史迪仔 PAYYOV
❌通道编码:8170 支付宝抖音原生固额30 |切停 ❌❌❌ ❌通道编码:8170 支付宝抖音原生固额30 |切停 ❌❌❌
Signed 史迪仔 PAYYOV
🫧:支付宝 抖音原生固额30 【双端】 通道编码:8170 通道金额:30 通道费率为【⚡️5️⃣❤️8️⃣】 通道费率为【⚡️5️⃣❤️8️⃣】
Signed 史迪仔 PAYYOV
⚡️今日诺菲(@NFPAY)08/07开启通道 播报 诺菲微信专区 😳8080 微信 双端 淘宝固额100 【10.3】100【双端】 😳8081 微信 IOS 淘宝固额200 【9.2】200【单端】 😳8087 微信小额原生 【2.3】10-100【双端】 😳8163 微信 京东 直付【2.5】10-50|100~1000 整百)【双端】 诺菲支付宝UID纯码 😳8006 小额 UID【9.0】300~1000 【双端】 😳8007 中额 UID【8.0】500~3000 【双端】 😳8008 大额 UID【7.0】800~10000【双端】 😳8010 超大 UID【5.0】2000-50000【双端】 诺菲支付宝金条专区 😳7777 支付宝 纯原 金条 企业版【10.5】200-500【双端】 😳8171 支付宝100起小金条【10.5】100-200【双端】 😳8172 支付宝 200起小金条【8…
Signed 史迪仔 PAYYOV
Showing the 12 most recent of 20 posts we hold for @nfpay. 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.
Named by 3 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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“诺菲(NFPAY) 官方” (@nfpay), 2,311 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/nfpay.
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.