🧹关注导航不迷路 🇲🇲缅甸新闻:@xinwenbd 🇰🇭柬埔寨新闻:@dnybaoguangg 🇱🇰斯里兰卡新闻:@lankaxinwen1 📺苹果TV电视剧:@dianshiju8090 📺苹果TV电影:@PGTV22 🍉吃瓜频道:@chiguaa258 🍉吃瓜频道:@cgcg188 🍑韩国三级:@xiuchewenxi
❤16😁16🔥14👍11🎉6

Channel
@sabaodh
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
9,061subscribers
-592 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003265253828 |
|---|---|
| Type | Channel |
| Username | @sabaodh |
| Created | 6 November 2025 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/sabaodh |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 22:34 | 9,061 | -219 |
| 26 Aug 2026, 15:47 | 9,280 | -525 |
| 23 Aug 2026, 12:37 | 9,805 | +117 |
| 19 Aug 2026, 14:45 | 9,688 | -481 |
| 18 Aug 2026, 12:37 | 10,169 | -92 |
| 17 Aug 2026, 10:47 | 10,261 | -79 |
| 15 Aug 2026, 19:03 | 10,340 | -240 |
| 14 Aug 2026, 07:04 | 10,580 | -90 |
| 13 Aug 2026, 01:28 | 10,670 | +137 |
| 12 Aug 2026, 02:31 | 10,533 | -67 |
| 10 Aug 2026, 23:12 | 10,600 | +950 |
| 7 Aug 2026, 20:37 | 9,650 | -3 |
| 7 Aug 2026, 18:02 | 9,653 | first reading |
9 posts held, back to 6 November 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 35 pagesof 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 9 posts for this entry, the most recent from 17 June 2026. An engagement rate over an empty window would be a number about nothing.
757 reactions across 8 posts, in 12 distinct kinds. The most used accounts for 36.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤🔥 | 274 | 36.2% | |
| ❤ | 75 | 9.91% | |
| 🔥 | 62 | 8.19% | |
| 🥰 | 59 | 7.79% | |
| 👍 | 56 | 7.40% | |
| 🤩 | 55 | 7.27% | |
| 💯 | 54 | 7.13% | |
| 🎉 | 53 | 7.00% | |
| 😍 | 48 | 6.34% | |
| 😁 | 16 | 2.11% | |
| 👌 | 4 | 0.528% | |
| 👀 | 1 | 0.132% |
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 8 of the 9 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 757reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 6 November 2025 to 17 June 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.
🧹关注导航不迷路 🇲🇲缅甸新闻:@xinwenbd 🇰🇭柬埔寨新闻:@dnybaoguangg 🇱🇰斯里兰卡新闻:@lankaxinwen1 📺苹果TV电视剧:@dianshiju8090 📺苹果TV电影:@PGTV22 🍉吃瓜频道:@chiguaa258 🍉吃瓜频道:@cgcg188 🍑韩国三级:@xiuchewenxi
❤16😁16🔥14👍11🎉6
解除 苹果手机 敏感内容 限制: 必须先设置用户名id Telegram 手机版 @sabaodh https://web.telegram.org 浏览器打开官网 登陆账号 (验证码 在app内) 成功登入Telegram 网页版后,点选左上角“选单”按钮 👉 点选“Settings” 👉 Privacy and Security 👉 Sensitive Content 👉 开启Disable filtering √ 👉 重启app 重新加群 (迪拜号码无选项)
❤3🔥2👌1🥰1
🧹关注导航不迷路 🇲🇲缅甸新闻:@xinwenbd 🇰🇭柬埔寨新闻:@dnybaoguangg 🇱🇰斯里兰卡新闻:@lankaxinwen1 📺苹果TV电视剧:@dianshiju8090 📺苹果TV电影:@PGTV22 🍉吃瓜频道:@chiguaa258 🍑韩国三级:@xiuchewenxi
❤🔥229❤2👍1🔥1🥰1
🤩 沙包导航 🤩
💯50❤45🤩43🎉40😍39👍38🥰38❤🔥34
各位群友,大家好! 我之前【沙包大的拳头】账号已被冻结,现在新联系 【半语山岚】@PO1616 给大家带来不变深感抱歉😏
👌3🔥1🥰1
🐎 各位朋友马年快乐! 新的一年祝大家: 钱包鼓鼓,烦恼跑跑; 好运常在,霉运走开; 工作不累,睡觉不贵; 想吃就吃,想睡就睡; 天天开心,顿顿有肉! 愿大家马年: 马上有钱,马上有对象,马上有好消息!🎉
❤4🥰2🔥1
🧹关注导航不迷路 🇲🇲缅甸新闻:@xinwenbd 🇰🇭柬埔寨新闻:@dnybaoguangg 🍑日本AV:@jinguoji01 📺苹果TV电视剧:@dianshiju8090 📺苹果TV电影:@PGTV22 🍉吃瓜频道:@chiguaa258 🍑韩国三级:@xiuchewenxi
🥰8🤩7🔥5❤🔥4😍4❤3👍3🎉2
沙包导航
🥰8❤🔥7🔥7🎉5🤩5😍5👍3❤2
Channel created
Showing the 9 most recent of 9 posts we hold for @sabaodh. 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 — 274,536 of 1,627,068entries 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.
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.
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.
@sabaodh named 1 handle 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.
References a handle that is not a live channel — we have no record it ever was one.
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.
“沙包导航🔍” (@sabaodh), 9,061 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/sabaodh.
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.