Channel
@liumei66
On this record: Growth · Engagement · Posts · Citations · Cite this entry
87subscribers
-4 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001797199790 |
|---|---|
| Type | Channel |
| Username | @liumei66 |
| Created | Between 1 January 2022 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/liumei66 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 03:19 | 87 | -2 |
| 4 Sept 2026, 00:41 | 89 | -1 |
| 19 Aug 2026, 18:52 | 90 | -1 |
| 13 Aug 2026, 09:35 | 91 | no change |
| 13 Aug 2026, 05:32 | 91 | first reading |
18 posts held, back to 5 September 2025 — 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 18 posts for this entry, the most recent from 1 June 2026. An engagement rate over an empty window would be a number about nothing.
集团总部直营 中国支付： 👩🦯 K豆钱包 / KDpay 🫸 C币钱包 / CBpay 🤯 JD钱包 / JDpay 😶🌫️ 365钱包 / 365pay ❤️红豆钱包 / HDpay DFPAY 💸支付宝UID模式：100-50000 支付宝成交率高 ULPAY 实现🔤🔤🔤🔤充提 实时到账、自动识别、秒级回调。 所有业务招商招代理，请联系总部🤏 艾妹 • @aimei3 六妹 • @liumei6 艾菲 • @cyang5200 @aifei28 🥳🤨😏🥺 欢迎关注 总部频道 保持联系 @aifei68
六妹 艾菲 C币钱包 K豆钱包 全球 短信 电销 线路 通道 pinned a photo
⚡️⚡️⚡️⚡️⚡️USDT收付回调😀😀😀😀😀 🔥ULPAY专为虚拟币用户提供自动收款与付款解决方案。 实现 😍😍😜😍 实时到账、自动识别、秒级回调。 无需人工盯账，无需复杂操作，一切交给系统自动完成。 😄 安全可靠，资金保障 👍👍 😃 到账即回调，实时可用 👍👍 😄 自动查验，出入无忧 👍👍 😃 到账即回调，实时可用 👍👍 😃 全自动化，解放人力 👍👍 😀😀😀😀⚡️😀😀 😀😀😀⚡️ 交易时间：🤣🤣小时⚡️ ⚡️到账时间：实时 ⚡️客服运维：🤣🤣小时 ⚡️充值单笔限额：😘😘😀🤣😘😘 ⚡️付单笔限额：😘😘😀🤣😘😘 所有业务招商招代理，请联系总部🤏 艾妹 • @aimei3 六妹 • @liumei6 艾菲 • @cyang5200 @aifei28 🥳🤨😏🥺 欢迎关注 总部频道 保持联系 @aifei68
集团总部直营 中国支付： 👩🦯 K豆钱包 / KDpay 🫸 C币钱包 / CBpay 🤯 JD钱包 / JDpay 😶🌫️ 365钱包 / 365pay ❤️红豆钱包 / HDpay 所有业务招商招代理，请联系总部🤏 艾妹 • @aimei3 六妹 • @liumei6 艾菲 • @cyang5200 @aifei28 🥳🤨😏🥺 欢迎关注 总部频道 保持联系 @aifei68
集团总部直营 中国支付： 👩🦯 K豆钱包 / KDpay 🫸 C币钱包 / CBpay 🤯 JD钱包 / JDpay 😶🌫️ 365钱包 / 365pay ❤️红豆钱包 / HDpay 所有业务招商招代理，请联系总部🤏 艾妹 • @aimei3 六妹 • @liumei6 艾菲 • @cyang5200 @aifei28 🥳🤨😏🥺 欢迎关注 总部频道 保持联系 @aifei68
集团总部直营 中国支付： 👩🦯 K豆钱包 / KDpay 🫸 C币钱包 / CBpay 🤯 JD钱包 / JDpay 😶🌫️ 365钱包 / 365pay ❤️红豆钱包 / HDpay 所有业务招商招代理，请联系总部商务 🤏 艾妹 • @aimei3 六妹 • @liumei6 艾菲 • @cyang5200 @aifei28 🥳🤨😏🥺 欢迎关注 总部频道 保持联系 @aifei68
易呼语音 😦 中国电销系统线路 目前有 国显、国际显、港显 🉑选择配置 需要更新配置请@我们 艾妹 • @aimei3 六妹 • @liumei6 艾菲 • @cyang5200 🥳🤨😏🥺 欢迎关注 总部频道 保持联系 @aifei68
总部直营 中国支付： 👩🦯 K豆钱包 / KDpay 🫸 C币钱包 / CBpay 🤯 JD钱包 / JDpay 😶🌫️ 365钱包 / 365pay ❤️红豆钱包 / HDpay 所有业务招商招代理，请联系总部商务 🤏 艾妹 • @aimei3 六妹 • @liumei6 艾菲 • @cyang5200 @aifei28 🥳🤨😏🥺 欢迎关注 总部频道 保持联系 @aifei68
总部直营 中国支付： 👩🦯 K豆钱包 / KDpay 🫸 C币钱包 / CBpay 🤯 JD钱包 / JDpay 😶🌫️ 365钱包 / 365pay ❤️红豆钱包 / HDpay 所有业务招商招代理，请联系总部商务 🤏 艾妹 • @aimei3 六妹 • @liumei6 艾菲 • @cyang5200 @aifei28 🥳🤨😏🥺 欢迎关注 总部频道 保持联系 @aifei68
中国语音 易呼通知： 最新 BC线路 中国线路包（港显） 来显：港显 需要更新配置请@我们 艾妹 • @aimei3 六妹 • @liumei6 艾菲 • @cyang5200 🥳🤨😏🥺 欢迎关注 总部频道 保持联系 @aifei68
集团总部直营 Upay印度钱包 目前已经优化到最简易版本了（无需KYC,快捷买币） 所有业务招商招代理，请联系总部商务 🤏 艾妹 • @aimei3 六妹 • @liumei6 艾菲 • @cyang5200 🥳🤨😏🥺 欢迎关注 总部频道 保持联系 @aifei68
欢迎咨询 巴西支付 艾妹 • @aimei3 六妹 • @liumei6 艾菲 • @cyang5200
Showing the 12 most recent of 18 posts we hold for @liumei66. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“六妹 艾菲 C币钱包 K豆钱包 全球 短信 电销 线路 通道” (@liumei66), 87 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/liumei66.
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.