Channel
@flwpaimai
On this record: Topic · Previous handles · Growth · Engagement · Posts · Citations · Cite this entry
7,041subscribers
-2,209 since we began measuring on 10 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001116839499 |
|---|---|
| Type | Channel |
| Usernames | @flwpaimai @NXCUsdt @yxpaimai |
| Created | Between 1 February 2017 and 31 December 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 September 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/flwpaimai |
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 25 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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 the other topics.
@flwpaimai was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 19:11 | 7,041 | -273 |
| 9 Nov 2026, 07:59 | 7,314 | -3 |
| 8 Nov 2026, 06:00 | 7,317 | -9 |
| 5 Nov 2026, 12:50 | 7,326 | -2 |
| 2 Nov 2026, 04:28 | 7,328 | -58 |
| 30 Oct 2026, 14:36 | 7,386 | -164 |
| 27 Oct 2026, 13:16 | 7,550 | -98 |
| 24 Oct 2026, 09:26 | 7,648 | -26 |
| 21 Oct 2026, 00:57 | 7,674 | -61 |
| 17 Oct 2026, 21:59 | 7,735 | -283 |
| 15 Oct 2026, 00:59 | 8,018 | -487 |
| 11 Oct 2026, 16:16 | 8,505 | -662 |
| 4 Oct 2026, 18:57 | 9,167 | +4,998 |
| 27 Sept 2026, 13:21 | 4,169 | -392 |
| 25 Sept 2026, 05:16 | 4,561 | -2,679 |
| 17 Sept 2026, 04:39 | 7,240 | -439 |
| 15 Sept 2026, 10:00 | 7,679 | -793 |
| 12 Sept 2026, 22:41 | 8,472 | -150 |
| 12 Sept 2026, 05:19 | 8,622 | -209 |
| 11 Sept 2026, 13:51 | 8,831 | first reading |
20 posts held, back to 9 September 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 18 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 9 September 2026. An engagement rate over an empty window would be a number about nothing.
🔴 TRON USDT 已冻结 地址：TDLRfw4ZAGquYDPpDpviXrJPcsyRLMS7Uq 状态：冻结已执行 冻结时间：2026-09-10 03:56:18（北京时间） 节点查询余额：71115.27972 USDT 签名确认/执行交易：3deb68c55a541ab21e33c379d0c375b6ab1f968d74664f6138bf10b53388510d 历史事件不等于当前冻结状态。 余额为查询时结果，非事件时余额；实时记录以链上最终确认为准。 冻结不等于诈骗认定。 检测结果可能存在延迟，不代表完整安全评估。
🟠 TRON USDT 即将冻结（已发起提案） 地址：TDLRfw4ZAGquYDPpDpviXrJPcsyRLMS7Uq 状态：已发起冻结提案，等待确认执行 提案时间：2026-09-10 03:55:21（北京时间） 节点查询余额：71115.27972 USDT 发起提案交易：d76cc1cf9b09a396188e259880154a64e0594ba63062ab2bfce72fc67833cf58 提案不代表已冻结，可能未执行；请查询最新状态。 余额为查询时结果，非事件时余额；实时记录以链上最终确认为准。 冻结不等于诈骗认定。 检测结果可能存在延迟，不代表完整安全评估。
🔴 TRON USDT 已冻结 地址：TMPWDhiDNKjaoZb46YPxbSq52EeLEkDwtr 状态：冻结已执行 冻结时间：2026-09-10 03:50:21（北京时间） 节点查询余额：43020 USDT 签名确认/执行交易：6bd61bba4e53500b568a929768824360e2810b783e445bac05c6c6800c3b12d3 历史事件不等于当前冻结状态。 余额为查询时结果，非事件时余额；实时记录以链上最终确认为准。 冻结不等于诈骗认定。 检测结果可能存在延迟，不代表完整安全评估。
🔴 TRON USDT 已冻结 地址：TG9qzUHEEvWVocCGQgyNsxGsq5VqwiPPFv 状态：冻结已执行 冻结时间：2026-09-10 03:50:21（北京时间） 节点查询余额：50319.994733 USDT 签名确认/执行交易：077ad0c2d70df1e666efecf5b96790a3ea7fb9862509a83dc6c343a165fa7680 历史事件不等于当前冻结状态。 余额为查询时结果，非事件时余额；实时记录以链上最终确认为准。 冻结不等于诈骗认定。 检测结果可能存在延迟，不代表完整安全评估。
🔴 TRON USDT 已冻结 地址：TLzN4JbPqGc1X7qpZ8sqQg8b2iBJ8PYzqA 状态：冻结已执行 冻结时间：2026-09-10 03:50:15（北京时间） 节点查询余额：0 USDT 签名确认/执行交易：ead3fcc1b4fe3be784073b27789850ed48a6ada0e4a09e294d4eb7db21916c5b 历史事件不等于当前冻结状态。 余额为查询时结果，非事件时余额；实时记录以链上最终确认为准。 冻结不等于诈骗认定。 检测结果可能存在延迟，不代表完整安全评估。
🔴 TRON USDT 已冻结 地址：TSkhxNzVyKBwnDfMSPUUTMYGDXXwkunMiB 状态：冻结已执行 冻结时间：2026-09-10 03:50:12（北京时间） 节点查询余额：32862.313224 USDT 签名确认/执行交易：4f186c1fbb599b9c150ee42c7d47c939d3d010ee02d59d2c0db78d57be7c28a4 历史事件不等于当前冻结状态。 余额为查询时结果，非事件时余额；实时记录以链上最终确认为准。 冻结不等于诈骗认定。 检测结果可能存在延迟，不代表完整安全评估。
🔴 TRON USDT 已冻结 地址：TBUkR8Uqd3Lf4K4n6EVdoaVeuYXkSYWwQ7 状态：冻结已执行 冻结时间：2026-09-10 03:49:57（北京时间） 节点查询余额：2297.270048 USDT 签名确认/执行交易：1d8acb74e7a2c1a77dbcc566355d9d3529360b8d31beb9d36aee2e0e829c5bd9 历史事件不等于当前冻结状态。 余额为查询时结果，非事件时余额；实时记录以链上最终确认为准。 冻结不等于诈骗认定。 检测结果可能存在延迟，不代表完整安全评估。
🔴 TRON USDT 已冻结 地址：TFqEQ7inHv1cXW5AashG7yjy2cQraJ7mk7 状态：冻结已执行 冻结时间：2026-09-10 03:49:51（北京时间） 节点查询余额：92147.03082 USDT 签名确认/执行交易：408fecd710b9f53b2ef40ace8858f8f9231d4046b1079503f68bf6ef1342f122 历史事件不等于当前冻结状态。 余额为查询时结果，非事件时余额；实时记录以链上最终确认为准。 冻结不等于诈骗认定。 检测结果可能存在延迟，不代表完整安全评估。
🔴 TRON USDT 已冻结 地址：TEotn55PBm3dGH3DqrkdDR3bb72FtN9Vxh 状态：冻结已执行 冻结时间：2026-09-10 03:49:42（北京时间） 节点查询余额：264677.310177 USDT 签名确认/执行交易：63cafc7302ea36f713733aae2d8a7bfe921bfc4cca92587be2d620ccb940168f 历史事件不等于当前冻结状态。 余额为查询时结果，非事件时余额；实时记录以链上最终确认为准。 冻结不等于诈骗认定。 检测结果可能存在延迟，不代表完整安全评估。
🔴 TRON USDT 已冻结 地址：TD8HgFo5zGFSBZVkeD2EMCNrGBNTTMVnwy 状态：冻结已执行 冻结时间：2026-09-10 03:49:39（北京时间） 节点查询余额：1279.573932 USDT 签名确认/执行交易：00056918df618a88f64e0a943a96eaa7f9fde06cdfc529549ffde7d1411c1368 历史事件不等于当前冻结状态。 余额为查询时结果，非事件时余额；实时记录以链上最终确认为准。 冻结不等于诈骗认定。 检测结果可能存在延迟，不代表完整安全评估。
🔴 TRON USDT 已冻结 地址：TPKBCbsFRL3Z7LR43m1fhWQz4d3BGkgsCv 状态：冻结已执行 冻结时间：2026-09-10 03:49:36（北京时间） 节点查询余额：1000 USDT 签名确认/执行交易：04cbb210c4e3c8d4e8f090d933ef468d6eadbc560cca65da036c7674bc91af6e 历史事件不等于当前冻结状态。 余额为查询时结果，非事件时余额；实时记录以链上最终确认为准。 冻结不等于诈骗认定。 检测结果可能存在延迟，不代表完整安全评估。
🔴 TRON USDT 已冻结 地址：TBvYgN1EG1t4JA6qyFE1ww5YrtnJNSkjE2 状态：冻结已执行 冻结时间：2026-09-10 03:49:27（北京时间） 节点查询余额：6836 USDT 签名确认/执行交易：fd6246382d950ff86a5a07e7e8ae97fa97f0ceb9900047a254b8e000abdee50c 历史事件不等于当前冻结状态。 余额为查询时结果，非事件时余额；实时记录以链上最终确认为准。 冻结不等于诈骗认定。 检测结果可能存在延迟，不代表完整安全评估。
Showing the 12 most recent of 20 posts we hold for @flwpaimai. 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 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.
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“南希USDT冻结播报” (@flwpaimai), 7,041 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/flwpaimai.
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.