Telegram RegisterThe public register of Telegram
Telegram profile photo for uzpay官方频道

Channel

uzpay官方频道

@uzpay88

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

51subscribers

-4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002259385932
TypeChannel
Username@uzpay88
CreatedBetween 1 October 2024 and 21 November 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live17 November 2026
Measurements held6
Confirmed unchanged2 times, most recently 17 November 2026
On Telegramt.me/uzpay88

Topic

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 29 September 2026 and assigned it the closest of 31 fixed categories, at 76% 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.

Growth

5155537 August 2026 — 55 subscribers10 August 2026 — 55 subscribers7 September 2026 — 54 subscribers9 October 2026 — 53 subscribers30 October 2026 — 52 subscribers8 November 2026 — 51 subscribers7 August 20268 November 2026
6 measurements spanning 92 days, net -4. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 50–56 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Nov 2026, 00:0951-1
30 Oct 2026, 23:4052-1
9 Oct 2026, 08:3853-1
7 Sept 2026, 13:5654-1
10 Aug 2026, 08:3055no change
7 Aug 2026, 14:2055first reading

Engagement

17 posts held, back to 21 November 2024 — 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 17 posts for this entry, the most recent from 8 April 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

8 reactions across 2 posts, in 6 distinct kinds. The most used accounts for 37.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤337.5%
❤‍🔥112.5%
💋112.5%
💯112.5%
😍112.5%
🥰112.5%

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 2 of the 17 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 8 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 21 November 2024 to 8 April 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

8 Apr 2025, 10:09 UTC124 viewsread 10 August 2026

加拿大🇨🇦直通车进算 高速通车!🤘 加拿大🇨🇦直通车进算 高速通车!🤘 加拿大🇨🇦直通车进算 高速通车!🤘 单笔范围: 🔥 单笔1000—20万加币(大额另行通知) 可承接模式: 🚀 精聊、大区 🚀 快杀、盗刷、公检法 (特殊料性提前报备) 我司优势: 💡全行业类型(具体协商) 💡各银行账户充裕,提供一对一同行转账,资金更快到账更安全! 💡价格冰点,一手车队,效率回款 结算方式: 🏆 拖出结算USDT,最快落账当天就可以结算。

Signed UZpay 橙子

22 Mar 2025, 08:51 UTC142 viewsread 10 August 2026

🇪🇸西班牙-欧元🇪🇸交易所账户 🇬🇧英国-欧元户🇬🇧交易所账户 ✅到账就算,效率回款✅ ✅一手资源,量大可谈✅ 🇪🇸西班牙欧元,单笔3000-10w欧元 🇬🇧英国欧元户,单笔3000-2.5w欧元 ————————————————— ❗️入金请尽力提供清晰手持证件照 ❗️如不方便引导务必提供高清的证件照片! 有需要请随时滴滴联系,群内24小时专业客服为您解答! ————————————————— 专业的事,交给专业的人 为贵司打造安全稳定的支付通道✅ ㊗️各位老板天天开大单,财源广进

Signed UZpay 橙子

28 Jan 2025, 03:25 UTC173 viewsread 10 August 2026
Photo

“金蛇迎春贺新岁,UZPay与您共创辉煌!” 贺词正文 尊敬的客户: 值此新春佳节到来之际,UZPay全体员工向您及家人致以最诚挚的节日问候和美好的祝福! 2025年是充满机遇与希望的一年,感谢您一直以来的支持与信任。展望未来,UZPay将继续以优质的服务与创新的解决方案,为您的每一次交易带来更多便利和价值。 愿您在新的一年里: 财运亨通,好运连连! 事业蒸蒸日上! 阖家幸福安康! 我们期待在2025年与您携手并进,共同书写新的篇章!新春快乐! UZPay团队敬上

Signed UZpay 橙子

17 Jan 2025, 11:26 UTC162 viewsread 10 August 2026

🇮🇳 印度全类 进算 拖算 产品🇮🇳 😄😃😄😃😄 😎 优势在我:价格实惠 / 入金丝滑 / 可靠安全 😀 😎 上课时间:12:00 - 24:00 北京时间 😃 😎 可承接盘口类型:精聊 / 刷单 / 公检法 / 电诈 / 盗刷 / 三黑 😃 😎 印度 UPI钱包 无视料子 一手价格 欢迎质询 😃 😎 印度 大区 三类 承兑 一手价格 欢迎质询😀 😎 单笔金额:1000 ~ 1000万印度卢比起入! 😀 😎 结算方式:USDT 😃 🤑 懂行的来 想玩的也来!稳定通车! ⏺ 大量收量,有量老板欢迎来骚扰以下飞机号哟😂 商务合作1:@uzdalaoge1 商务合作2:@chuangzhang213 商务合作3:@uz0794 商务合作4:@uz369888 商务合作5:@pay9980 商务合作6:@UZYYZZZ 商务合作7:@UZLDLD 商务合作8:@pay6989 商务合作9…

