Telegram RegisterThe public register of Telegram
Telegram profile photo for 号王的来时路

Channel

号王的来时路

@hwgg18

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

7subscribers

-7 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-1002802740926
TypeChannel
Username@hwgg18
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live9 October 2026
Measurements held7
Confirmed unchanged1 time, most recently 9 October 2026
On Telegramt.me/hwgg18

Topic

Ecommerce storefront — 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 2 October 2026 and assigned it the closest of 31 fixed categories, at 65% 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

71410.57 August 2026 — 14 subscribers12 August 2026 — 14 subscribers17 August 2026 — 12 subscribers2 September 2026 — 11 subscribers11 September 2026 — 9 subscribers28 September 2026 — 8 subscribers9 October 2026 — 7 subscribers7 August 20269 October 2026
7 measurements spanning 63 days, net -7. 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 6–15 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Oct 2026, 14:027-1
28 Sept 2026, 14:018-1
11 Sept 2026, 17:219-2
2 Sept 2026, 04:1211-1
17 Aug 2026, 09:2312-2
12 Aug 2026, 01:3014no change
7 Aug 2026, 19:1214first reading

Engagement

6 posts held, back to 7 May 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 6 posts for this entry, the most recent from 18 May 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

18 May 2026, 13:53 UTC12 viewsread 12 August 2026
Photo

🥰2026.5.18 记录发货日常 1️⃣4把(3-6月号实名带支付)寄江苏 2️⃣1把(抖音原机老人号带实名)+1把(抖音原机地推实名号)寄广西 3️⃣6张联通老卡寄云南 🤪感谢老板们支持 ❤️客服: @EH918 🔝频道: @EH9188 双向机器人: @EHSJKbot

17 May 2026, 13:25 UTC10 viewsread 12 August 2026
Photo

❤️❤️❤️❤️❤️❤️❤️ 部分交易记录 信任寥寥数语便可成交 以诚相待 以礼相待 ❤️❤️❤️❤️❤️❤️❤️ 🤪感谢老板们支持 ❤️客服: @EH918 🔝频道: @EH9188 双向机器人: @EHSJKbot 你有好眼光我有好品质合作共赢 信任胜过千言万语不负每一份信任

11 May 2026, 13:32 UTC16 viewsread 12 August 2026
Photo

🥰2026.5.11 记录发货日常 1️⃣2把半年阅读 带资料(可企业带手持 可支付)寄江西 2️⃣7把原机(微信私人地推号)寄浙江 3️⃣3把(抖音原机带月号)寄河南 🤪感谢老板们支持 ❤️客服: @EH918 🔝频道: @EH9188 双向机器人: @EHSJKbot

9 May 2026, 11:54 UTC12 viewsread 12 August 2026
Photo

🥰2026.5.9 记录发货日常 1️⃣4把(抖音原机带月号)+3张移动老卡寄广东 2️⃣3把(半年实名带支付)1把(五年实名带支付)寄福建 3️⃣6张电信老卡寄贵州 🤪感谢老板们支持 ❤️客服: @EH918 🔝频道: @EH9188 双向机器人: @EHSJKbot

8 May 2026, 14:05 UTC11 viewsread 12 August 2026
Photo

🥰2026.5.8 记录发货日常 1️⃣1把(五年以上实名带支付)+1把(年号实名带支付)寄四川 2️⃣3把(抖音原机带月号)寄湖南 3️⃣7张移动老卡寄广东 🤪感谢老板们支持 ❤️客服: @EH918 🔝频道: @EH9188 双向机器人: @EHSJKbot

7 May 2026, 13:24 UTC12 viewsread 12 August 2026
Photo

🥰2026.5.7 记录发货日常 1️⃣ 4把五年以上(微信实名带支付)+5(sm联通老卡)寄黑龙江 2️⃣6张(sm移动老卡)寄河南 3️⃣8张(sm联通老卡)寄广东 🤪感谢老板们支持 ❤️客服: @EH918 🔝频道: @EH9188 双向机器人: @EHSJKbot

Showing the 6 most recent of 6 posts we hold for @hwgg18. 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.

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

“号王的来时路” (@hwgg18), 7 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/hwgg18.

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.