Channel
@uuwallet_fx_cn
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
3,801subscribers
+91 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002073416621 |
|---|---|
| Type | Channel |
| Username | @uuwallet_fx_cn |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/uuwallet_fx_cn |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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 |
|---|---|---|
| 18 Sept 2026, 16:15 | 3,801 | +5 |
| 14 Sept 2026, 15:56 | 3,796 | -2 |
| 10 Sept 2026, 20:16 | 3,798 | +27 |
| 5 Sept 2026, 22:40 | 3,771 | -2 |
| 1 Sept 2026, 19:57 | 3,773 | +10 |
| 29 Aug 2026, 18:54 | 3,763 | +3 |
| 26 Aug 2026, 19:19 | 3,760 | +11 |
| 23 Aug 2026, 20:06 | 3,749 | +5 |
| 20 Aug 2026, 08:02 | 3,744 | +25 |
| 17 Aug 2026, 15:35 | 3,719 | +7 |
| 14 Aug 2026, 11:28 | 3,712 | -1 |
| 11 Aug 2026, 00:12 | 3,713 | -2 |
| 8 Aug 2026, 01:36 | 3,715 | +5 |
| 7 Aug 2026, 12:18 | 3,710 | first reading |
20 posts held, back to 4 July 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 2 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 4 August 2026. An engagement rate over an empty window would be a number about nothing.
35 reactions across 15 posts, in 2 distinct kinds. The most used accounts for 80.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 28 | 80.0% | |
| 👍 | 7 | 20.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 17 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 35 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 4 July 2026 to 4 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
【UU安全小课堂｜给U卡上好“双保险”⚠️】 安全用卡，不只是在发现异常后处理，更要学会主动防护。 暂时不用U卡时，可以在UU App内主动冻结；需要使用时再随时解冻。 实体卡和虚拟卡均支持，冻结、解冻不限次数。 同时，还可以分别设置交易限额和ATM取现限额，支持单笔、每日、每月额度管理。 日常消费把额度设到“够用”，临时大额消费或取现时再按需调整，用完及时恢复。 ⚠️操作路径：UU App → 卡片 → 冻结卡片 / 限额设置 如发现可疑交易，请立即冻结卡片，并通过官方渠道核实。 ☀️记住：卡信息不外泄，是最重要的安全防线；主动锁卡、合理限额，是额外的安全保障。
❤4
🌍 跨境生活攻略｜境外ATM取现，费用可能来自三个地方 在海外ATM取现时，屏幕显示的手续费不一定是全部成本。一笔取现通常可能涉及： 1️⃣ ATM运营方手续费由当地ATM运营机构收取，通常会在确认取现前显示。 2️⃣ 发卡机构境外取现费由银行卡或账户所属机构收取，可能不会显示在ATM页面上。 3️⃣ 汇率转换费用如果ATM询问使用人民币还是当地货币结算，选择人民币可能触发动态货币转换，由ATM服务商提供汇率并加入额外费用。 操作前建议注意： ▪️ 查看ATM是否明确显示手续费▪️ 同时比较人民币金额、当地货币金额和转换汇率▪️ 不清楚转换成本时，可以拒绝ATM提供的货币转换▪️ 提前查询自己的银行卡是否收取境外取现费▪️ 尽量减少多次、小额取现带来的重复手续费 选择“当地货币结算”并不代表一定没有费用，发卡机构仍可能收取境外取现或货币转换费用，最终以银行卡规则为准。
👍2
⚠️ UU Wallet 安全提醒：谨防假冒官方客服及诈骗频道 ⚠️ 近期发现有不法分子冒充 UU Wallet 官方客服，通过相似头像、相似名称或假冒机器人账号主动联系用户，诱导用户转账、提供验证码或泄露账户信息。 请所有用户务必提高警惕。 一、请认准 UU Wallet 官方渠道 ✅ 官方 Telegram 客服：@UUWalletSupport_bot ✅ 官方 Telegram 中文频道：@uuwallet_fx_cn ❌目前发现的假冒账号示例：@UYH00_bot 该账号并非 UU Wallet 官方客服，请勿联系、请勿转账、请勿提供任何账户信息。 二、如何找到正确的官方客服 请只通过以下两种方式进入官方客服： 进入官方频道 @uuwallet_fx_cn，点击频道内的 “官方客服” 按钮； 打开 UU Wallet App 首页，点击右上角 客服图标，跳转至官方客服。 ⚠️ ❌请勿在 Telegram 内直接…
❤3
🌍 跨境生活攻略｜酒店押金一直没退，是不是被重复扣款了？ 💳 📌 海外酒店办理入住时，通常会要求刷卡支付押金。退房后发现账单里同时出现“押金”和“房费”，不一定代表酒店重复收费。 💡 酒店押金通常采用预授权：酒店先冻结一部分额度，用于覆盖房费、延迟退房或房间内消费。它会占用信用卡额度；如果使用借记卡，也可能暂时影响账户可用余额。 遇到这种情况，可以先做三步： 1️⃣ 查看交易状态 👀 “处理中”通常表示资金仍在冻结；“已入账”才代表正式扣款。 2️⃣ 保留退房凭证 🧾 保存最终账单、押金单和取消凭证，确认酒店是否已经提交预授权撤销。 3️⃣ 分别联系酒店和发卡机构 ☎️ 先让酒店确认撤销时间和金额；如果长时间没有释放，再向发卡机构提供交易日期、金额和酒店名称查询。 ✈️⚠️出行提示： 入住酒店或租车时，尽量预留额外额度。💳 退房结账如果更换支付方式，也要确认原卡上的预授权已经撤销。 ✅
❤2
尊敬的 👍UU Wallet 用户： 感谢大家一直以来对 UU 官方汇率频道 的关注与支持。 由于近期国际汇款业务调整升级，国际汇款服务暂时暂停，恢复时间待官方进一步确认。 因此，本频道将暂时停止每日汇率更新。 ⬅️⬅️请大家放心，本频道持续运营中🫶🫶🫶 后续仍将持续发布： ➖ 官方公告 ➖ 产品更新 ➖ 系统维护通知 ➖ 最新业务动态 近期如有兑换需求可联系 合作商家「U益汇」 办理兑换业务⬅️ 【U益汇】🛫飞机号：@UYH00 咨询交易⬅️ 合作商家营业时间： 10:00AM~01:00AM 🚀 温馨提示 国际汇款业务恢复后，我们将第一时间发布公告，并同步恢复每日汇率更新。感谢大家一直以来的理解、支持与信任！ 💰💰💰💰💰💰💰💰 🪙🪙🪙🪙🪙🪙🪙🪙 👍UU Wallet 团队
❤6👍4
UU 速汇 官方汇率 —UU国际汇款，由持牌银行和合规机构承汇 🕯 UU Wallet 匯率更新 🕯 🔘2026.7.17 👑客 户 ➡️ UU Wallet👍 🫶🫶🫶🫶🫶🫶🫶🫶🫶🫶 💵 USDT➡️🇨🇳 人民币 ✖️ 转账 6.71 💵 USDT➡️👌 Gcash ✖️ 转账 61.15 💵 USDT➡️🇭🇰 港币 ✖️ 转账 7.77 💵 USDT➡️🇹🇭 泰铢 ✖️ 转账 33.33 💵 USDT➡️🇲🇾 马币 ✖️ 转账 4.02 💵 USDT➡️🇻🇳 越南盾 ✖️ 转账 26089 🔒🔒🔒🔒🔒🔒🔒 ⭐实时参考银行牌价 ⭐合规清算体系 ⭐快速到账，全天候支持 ⬅️黑U检测-点击立查⬅️ 📱 UU官方客服 📱 UU官方客服 ⭐ UU官方频道 👍 UU官方账号验证
❤2
UU 速汇 官方汇率 —UU国际汇款，由持牌银行和合规机构承汇 🕯 UU Wallet 匯率更新 🕯 🔘2026.7.16 👑客 户 ➡️ UU Wallet👍 🫶🫶🫶🫶🫶🫶🫶🫶🫶🫶 💵 USDT➡️🇨🇳 人民币 ✖️ 转账 6.7 💵 USDT➡️👌 Gcash ✖️ 转账 61.2 💵 USDT➡️🇭🇰 港币 ✖️ 转账 7.76 💵 USDT➡️🇹🇭 泰铢 ✖️ 转账 33.35 💵 USDT➡️🇲🇾 马币 ✖️ 转账 4.02 💵 USDT➡️🇻🇳 越南盾 ✖️ 转账 26083 🔒🔒🔒🔒🔒🔒🔒 ⭐实时参考银行牌价 ⭐合规清算体系 ⭐快速到账，全天候支持 ⬅️黑U检测-点击立查⬅️ 📱 UU官方客服 📱 UU官方客服 ⭐ UU官方频道 👍 UU官方账号验证
❤1
UU 速汇 官方汇率 —UU国际汇款，由持牌银行和合规机构承汇 🕯 UU Wallet 匯率更新 🕯 🔘2026.7.15 👑客 户 ➡️ UU Wallet👍 🫶🫶🫶🫶🫶🫶🫶🫶🫶🫶 💵 USDT➡️🇨🇳 人民币 ✖️ 转账 6.7 💵 USDT➡️👌 Gcash ✖️ 转账 61.2 💵 USDT➡️🇭🇰 港币 ✖️ 转账 7.76 💵 USDT➡️🇹🇭 泰铢 ✖️ 转账 33.21 💵 USDT➡️🇲🇾 马币 ✖️ 转账 4.01 💵 USDT➡️🇻🇳 越南盾 ✖️ 转账 26088 🔒🔒🔒🔒🔒🔒🔒 ⭐实时参考银行牌价 ⭐合规清算体系 ⭐快速到账，全天候支持 ⬅️黑U检测-点击立查⬅️ 📱 UU官方客服 📱 UU官方客服 ⭐ UU官方频道 👍 UU官方账号验证
❤1
UU 速汇 官方汇率 —UU国际汇款，由持牌银行和合规机构承汇 🕯 UU Wallet 匯率更新 🕯 🔘2026.7.14 👑客 户 ➡️ UU Wallet👍 🫶🫶🫶🫶🫶🫶🫶🫶🫶🫶 💵 USDT➡️🇨🇳 人民币 ✖️ 转账 6.71 💵 USDT➡️👌 Gcash ✖️ 转账 61.2 💵 USDT➡️🇭🇰 港币 ✖️ 转账 7.76 💵 USDT➡️🇹🇭 泰铢 ✖️ 转账 33.24 💵 USDT➡️🇲🇾 马币 ✖️ 转账 4.02 💵 USDT➡️🇻🇳 越南盾 ✖️ 转账 26079 🔒🔒🔒🔒🔒🔒🔒 ⭐实时参考银行牌价 ⭐合规清算体系 ⭐快速到账，全天候支持 ⬅️黑U检测-点击立查⬅️ 📱 UU官方客服 📱 UU官方客服 ⭐ UU官方频道 👍 UU官方账号验证
UU 速汇 官方汇率 —UU国际汇款，由持牌银行和合规机构承汇 🕯 UU Wallet 匯率更新 🕯 🔘2026.7.13 👑客 户 ➡️ UU Wallet👍 🫶🫶🫶🫶🫶🫶🫶🫶🫶🫶 💵 USDT➡️🇨🇳 人民币 ✖️ 转账 6.71 💵 USDT➡️👌 Gcash ✖️ 转账 61.15 💵 USDT➡️🇭🇰 港币 ✖️ 转账 7.76 💵 USDT➡️🇹🇭 泰铢 ✖️ 转账 33.11 💵 USDT➡️🇲🇾 马币 ✖️ 转账 4.02 💵 USDT➡️🇻🇳 越南盾 ✖️ 转账 26119 🔒🔒🔒🔒🔒🔒🔒 ⭐实时参考银行牌价 ⭐合规清算体系 ⭐快速到账，全天候支持 ⬅️黑U检测-点击立查⬅️ 📱 UU官方客服 📱 UU官方客服 ⭐ UU官方频道 👍 UU官方账号验证
❤1
UU 速汇 官方汇率 —UU国际汇款，由持牌银行和合规机构承汇 🕯 UU Wallet 匯率更新 🕯 🔘2026.7.12 👑客 户 ➡️ UU Wallet👍 🫶🫶🫶🫶🫶🫶🫶🫶🫶🫶 💵 USDT➡️🇨🇳 人民币 ✖️ 转账 6.71 💵 USDT➡️👌 Gcash ✖️ 转账 61.1 💵 USDT➡️🇭🇰 港币 ✖️ 转账 7.76 💵 USDT➡️🇹🇭 泰铢 ✖️ 转账 33.01 💵 USDT➡️🇲🇾 马币 ✖️ 转账 4.01 💵 USDT➡️🇻🇳 越南盾 ✖️ 转账 26090 🔒🔒🔒🔒🔒🔒🔒 ⭐实时参考银行牌价 ⭐合规清算体系 ⭐快速到账，全天候支持 ⬅️黑U检测-点击立查⬅️ 📱 UU官方客服 📱 UU官方客服 ⭐ UU官方频道 👍 UU官方账号验证
UU 速汇 官方汇率 —UU国际汇款，由持牌银行和合规机构承汇 🕯 UU Wallet 匯率更新 🕯 🔘2026.7.11 👑客 户 ➡️ UU Wallet👍 🫶🫶🫶🫶🫶🫶🫶🫶🫶🫶 💵 USDT➡️🇨🇳 人民币 ✖️ 转账 6.71 💵 USDT➡️👌 Gcash ✖️ 转账 61.1 💵 USDT➡️🇭🇰 港币 ✖️ 转账 7.76 💵 USDT➡️🇹🇭 泰铢 ✖️ 转账 33.01 💵 USDT➡️🇲🇾 马币 ✖️ 转账 4.01 💵 USDT➡️🇻🇳 越南盾 ✖️ 转账 26090 🔒🔒🔒🔒🔒🔒🔒 ⭐实时参考银行牌价 ⭐合规清算体系 ⭐快速到账，全天候支持 ⬅️黑U检测-点击立查⬅️ 📱 UU官方客服 📱 UU官方客服 ⭐ UU官方频道 👍 UU官方账号验证
❤3
Showing the 12 most recent of 20 posts we hold for @uuwallet_fx_cn. 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 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“官方汇率频道【UU Wallet】” (@uuwallet_fx_cn), 3,801 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/uuwallet_fx_cn.
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.