Signed UZpay 橙子

11 Jan 2025, 09:55 UTC139 viewsread 10 August 2026

🇺🇸🇺🇸🇺🇸美国本土公户🇺🇸🇺🇸🇺🇸 ⚽单笔1000起接, 额度充足!! ⚽提供专户专用!量大从优! ⚽账户使用周期短.更新账户快! ⚽本土银行账户多.稳!稳!稳! ⚽支持美金精聊代收,满足客户 ————————————————— 🇪🇺🇪🇺🇪🇺欧元直通车🇪🇺🇪🇺🇪🇺 ⚽单笔1000起接, 额度充足!! ⚽支持多国欧盟国家欧元账户! ⚽支持维护15天以上精聊客户! ————————————————— 🇻🇳🇻🇳🇻🇳越南国际户🇻🇳🇻🇳🇻🇳 ⚽多元化多币种账户提供选择!! ⚽美金/欧元/英镑/加币/澳币/法郎 ⚽到账快,到账当天即可结算!! ⚽相比本土户价格更实惠, 更划算! ⚽风控小,成功率高,大额无忧!! ————————————————— 🇭🇰🇭🇰🇭🇰香港国际户🇭🇰🇭🇰🇭🇰 ⚽香港国际户可承接日本,韩国资金! ⚽当地币种转出.选择美金落账即可! ⚽无论币种1000美金等值起接!! ⚽公户私户 不限料、拖出即算!! ————————…

Signed UZpay 橙子

6 Jan 2025, 16:50 UTC157 viewsread 10 August 2026
Photo

用户名:Uzpay-胖虎 UZpay-阿星 骗子id:@uzpaypanghu @pay2380 此骗子在模仿我们的头像,名字,搞了一个新币的假公群去到处骗人,败坏我们名声的同时,也使很多人上当受骗。 合作请认准 UZpay 唯一公群 新币i小组1353 24小时客服,让您随时感受5星级服务 联系我们: 商务合作1:@uzdalaoge1 商务合作2:@chuanzhang121 商务合作3:@uz0794 商务合作4:@uz369888 商务合作5:@pay9980 商务合作6:@UZYYZZZ 商务合作7:@UZLDLD 商务合作8:@pay8689 商务合作9:@UZpay1688 让UZpay为您出海掘金之路保驾护航!

Signed UZpay 橙子

5 Jan 2025, 22:56 UTC120 viewsread 10 August 2026

黎巴嫩 已通车 价格冰点全网最低价 卡多 承兑稳 有需要的联系商务

Signed UZ-pay 灵儿

31 Dec 2024, 16:17 UTC142 viewsread 10 August 2026
Photo

🎉✨各位商户祝您新年快乐!🎉✨ 随着一年的最后几天悄然溜走,这是一个停下来反思我们所走过的旅程的好时机。🫐每一个时刻,无论是充满欢乐还是充满挑战,都将自己的线索编织进了我们的生活,造就了今天的我们。 2024即将已过!愿你2025年 步步高升,事业蒸蒸日上,家庭和和美美,健康安康,快乐常伴! 愿在新的一年✨所求皆如愿,所行化坦途 乘风破浪,一往无前 让我们满怀希望,胸怀开阔,迎接新的可能性,迈入 2025 年。愿新的一年为您带来无限机遇、无尽幸福和追逐梦想的勇气。🌈✨ 祝愿新的冒险、新的开始和无数珍贵的回忆。让我们让 2025 年成为值得纪念的一年!🥂 🔥🔥UZpay全体 祝您和您的亲人新年快乐!🎆🥳

Signed UZpay 橙子

6 Dec 2024, 11:57 UTC354 viewsread 10 August 2026
Photo

UzPay——老牌源头支付通道!多元支付方式,开启便捷支付之门,让交易快人一步! 主营国家:🇮🇳印度 🇧🇷 巴西 🇲🇽墨西哥 🇿🇦南非 🇨🇴哥伦比亚 🇧🇩孟加拉 🇹🇷 土耳其 线上api 线下卡接 🇦🇪阿联酋 🇮🇹意大利 🇳🇵尼泊尔 🇲🇿莫桑比克 🇹🇭泰国 🇻🇳越南 🇲🇾马来西亚 优势: 公群担保,保障资金安全 24小时客服,让您随时感受5星级服务 联系我们: 商务合作1:@uzdalaoge1 商务合作2:@chuanzhang121 商务合作3:@uz0794 商务合作4:@uz369888 商务合作5:@pay9980 商务合作6:@UZYYZZZ 商务合作7:@UZLDLD 商务合作8:@pay6869 商务合作9:@UZpay1688 让UzPay为您出海掘金之路保驾护航!

