The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 18 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

Channel
HuangYu M5数据团队
@upm5_55688
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
51subscribers
+0 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 | -1001933023256 |
|---|---|
| Type | Channel |
| Username | @upm5_55688 |
| Description | 滲透團隊,實力技術歡迎來合作。 |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/upm5_55688 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 10:46 | 51 | no change |
| 7 Aug 2026, 10:28 | 51 | first reading |
Engagement
20 posts held, back to 16 July 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 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- —
- no view readings in window
- Avg views / post
- —
- no view readings
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1
- of 20 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 1 August 2026 |
|---|---|
| Posts held | 20 (16 July 2024 – 1 August 2026) |
| Views total | — |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 10:46 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Photos
- 214
- Videos
- 49
- Links
- 228
Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 50.0% | |
| 👍 | 1 | 50.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 2 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 2reactions 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 16 July 2024 to 1 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.
Recent posts
🤓皇裕通知:番丽网♥️ 📣类型:购物 📣筛选条件:无 📣总数量:不祥 📣数据格式:英文名/中文名/电话/地址 📣适用:电销公检/精聊/快杀/刷单 📣站点连结:暂不公布 📣起单量:500 ---------------------- 🌟公司验证:无 本公司出售产品均可在验证系统上查询 ❌如查无均不为本公司出产之产品❌ ---------------------- ☎️谘询业务合作专员: @Huangyu1788_do02 @Huangyu1788_AP @Huangyu1788_B @Huangyu1788_C @Huangyu1788_D ••••••••••••••••••••••••••••••••••• ✅落地頁項目: [提供落地页引流支援·可提供二筛/表筛/精筛/粉类] ••••••••••••••••••••••••••••••••••• ✅验证部: [周边服务·国内三要素验证·撞库批配字段·全球软件过筛] 🤩Mobi…
👍1
🤓皇裕通知:广东不动产♥️ 📣类型:不动产 📣筛选条件:筛IOS全国出 📣总数量: 单一中国广东地区 📣数据格式:姓名/手机号/证件号/地址 📣适用:电销公检/精聊/快杀/刷单 📣站点连结:暂不公布 📣起单量:1000 ---------------------- 🌟公司验证:无 本公司出售产品均可在验证系统上查询 ❌如查无均不为本公司出产之产品❌ ---------------------- ☎️谘询业务合作专员: @Huangyu1788_do02 @Huangyu1788_AP @Huangyu1788_B @Huangyu1788_C @Huangyu1788_D ••••••••••••••••••••••••••••••••••• ✅落地頁項目: [提供落地页引流支援·可提供二筛/表筛/精筛/粉类] ••••••••••••••••••••••••••••••••••• ✅验证部: [周边服务·国内三要素验证·撞库批…
🤓皇裕通知:鲲鹏保险♥️ 📣类型:保险 📣筛选条件:筛地区到省/性别/年纪/筛IOS全国 📣总数量: 单一中国地区 📣数据格式:电话/支付方式/姓名/证件号/性别/生日/申请日期 📣适用:电销公检/精聊/快杀/刷单 📣站点连结:暂不公布 📣起单量:1000 ---------------------- 🌟公司验证:无 本公司出售产品均可在验证系统上查询 ❌如查无均不为本公司出产之产品❌ ---------------------- ☎️谘询业务合作专员: @Huangyu1788_do02 @Huangyu1788_AP @Huangyu1788_B @Huangyu1788_C @Huangyu1788_D ••••••••••••••••••••••••••••••••••• ✅落地頁項目: [提供落地页引流支援·可提供二筛/表筛/精筛/粉类] ••••••••••••••••••••••••••••••••••• ✅验证部…
🤓皇裕通知:在美泰侨♥️ 📣类型:侨民类型 📣筛选条件:筛选年纪+钱 📣总数量:不祥 📣数据格式:名字/地址/生日/手机号 📣适用:电销公检/精聊/快杀/刷单 📣站点连结:暂不公布 📣起单量:500 ---------------------- 🌟公司验证:无 本公司出售产品均可在验证系统上查询 ❌如查无均不为本公司出产之产品❌ ---------------------- ☎️谘询业务合作专员: @Huangyu1788_do02 @Huangyu1788_AP @Huangyu1788_B @Huangyu1788_C @Huangyu1788_D ••••••••••••••••••••••••••••••••••• ✅落地頁項目: [提供落地页引流支援·可提供二筛/表筛/精筛/粉类] ••••••••••••••••••••••••••••••••••• ✅验证部: [周边服务·国内三要素验证·撞库批配字段·全球软件过筛…
🤓皇裕通知:在美越侨♥️ 📣类型:侨民类型 📣筛选条件:筛选年纪+钱 📣总数量:不祥 📣数据格式:名字/街道/州/邮递区号/县/城市/生日/手机号 📣适用:电销公检/精聊/快杀/刷单 📣站点连结:暂不公布 📣起单量:500 ---------------------- 🌟公司验证:无 本公司出售产品均可在验证系统上查询 ❌如查无均不为本公司出产之产品❌ ---------------------- ☎️谘询业务合作专员: @Huangyu1788_do02 @Huangyu1788_AP @Huangyu1788_B @Huangyu1788_C @Huangyu1788_D ••••••••••••••••••••••••••••••••••• ✅落地頁項目: [提供落地页引流支援·可提供二筛/表筛/精筛/粉类] ••••••••••••••••••••••••••••••••••• ✅验证部: [周边服务·国内三要素验证·撞…
🤓皇裕通知:长荣学生带家长♥️ 📣类型:学生家长 📣筛选条件:无 📣总数量: 单一台湾地区/数量稀少 📣数据格式:家用电话/学生性别/代办人/家长/地区/学生姓名/代办人/电话/家长邮箱/电话/学生出生日期/代办日期/代辦人关系/邮递区号/居住地址/级别/学校名称 📣适用:电销/精聊/快杀/刷单 📣站点连结:暂不公布 📣起单量:500 ---------------------- 🌟公司验证:同业合作 本公司出售产品均可在验证系统上查询 ❌如查无均不为本公司出产之产品❌ ---------------------- ☎️谘询业务合作专员: @Huangyu1788_do02 @Huangyu1788_AP @Huangyu1788_B @Huangyu1788_C @Huangyu1788_D ••••••••••••••••••••••••••••••••••• ✅落地頁項目: [提供落地页引流支援·可提供二筛/表筛/精筛/粉…
🤓皇裕通知:南银法巴消金♥️ 📣类型:贷款 📣筛选条件:现提 📣总数量: 中国 📣数据格式:电话/市 📣适用:助贷 📣站点连结:暂不公布 📣起单量:500 ---------------------- 🌟公司验证:同业合作 本公司出售产品均可在验证系统上查询 ❌如查无均不为本公司出产之产品❌ ---------------------- ☎️谘询业务合作专员: @Huangyu1788_do02 @Huangyu1788_AP @Huangyu1788_B @Huangyu1788_C @Huangyu1788_D ••••••••••••••••••••••••••••••••••• ✅落地頁項目: [提供落地页引流支援·可提供二筛/表筛/精筛/粉类] ••••••••••••••••••••••••••••••••••• ✅验证部: [周边服务·国内三要素验证·撞库批配字段·全球软件过筛] 🤩Mobile Check🤩Lin…
👑专业数据集团👑 🤩全新全球各国华侨品项🤩 👑还在回购之前的品项那就错了,最新最夯的华侨品项来了👑 😀赶紧联系我们😀 ✨服务项目如下✨ 🔸电销数据国内/海外/全格式底料渗透数据库 🔸精聊盘数据: ①-可根据全格式底料数据库提取裸号过需要的软件 ②-也可以指定网站爬虫提取裸号过软件 🔸国内运营商网提数据,可针对指定app提取注册用户,安装用户棋牌/股民/六合/网贷/POS机/全行业提取 🔸可针对所需要的站点进行打站渗透,并且我方可提供双向验证 🔸海外落地页引流精准粉/表筛 精筛/手工粉 🔸全球软件过筛活跃/去空号/代筛服务 🔸国内数据库批配字段撞库,如地址.证件等 ---------------------- ☎️谘询业务合作专员: @Huangyu1788_do02 @Huangyu1788_AP @Huangyu1788_B @Huangyu1788_C @Huangyu1788_D •••••••••••••••••…
🤓皇裕通知:Eheya留学生租屋♥️ 📣类型:租屋类型 📣筛选条件:无 📣总数量:未知 📣数据格式:英文姓名/中文名/电话 📣适用:电销公检/精聊/快杀/刷单 📣站点连结:暂不公布 📣起单量:500 ---------------------- 🌟公司验证:同业合作 本公司出售产品均可在验证系统上查询 ❌如查无均不为本公司出产之产品❌ ---------------------- ☎️谘询业务合作专员: @Huangyu1788_do02 @Huangyu1788_AP @Huangyu1788_B @Huangyu1788_C @Huangyu1788_D ••••••••••••••••••••••••••••••••••• ✅落地頁項目: [提供落地页引流支援·可提供二筛/表筛/精筛/粉类] ••••••••••••••••••••••••••••••••••• ✅验证部: [周边服务·国内三要素验证·撞库批配字段·全球软…
🤓皇裕通知:美国华裔社区♥️ 📣类型:交友类型 📣筛选条件:无 📣总数量:1.2W+ 📣数据格式:使用者名称/密码/姓名/电话编号/移动电话/使用者ID/来源/使用者类型/禁止访问/发送邮件/gid/注册日期/上次访问日期/用户对话时间/用户对话页面/用户上次访问/用户注册日期/用户级别/用户发帖/用户时区/用户语言/用户新密码/是否商业号/注册IP/国家/使用者来源/用户等级 📣适用:电销/精聊/快杀/刷单 📣站点连结:暂不公布 📣起单量:500 ---------------------- 🌟公司验证:@hyg_guest_verify_bot 本公司出售产品均可在验证系统上查询 ❌如查无均不为本公司出产之产品❌ ---------------------- ☎️谘询业务合作专员: @Huangyu1788_do02 @Huangyu1788_AP @Huangyu1788_B @Huangyu1788_C @Huangyu…
🤓皇裕通知:YD华裔物流♥️ 📣类型:快递类型 📣筛选条件:无 📣总数量:1.7K 📣数据格式:会员名称/金额/单号/姓名/移动电话/邮政编码/尺寸/地址/订购电话/国家 📣适用:电销公检/精聊/快杀/刷单 📣站点连结:暂不公布 📣起单量:500 ---------------------- 🌟公司验证:@hyg_guest_verify_bot 本公司出售产品均可在验证系统上查询 ❌如查无均不为本公司出产之产品❌ ---------------------- ☎️谘询业务合作专员: @Huangyu1788_do02 @Huangyu1788_AP @Huangyu1788_B @Huangyu1788_C @Huangyu1788_D ••••••••••••••••••••••••••••••••••• ✅落地頁項目: [提供落地页引流支援·可提供二筛/表筛/精筛/粉类] •••••••••••••••••••••••••…
Showing the 12 most recent of 20 posts we hold for @upm5_55688. 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.
Citation-graph rank
Citation-graph rank — 1,197,474 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
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.
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.
Handles this channel named that no longer answer
- Dead references
- 4
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 4
- vacant every time we have ever looked
@upm5_55688 named 4 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 19 posts, 11 August 2026 – 11 August 2026
named in 19 posts, 11 August 2026 – 11 August 2026
named in 19 posts, 11 August 2026 – 11 August 2026
named in 19 posts, 11 August 2026 – 11 August 2026
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“HuangYu M5数据团队” (@upm5_55688), 51 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/upm5_55688.
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.