今日快递已分批次发出 未收到快递单号的老板请联系一下 ❤️❤️❤️❤️❤️❤️ ❤️❤️❤️❤️❤️❤️❤️ 客服: @EH918 信誉墙: @hwgg18 双向机器人: @EHSJKbot

Channel
号王机房 @EH918
@EH9188
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
134subscribers
-6 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001776484348 |
|---|---|
| Type | Channel |
| Username | @EH9188 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 3 October 2026 |
| On Telegram | t.me/EH9188 |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 26 September 2026 and assigned it the closest of 31 fixed categories, at 34% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 13:38 | 134 | -2 |
| 10 Sept 2026, 06:21 | 136 | -2 |
| 18 Aug 2026, 07:03 | 138 | -2 |
| 12 Aug 2026, 07:45 | 140 | no change |
| 12 Aug 2026, 01:31 | 140 | first reading |
Engagement
15 posts held, back to 6 April 2026 — 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 page of 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 15 posts for this entry, the most recent from 9 May 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 1m 45s
- Average length
- 15s
Measured directly from 7 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.
Recent posts
大量出半年微信的阅读18带账单 包支付 包加人 带设备一机一号 一机两号都有 客服: @EH918 信誉墙: @hwgg18 双向机器人: @EHSJKbot
🥰测卡中 原机(苹果原装机耐用)带卡直接发货 避免异地联网和多次拔插秒封卡 🥰三网现货秒发中 老人厅卡非网申 客服: @EH918 信誉墙: @hwgg18 双向机器人: @EHSJKbot
客服: @EH918 信誉墙: @hwgg18 双向机器人: @EHSJKbot
🫤私人年活跃鱼号带好友100+要的速度来盘! 😀纯私人号 可小额支付 正常收付款 😀带活跃账单带定期朋友圈「可各种解封 好友 环境 扫脸均可」 到手养3天嘎嘎用 非常耐用 售后在线 嘎嘎猛~ 👍👍👍 安全交易须知流程 客服: @EH918 信誉墙: @hwgg18 双向机器人: @EHSJKbot
三网厅卡 有量:北京. 天津. 上海. 重庆. 广东. 浙江. 河北. 福建. 辽宁. 吉林. 少量:黑龙江. 江苏. 安徽. 山东 . 河南. 四川. 贵州. 广西. 全球手机卡都有货 说需求来聊 一手机房支持视频验证(打视频通话看都可以) 拒绝骗子 底价套路 擦亮眼睛 验证后再合作 老蒋 你的灰产互联网好朋友🧑🤝🧑 欢迎老板 工作室 中介 盘总长期合作! 一手卡源 已经实名 拿到就可以使用!耐造 ! 客服: @EH918 信誉墙: @hwgg18 双向机器人: @EHSJKbot
原机实名一年➕的号,去年12月份的登陆记录,登陆设备半年时间,可修改微信号! 客服: @EH918 信誉墙: @hwgg18 双向机器人: @EHSJKbot
真正的纯私人地推🐟号 已过加好友人脸,已过网络安全验证,可邮寄,每天长期稳定出货 客服: @EH918 信誉墙: @hwgg18 双向机器人: @EHSJKbot
微信老号(可原机带号出) 3 年以上 通信证实名 可加好友 可进群 可进企业 可解封 部分带好友带群 可扫码 可62 需要的老板来问价 客服: @EH918 信誉墙: @hwgg18 双向机器人: @EHSJKbot
到货三网厅卡 有量:北京. 天津. 上海. 重庆. 广东. 浙江. 河北. 福建. 辽宁. 吉林. 少量:黑龙江. 江苏. 安徽. 山东 . 河南. 四川. 贵州. 广西. 全球手机卡都有货 说需求来聊 一手机房支持视频验证(打视频通话看都可以) 拒绝骗子 底价套路 擦亮眼睛 验证后再合作 老蒋 你的灰产互联网好朋友🧑🤝🧑 欢迎老板 工作室 中介 盘总长期合作! 一手卡源 已经实名 拿到就可以使用!耐造 ! 客服: @EH918 信誉墙: @hwgg18 双向机器人: @EHSJKbot
到货香港鸭聊 🉑套餐带号码纯流量 🉑年卡套餐 推荐年卡套餐免费收短信高速流量 自主续费充值上网不需要vpn安全 耐用 注册一体卡 干啥都行 小白直接上✈️ 客服: @EH918 信誉墙: @hwgg18 双向机器人: @EHSJKbot
专业靠谱手机卡 微信 支付宝 抖音 快手 小红书各类app以及原机 🔐伪装发货中 安全放心 ❤️客服: @EH918 🔝频道: @EH9188 双向机器人: @EHSJKbot
Showing the 12 most recent of 15 posts we hold for @EH9188. 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.
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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“号王机房 @EH918” (@EH9188), 134 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/EH9188.
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.