Signed UZ-pay 老哥

4 Dec 2024, 11:27 UTC248 viewsread 10 August 2026

😀海外直营通道😆诚信运营😆高效团队😆闪电回😆 😀专业稳定靠谱😏 🇮🇳 印度直通车 🇵🇭 菲律宾直通车 🇸🇬 新币直通车 🇰🇪 肯尼亚直通车 🇻🇳 越南直通车 🇷🇺 俄罗斯直通车 🇲🇨 印尼直通车 🇹🇷 土耳其直通车 🇲🇾 马来直通车 🇲🇦 摩洛哥直通车 🇹🇭 泰国直通车 🇪🇸 西班牙直通车 🇭🇰 香港直通车 🇮🇹 意大利直通车 🇯🇵 日本直通车 🇲🇽 墨西哥直通车 🇸🇦 沙特直通车 🇵🇹 葡萄牙直通车 🇿🇦 南非直通车 🇦🇷 阿根廷直通车 🇪🇬 埃及直通车 🇦🇪 阿联酋直通车 🇯🇴 约旦直通车 🇹🇳 突尼斯直通车 🇴🇲 阿曼直通车 🇵🇰 巴基斯坦直通车 🇧🇷 巴西直通车…

Signed UZpay 橙子

1 Dec 2024, 06:06 UTC217 viewsread 10 August 2026

😀😀😀UZpay国际全球支付😀😀😀 😀😀😀😀😀😀😀😀😀😀 源头支付通道 欢迎各位盘总来骚扰 📱📱📱承接各国的量📱📱📱 📱📱📱📱📱📱 📱📱📱📱📱📱 📊🇮🇳印度支付 📊🇵🇭菲律宾支付 📊🇲🇲缅甸支付 📊🇮🇩印尼支付 📊🇧🇩孟加拉支付 📊🇪🇬埃及支付 📊🇧🇷巴西支付 📊🇲🇽墨西哥支付 📊🇺🇸美国支付 📊🇰🇷韩国支付 📊🇹🇷土耳其支付 📊🇿🇦南非支付 📊🇳🇬尼日利亚 📊🇸🇦沙特阿拉伯 📊🇨🇴哥伦比亚 📊🇲🇾马来西亚 📊 🇳🇬尼日利亚 📊🇯🇵日本支付 📊🇹🇭泰国支付 📊 🇵🇭菲律宾 📊🇻🇳越南支付 以上所有通道正常上课中,欢迎各位老板入金 😀飞机一响 黄金万两 😀今日用支付,明日当首富 😀大额入款解决方案 😀完善代收付 一站式服务

Signed UZpay 橙子

30 Nov 2024, 08:48 UTC226 viewsread 10 August 2026

🔥~全球源头支付通道🔥 印度🇮🇳纯原生 线上丝滑📱 线下接所有料🚨🚨 🇧🇷 巴西 🇲🇽墨西哥 🇿🇦南非 🇨🇴哥伦比亚 🇧🇩孟加拉 🇹🇷 土耳其 ➡️➡️线上api 线下卡接⬅️⬅️ 🇦🇪阿联酋 🇮🇹意大利 🇳🇵尼泊尔 🇲🇿莫桑比克 🇹🇭泰掴 🇻🇳越南 🇲🇾马来西亚 🌈🌈卡接价格冰点📱📱收付一体 ⚠️⚠️⚠️欢迎询价👀👀 ❕❕点位挑战全网最低❕❕ 所有国家😄😄小时🔤🔤 回 😄 海外支付认准 🚩🚩🚩🚩🚩 ☺️☺️☺️☺️☺️☺️ ☺️☺️☺️☺️☺️☺️☺️☺️ ✈️📱📱:@pay9980 @UZLDLD @UZpay1688 @pay6869 @uzdalaoge1 @UZYYZZZ @uz14725 @uz0794

Signed UZpay 橙子

Showing the 12 most recent of 17 posts we hold for @uzpay88. 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

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.

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 8 November 2026 — this entry's latest reading, not the date you are reading this.

“uzpay官方频道” (@uzpay88), 51 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/uzpay88.

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.