Telegram RegisterThe public register of Telegram
Telegram profile photo for 急救包官方频道

Channel

急救包官方频道

@MUX8866

On this record: Previous handles · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,798subscribers

+739 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003783458586
TypeChannel
Username@MUX8866
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live29 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/MUX8866

Previous handles

@MUX8866 was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@Demon00888
held 8 August 20268 August 2026

Growth

1,0591,7981,428.57 August 2026 — 1,059 subscribers7 August 2026 — 1,061 subscribers8 August 2026 — 1,061 subscribers10 August 2026 — 1,096 subscribers22 August 2026 — 1,266 subscribers23 August 2026 — 1,338 subscribers27 August 2026 — 1,753 subscribers29 August 2026 — 1,798 subscribers7 August 202629 August 2026
8 measurements spanning 22 days, net +739. 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 948–1,909 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 21:161,798+45
27 Aug 2026, 00:431,753+415
23 Aug 2026, 23:361,338+72
22 Aug 2026, 16:001,266+170
10 Aug 2026, 03:211,096+35
8 Aug 2026, 00:181,061no change
7 Aug 2026, 14:051,061+2
7 Aug 2026, 12:151,059first reading

Engagement

13 posts held, back to 2 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 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
65.8%
avg views ÷ 1,798 subscribers
Avg views / post
1,180
13 posts measured
Reaction rate
0.337%
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 9 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 22 August 2026
Posts held13 (2 August 202622 August 2026)
Views total15,372
Reactions total24
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Aug 2026, 16:00 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.

Reaction mix

24 reactions across 9 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍24100.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 9 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 24reactions 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 2 August 2026 to 22 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

22 Aug 2026, 11:54 UTC81 views3 reactionsread 22 August 2026
Photo

传媒招人中,给固定奖金,卡密免费玩,会拍视频,不要废物 👉项目介绍 👉想当代理赚米点我 👉提卡点我 👉上APK广告位点我 ❤️售后客服:@Demon886600 ❤️双向客服:@TAOBI886_bot

👍3

22 Aug 2026, 08:52 UTC130 views3 reactionsread 22 August 2026
Photo

请不要质疑神,目前依旧稳定奔放中,该修复的东西都修复了,你们直接安排就行了 👉项目介绍 👉想当代理赚米点我 👉提卡点我 👉上APK广告位点我 ❤️售后客服:@Demon886600 ❤️双向客服:@TAOBI886_bot

👍3

22 Aug 2026, 05:11 UTC163 views2 reactionsread 22 August 2026

🔥7s无限授权数据号源头旗舰店🔥 🥇一年诚信经营,三年售后兜底 📩💵购买地址https://mall.682fk.cn/shop/QIL2R3MW 🔝数据号主频道:https://t.me/bingpannb 🔗无限授权网址:http://www.kssq1.com/ 🔥点我进入每天免费发放1000+数据号频道

👍2

22 Aug 2026, 04:20 UTC177 views1 reactionsread 22 August 2026
File

【急救包1.2.7硬件断点漏打追锁内核】 ✅修复APK启动卡悬浮窗问题 ✅加固卡密验证加密问题 ❌开启辅助前确保你的设备重启过 ❌设备不好请不要开掩体漏打 ❌在验证卡密时不要开启VPN APK启动完美规避终端检测,独家硬件断点驱动没有任何特征现象,驱动多,适配4-6系机型,新价比拉满,培育出多个战神,只做精品,CPU占比极低,可流畅运行,绘制不卡顿,采用模型漏打不动内存,内置解密不怕下发问题

👍1

21 Aug 2026, 05:57 UTC301 views8 reactionsread 22 August 2026
Photo

如果1.2.6使用不了请使用1.2.5复活版,由于加密所以导致启动有点问题 👉项目介绍 👉想当代理赚米点我 👉同款提卡 👉上APK广告位点我 ❤️售后客服:@Demon886600 ❤️双向客服:@TAOBI886_bot

👍8

20 Aug 2026, 10:38 UTC300 views1 reactionsread 22 August 2026
Photo

🌟部分验证上不去问题正在解决,大家不要着急,只有部分人用不了 👉项目介绍 👉想当代理赚米点我 👉同款提卡 👉上APK广告位点我 ❤️售后客服:@Demon886600 ❤️双向客服:@TAOBI886_bot

👍1

7 Aug 2026, 18:43 UTC78 views1 reactionsread 8 August 2026
Photo

😊依旧稳定,放心使用高质量反馈加时,想要当代理的过来联系客服 💝项目介绍 😝想要免费赚米点我 🤩同款提卡 👏想玩其他项目点我 ❤️售后客服:@Demon886600 ❤️双向客服:@TAOBI886_bot

👍1

6 Aug 2026, 13:31 UTC462 views4 reactionsread 8 August 2026
File

😀全部人使用DEMON 1.2.1版本的新包 1️⃣🔣追踪和驱动全部重新改写,使追踪枪枪到肉 2️⃣🔣新驱动增强稳定性,无特征现象(不包括其余驱动) 3️⃣🔣修复全图信息显示BUG,APK图标轻微改动 ➡️玩伊雷娜公益解密端口点我进频道

👍4

6 Aug 2026, 09:16 UTC527 viewsread 8 August 2026
Photo

😊依旧稳定,放心使用高质量反馈加时,想要当代理的过来联系客服 💝项目介绍 😝想要免费赚米点我 🤩同款提卡 👏想玩其他项目点我 ❤️售后客服:@Demon886600 ❤️双向客服:@TAOBI886_bot

5 Aug 2026, 13:57 UTC723 viewsread 8 August 2026
Photo

😊最新版本同号地铁得吃依旧稳定,放心使用高质量反馈加时,想要当代理的过来联系客服 💝项目介绍 😝想要免费赚米点我 🤩同款提卡 👏想玩其他项目点我 ❤️售后客服:@Demon886600 ❤️双向客服:@TAOBI886_bot

4 Aug 2026, 09:40 UTC940 viewsread 8 August 2026
Photo

😊依旧稳定,放心使用高质量反馈加时,想要当代理的过来联系客服 💝项目介绍 😝想要免费赚米点我 🤩同款提卡 👏想玩其他项目点我 ❤️售后客服:@Demon886600 ❤️双向客服:@TAOBI886_bot

2 Aug 2026, 10:27 UTC≈6,060 viewsread 8 August 2026
Photo

😊依旧稳定,放心使用高质量反馈加时,想要当代理的过来联系客服 💝项目介绍 😝想要免费赚米点我 🤩同款提卡 👏想玩其他项目点我 ❤️售后客服:@Demon886600 ❤️双向客服:@TAOBI886_bot

Showing the 12 most recent of 13 posts we hold for @MUX8866. 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 — 22,596 of 1,628,524entries 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.

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.

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

“急救包官方频道” (@MUX8866), 1,798 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/MUX8866.

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.