Telegram RegisterThe public register of Telegram

Channel

蜜雪冰城

@akad520

On this record: Growth · Engagement · Posts · Citations · Cite this entry

1,202subscribers

+46 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002933707376
TypeChannel
Username@akad520
CreatedBetween 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/akad520

Growth

1,1561,2021,1796 August 2026 — 1,156 subscribers6 August 2026 — 1,156 subscribers6 August 2026 — 1,176 subscribers10 August 2026 — 1,185 subscribers13 August 2026 — 1,202 subscribers6 August 202613 August 2026
5 measurements spanning 7 days, net +46. 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 1,149–1,209 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 00:341,202+17
10 Aug 2026, 04:201,185+9
6 Aug 2026, 19:411,176+20
6 Aug 2026, 09:051,156no change
6 Aug 2026, 04:081,156first reading

Engagement

11 posts held, back to 22 July 2026the 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
56.6%
avg views ÷ 1,202 subscribers
Avg views / post
680
10 posts measured
Reaction rate
0.158%
reactions ÷ views · ER floor
Posts in window
11
of 11 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 5 of 10 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 26 July 2026
Posts held11 (22 July 202626 July 2026)
Views total6,802
Reactions total6
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 09:05 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.

Recent posts

26 Jul 2026, 14:30 UTC≈905 views1 reactionsread 6 August 2026

📢 订阅链接更新通知 订阅链接已完成更新,请各位用户前往官网用户中心,重新获取并导入新的订阅链接。 ⚠️ 请注意: - 旧订阅链接已经无法获取最新节点; - 请删除旧订阅后,重新添加新的订阅链接; - 更新订阅后即可正常使用。 感谢大家的支持与理解!

26 Jul 2026, 12:26 UTC≈965 views2 reactionsread 6 August 2026

🎉 蜜雪冰城一周年庆活动开启! 感谢大家一直以来的支持与陪伴,蜜雪冰城迎来开业一周年庆典,现推出 7折优惠券活动! 🎁 活动内容: 全场优惠券 7折优惠 🎫 优惠券码: "蜜雪冰城一周年庆" ⏰ 有效期: 2026年07月26日 00:00 至 2026年08月02日 23:59 活动期间请及时使用优惠券,逾期失效。 感谢大家一路支持,未来我们将继续为大家提供更优质的服务与体验! ❤️

26 Jul 2026, 12:25 UTC≈287 viewsread 6 August 2026
File

#蜜雪冰城 #tuic #用户投稿 📊 主观评分 稳定 ★★★☆☆ 速度 ★★★☆☆ 延迟 ★★★★☆ 性价比 ★★★☆☆ (以上评分仅供参考) 😀机场自介: 无 😀 链接导航 开业:2026 官网:https://kad520.uk 频道:https://t.me/akad520 群组:无 😀主观点评 晚高峰测试,价格未知,整体速度还行 😀翻翻墙提醒您 任何机场都有跑路可能,建议仅月付,以降低风险。(本消息不针对任何机场)

25 Jul 2026, 14:55 UTC≈722 viewsread 6 August 2026

蜜雪冰城:https://kad520.uk 群组:https://t.me/akad521 频道:https://t.me/akad520

25 Jul 2026, 14:55 UTCviews —

蜜雪冰城 pinned «蜜雪冰城:https://kad520.uk 群组:https://t.me/akad521 频道:https://t.me/akad520»

25 Jul 2026, 13:28 UTC≈724 viewsread 6 August 2026

📢 节点协议升级通知 为进一步提升节点稳定性、兼容性以及整体使用体验,我们已完成节点协议升级。 本次调整内容: 🔄 TUIC 协议 → VLESS 协议 🔗 订阅链接已同步更新 请各位用户注意: ⚠️ 原 TUIC 节点配置将逐步停止使用,请前往网站用户中心重新获取最新订阅链接。 操作步骤: 1. 登录官网用户中心; 2. 复制最新订阅链接; 3. 删除客户端内旧订阅; 4. 重新导入新的订阅链接; 5. 更新订阅后即可使用最新 VLESS 节点。 本次升级不会影响: ✅ 套餐有效期 ✅ 剩余流量 ✅ 账户数据 如更新后无法连接,请尝试重启客户端或重新添加订阅。 感谢大家的理解与支持,我们会持续优化线路质量,为大家提供更加稳定、快速的网络体验。

25 Jul 2026, 11:08 UTC≈428 views1 reactionsread 6 August 2026
File

v0.8.94 https://github.com/chen08209/FlClash/releases/tag/v0.8.94 - Fix macos performance issue - Support custom global-ua - Update core - Optimize some details - Fix linux silent launching not working

24 Jul 2026, 17:00 UTC≈601 views0 reactionsread 6 August 2026

📢 节点协议升级完成通知 本次节点协议升级已完成,现已将原 VLESS 协议 全面更换为 TUIC 协议,同时已更新全新的订阅链接。 请各位用户注意: ⚠️ 旧订阅链接已无法获取最新节点,请务必前往官网用户中心重新获取并导入新的订阅链接。 操作步骤: 登录官网用户中心; 获取最新订阅链接; 删除客户端中的旧订阅; 导入新的订阅链接; 更新订阅后即可正常使用。 本次升级不会影响: ✅ 套餐有效期 ✅ 剩余流量 ✅ 账号数据 若更新订阅后仍无法连接,请尝试重启客户端,或确认客户端已更新至支持 TUIC 协议的版本。如仍有问题,请联系客服协助处理。 感谢大家一直以来的支持与理解,我们将持续优化线路质量,为大家提供更稳定、更流畅的网络体验。

23 Jul 2026, 21:24 UTC≈732 viewsread 6 August 2026

蜜雪冰城:https://kad520.uk 群组:https://t.me/akad521 频道:https://t.me/akad520

22 Jul 2026, 16:44 UTC≈896 views2 reactionsread 6 August 2026
Forwarded from @yunspeedtestFile

#蜜雪冰城 #家宽三网测速 #移动 #广东移动1000M #惠州移动1000M #四川移动1000M #电信 #浙江电信2000M #深圳电信1000M #联通 #四川联通300M 官网:https://kad520.uk 群组:@abot0901 通知:@akad520 机场自我介绍:便宜大碗 測速次數: 4 测速 from @Yunspeedtest 测速 group @yunspeedtestg 申请投稿/机场测速/广告投放联系:@yunspeedtest_bot

Showing the 11 most recent of 11 posts we hold for @akad520. 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 — 463,887 of 1,160,990entries 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

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 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.

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

“蜜雪冰城” (@akad520), 1,202 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/akad520.

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.