Telegram RegisterThe public register of Telegram
Telegram profile photo for UAB内部官方频道

Channel

UAB内部官方频道

@NEXUS6677

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

6,167subscribers

-4,180 since we began measuring on 16 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1003886955708
TypeChannel
Username@NEXUS6677
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded16 August 2026
Last confirmed live31 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 31 August 2026
On Telegramt.me/NEXUS6677

Growth

6,16710,3478,25716 August 2026 — 10,347 subscribers17 August 2026 — 10,335 subscribers18 August 2026 — 10,312 subscribers19 August 2026 — 6,353 subscribers22 August 2026 — 6,302 subscribers25 August 2026 — 6,257 subscribers28 August 2026 — 6,215 subscribers31 August 2026 — 6,167 subscribers16 August 202631 August 2026
8 measurements spanning 15 days, net -4,180. 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 5,540–10,974 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 05:056,167-48
28 Aug 2026, 15:326,215-42
25 Aug 2026, 17:486,257-45
22 Aug 2026, 20:136,302-51
19 Aug 2026, 08:436,353-3,959
18 Aug 2026, 09:0310,312-23
17 Aug 2026, 12:2310,335-12
16 Aug 2026, 16:4510,347first reading

Engagement

13 posts held, back to 16 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.57%
avg views ÷ 6,167 subscribers
Avg views / post
96.5
13 posts measured
Reaction rate
0.847%
reactions ÷ views · ER floor
Posts in window
13
of 13 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. It is computed over the 1 of 13 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 18 August 2026
Posts held13 (16 August 202618 August 2026)
Views total1,255
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Aug 2026, 13:52 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

Video runtime
1m 17s
Average length
26s

Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1100.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 1 of the 13 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 16 August 2026 to 18 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

18 Aug 2026, 05:09 UTC39 viewsread 18 August 2026
Forwarded from @sky167899Photo

❗️❗️❗️❗️❗️❤️三角洲行动 【ETO】追踪版本 8月18日反馈 😙已更新新版本 解决了协议问题 无视游戏更新 ⚠️限时出售周卡⚡️⚡️⚡️ 😀➡️月卡⚡️⚡️⚡️⚡️ ⚡️ 适配新赛季 无视赛季加密 ⚡️工作室专用 护航专用 内部项目 👉ETO内部 支持 双版本 👉APK版本/定制BOOT版本 自行选择 👉全天开放交流群 欢迎进来看看 全网顶级售后服务‼️ 👉不敢开交流群的都是垃圾项目‼️ 🔈支持骁龙/天机处理器 5-6系内核版本 ⭐APK版本 傻瓜式操作 给root权限就行 ⚡️子追漏打+顶级绘制+完美物资 ⚡️距离显示 射线 下发提示 ⚡️头甲 基础绘制 盒子显示 防录屏 ⚡️提卡后联系客服进入内部群 👉限时额外服务:包刷机+环境一条龙 双向客服:😃😃😃😃@UU8800Bot 🥰🛒官方认证 免手续费卡网 点我➡️https://ufo.fakalon.cn/links/EE82D74

17 Aug 2026, 11:22 UTC55 viewsread 18 August 2026
Forwarded from @sky167899Photo

❗️❗️❗️❗️❗️❤️三角洲行动 【ETO】追踪版本 8月16日反馈 😙已更新新版本 解决了协议问题 无视游戏更新 ⚠️限时出售周卡⚡️⚡️⚡️ 😀➡️月卡⚡️⚡️⚡️⚡️ ⚡️ 适配新赛季 无视赛季加密 ⚡️工作室专用 护航专用 内部项目 👉ETO内部 支持 双版本 👉APK版本/定制BOOT版本 自行选择 👉全天开放交流群 欢迎进来看看 全网顶级售后服务‼️ 👉不敢开交流群的都是垃圾项目‼️ 🔈支持骁龙/天机处理器 5-6系内核版本 ⭐APK版本 傻瓜式操作 给root权限就行 ⚡️子追漏打+顶级绘制+完美物资 ⚡️距离显示 射线 下发提示 ⚡️头甲 基础绘制 盒子显示 防录屏 ⚡️提卡后联系客服进入内部群 👉限时额外服务:包刷机+环境一条龙 双向客服:😃😃😃😃@UU8800Bot 🥰🛒官方认证 免手续费卡网 点我➡️https://ufo.fakalon.cn/links/EE82D74

16 Aug 2026, 09:24 UTC118 views1 reactionsread 18 August 2026
Forwarded from @xxmnbnbnbPhoto

❤️ 三角洲落雪❄️范围 8月16日反馈 已更新 👉裸奔范围 无绘制 可以搭配单透使用😎 ⚡️更新最新写法 ⚡️完全不会网络波动封 ⚡️更换全新思路 ⚡️更新新功能 无限屏息、聚点 ⚡️拒绝频繁禁令 1.3.7 ⚡️从3月出现到现在无客户反馈封3650禁令🤘 🔗下载地址 https://1824582406.share.123pan.cn/123pan/n47Xjv-6YiDA?pwd=o2y6# 😃😃😃😃@UU8800Bot 🥰🛒官方认证 免手续费卡网 点我➡️https://ufo.fakalon.cn/links/EE82D74A ❤️卡网进不去的复制到浏览器进 ❗️❗️➡️点击进入官方频道 ❗️❗️➡️点击进入官方聊天群

👍1

16 Aug 2026, 05:11 UTC375 viewsread 16 August 2026
Photo

❗️❗️❗️❗️上架❤️三角洲行动 【UAB内部】 界面展示如下 纯算法解密不会十年!护航首选😀 👉全天开放交流群 欢迎进来看看 全网顶级售后服务‼️ 👉陀螺仪自瞄+顶级绘制+完美物资 👉开卡价格⚡️⚡️⚡️续费⚡️⚡️⚡️ 低价卡切勿上当受骗 严格控价 🔸支持骁龙/天机处理器 5.1-6.6和6.12内核版本 ‼️ 😄陀螺仪自瞄+顶级绘制+完美物资 😃距离显示 射线 下发提示 😄头甲 基础绘制 盒子显示 🔘首发纯算法写法,和谐只会遁地,不会出现封号问题!! 🔘绝对真实的纯算法,梓喵也不会动任何内存!! 🔘控人数防泛滥,禁止宣传一对一开卡!! 😙开卡福利 包刷机一条龙服务 ➡️可包刷机环境服务一次 免费赠送 ➡️需要自备电脑和数据线 双向客服:😃😃😃😃@UU8800Bot 🥰🛒官方认证 免手续费卡网 点我➡️https://ufo.fakalon.cn/links/EE82D74A ❤️卡网进不去的复

Showing the 12 most recent of 13 posts we hold for @NEXUS6677. 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 — 691,538 of 1,629,497 entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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.

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

“UAB内部官方频道” (@NEXUS6677), 6,167 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/NEXUS6677.

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.