Channel name was changed to «东南亚打工日记»

Channel
东南亚打工日记
@ABZS886
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
114subscribers
+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 | -1001434894239 |
|---|---|
| Type | Channel |
| Username | @ABZS886 |
| Created | Between 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/ABZS886 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 06:02 | 114 | no change |
| 7 Aug 2026, 22:03 | 114 | first reading |
Engagement
20 posts held, back to 3 August 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 8 June 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 477
- Videos
- 33
- Links
- 1
Lifetime counters from Telegram’s own channel header, read 9 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
5 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 60.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 3 | 60.0% | |
| ❤ | 2 | 40.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 7 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 5reactions 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 3 August 2024 to 8 June 2025, 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
17:00 球会友谊 格拉茨AK VS 斯崔普费宁魏登 主队-0.5/1 17:30 澳威超 中央海岸水手 VS 公牛学院 上半场大1.5 17:45 奥昆乙 魔术联 VS 北极星 主队-1 19:00 澳达超 明迪爱瑟斯 VS 海伦斯 客队+1/1.5 21:00 亚洲杯 文莱 VS 澳门 小2.5 22:00 欧国联 哈萨克斯坦 VS 挪威 客队-1/1.5
❤1
17:00 缅甸甲 银星 VS 雅儿曼妮亚联 大3.5/4 20:00 英U21 维冈竞技 VS 布伦特福德 上半场大1.5 21:00 英U21 巴恩斯利 VS 布里斯托尔城 大3/3.5 21:00 英U21 赫尔城 VS 女王公园巡游者 客队-0/0.5 22:30 丝萝妇科病 盖尔尼察 VS 特斯拉斯特洛普科夫 客队-2/2 23:00 罗乙 米耶尔库雷亚丘克 VS 梅塔鲁布泽特 主队-1.5 23:30 克罗丙 NIK哈鲁布詹 VS NIK克雷斯 上半场小1/1.5
日职联18:00 福冈黄蜂VS神户 推荐:全场小2球 2024.9.1 英超20:30 切尔西VS水晶宫 推荐:全场大3球 法甲21:00 摩纳哥VS朗斯 推荐:全场大3球 荷22:45 埃因霍温VS前进之鹰 推荐:全场大4球 德甲23:30 拜仁VS弗赖堡 推荐:全场大4球 西甲01:00 塞维利亚VS赫罗纳 推荐:全场大2.75球
👍1
乌克超20:30 奥博隆VS柔亚 推荐:客队-0 2024.8.30 阿联21:55 阿巴塔VS阿尔艾因 推荐:全场大3.75球 芬甲23:30 查普斯VS米克力 推荐:全场大3球 意甲00:30 威尼斯VS都灵 推荐:主队+0.5 意甲02:45 国米VS亚特兰大 推荐:全场大2.75球 法甲02:45 里昂VS斯特拉斯堡 推荐:全场大2.75球
澳足总17:30 休城VS墨尔本 推荐:客队+2.25 2024.8.27 泰超20:00 狮子港VS素可泰 推荐:全场大3.5球 印尼超20:00 普萨VS巴厘联 推荐:全场大2.75球 西甲01:00 马洛卡VS塞维利亚 推荐:全场小2球 挪01:00 康斯文格VS桑德尼斯 推荐:全场大3.5球 欧冠杯03:00 加拉塔VS年青人 推荐:全场大3.5球
👍1
日职联18:00 磐田喜悦VS札幌 推荐:全场大3球 2024.8.25 英21:00 伯恩茅斯VS纽卡斯尔 推荐:全场大3球 德甲21:30 沃尔夫斯堡VS拜仁 推荐:全场大3球 西甲23:00 皇马VS瓦拉多利德 推荐:全场大3.5球 英超23:30 利物浦VS布伦特 推荐:主队-2 法甲02:45 马赛VS兰斯 推荐:全场大3球
👍1
15:00 印米佐超 米佐拉姆警察 VS 西菲尔文格伦FC 上半场大1/1.5 16:30 印尼超 三宝垄 VS PSBS巴克伦佛 客队+1/1.5 17:30 澳维超 海德堡 VS 休姆 小3 18:15 奥塔超 格莱诺基骑士 VS 金保罗夫狮联 大3.5/4 20:00 泰超 罗勇 VS 蒙通联 客队-0.5/1 20:00 因此 帕尔斯巴亚 VS 巴日托 主队-0.5/1 22:00 阿联超 奥鲁巴 VS 迪拜胜利 小3
⚽️⚽️足球盘口⚽️⚽️ 【日皇杯】 2024/08/21 18:00 大阪钢巴 VS 湘南海洋 ⭐️推荐 👉让球盘:大阪钢巴 -0/0.5 👉全场大小盘:大 2.5 【中协杯】 2024/08/21 19:35 山东泰山 VS 河南队 ⭐️推荐 👉让球盘: 山东泰山 -0.5/1 👉全场大小盘:小 2.5 【欧冠杯】 2024/08/22 03:00 伯尔尼年轻人 VS 加拉塔萨雷 ⭐️推荐 👉让球盘:加拉塔萨雷 -0.5 👉全场大小盘:大 2.5/3
16:30 澳昆超U23 黄金海岸联 VS 莫顿城 上半场大1.5 17:30 奥昆女超 阳光海岸流浪者 VS 布里斯班城 大3.5 18:00 韩K联女 世宗 VS 水原FC 小3.5 20:00 澳西超 斯特灵马其顿 VS 帕斯光荣 主队-1 22:30 乌兹超 费尔干纳石油工人 VS 吉扎克栗特 小2/2.5 23:59 欧会杯 诺亚 VS 鲁容贝罗克 主队-0.5 23:59 丹麦甲 罗斯基勒 VS 霍森斯 客队-0.5
泰超20:00 狮子港VS清莱联 推荐:全场大3球 2024.8.19 芬甲23:30 科特卡VS学院 推荐:全场大3.5球 意甲00:30 莱切VS亚特兰大 推荐:客队-0 西甲01:00 瓦拉多VS西班牙人 推荐:主队-0 意甲02:45 尤文图斯VS科莫 推荐:主队-1 英超03:00 莱斯特城VS热刺 推荐:全场大3球
❤1
日18:00 川崎前锋VS横滨水手 推荐:全场大3.5球 2024.8.17 英超19:30 伊普斯VS利物浦 推荐:全场大3.5球 英超22:00 阿森纳VS狼队 推荐:全场大3.5球 英22:00 纽卡斯尔VS南安普敦 推荐:主队-1.5 意甲00:30 热那亚VS国际米兰 推荐:客队-1 法甲03:00 摩纳哥VS圣埃蒂安 推荐:全场大3球
Showing the 12 most recent of 20 posts we hold for @ABZS886. 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 — 61,756 of 1,350,102entries 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 2 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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“东南亚打工日记” (@ABZS886), 114 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/ABZS886.
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.