Telegram RegisterThe public register of Telegram
Telegram profile photo for wz071998

Channel

wz071998

@wz071998

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

1,411subscribers

+143 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002237881259
TypeChannel
Username@wz071998
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live9 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/wz071998

Growth

1,2681,4111,339.58 August 2026 — 1,268 subscribers9 August 2026 — 1,269 subscribers12 August 2026 — 1,286 subscribers16 August 2026 — 1,316 subscribers19 August 2026 — 1,326 subscribers22 August 2026 — 1,340 subscribers26 August 2026 — 1,363 subscribers29 August 2026 — 1,382 subscribers31 August 2026 — 1,398 subscribers4 September 2026 — 1,410 subscribers9 September 2026 — 1,411 subscribers8 August 20269 September 2026
11 measurements spanning 32 days, net +143. 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 1,247–1,432 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 18:371,411+1
4 Sept 2026, 03:011,410+12
31 Aug 2026, 20:461,398+16
29 Aug 2026, 06:341,382+19
26 Aug 2026, 04:541,363+23
22 Aug 2026, 20:041,340+14
19 Aug 2026, 12:231,326+10
16 Aug 2026, 16:451,316+30
12 Aug 2026, 17:071,286+17
9 Aug 2026, 06:411,269+1
8 Aug 2026, 20:451,268first reading

Engagement

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

What this channel posts

Video runtime
21s
Average length
11s

Measured directly from 2 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.

Reaction mix

23 reactions across 7 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
23100.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 12 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 23 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 14 August 2025 to 8 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

9 Jul 2026, 03:41 UTC≈2,580 views3 reactionsread 8 August 2026

报告 #6a4e3342b76161ca71a41758 合肥资源报告:https://t.me/hf_lsj 提交者:装饰公司 Bristol ⏰ 出击时间:2026-07-08 👩‍🏫 老师名称:#月月 🎂 目测年龄:30左右 📍 所在位置:蜀山 💰 修车水费:400 💃 身高身材:中等匀称(159-165cm 标准身材) 👩 颜值相似:8 🍈 罩杯胸型:C 🧼 卫生评价:非常干净 🛡️ 安全评价:安全 📋 服务项目:与课表一致 📝 服务详情:刚好路过附近,20分钟到达老师楼下,老师沈阳人。皮肤白,服务口活非常好,可以和老师玩69,鲍鱼水多,做爱蛇吻配合度高,一点都机车,很听话。 ⭐ 评价程度:#很好 👍 优缺点:蛇吻,69,做爱配合蛇吻

3

15 Sept 2025, 06:20 UTC≈6,050 views7 reactionsread 8 August 2026

报告 #68c5232c6b9b0f247120af13 合肥资源报告:https://t.me/hf_lsj 提交者:citywalker ⏰ 出击时间:2025-09-13 👩‍🏫 老师名称:#月月,四妹 🎂 目测年龄:25左右 📍 所在位置:蜀山 💰 修车水费:1000 💃 身高身材:中等偏瘦(159-165cm 偏瘦) 👩 颜值相似:8 🍈 罩杯胸型:B 🧼 卫生评价:非常干净 🛡️ 安全评价:比较安全 📋 服务项目:比课表多 📝 服务详情:两个妹子很漂亮热情的帮我洗澡,我们去床上先开始服务,她们舌头很软,从脖子开始到全身,酥酥麻麻,飘飘欲仙,然后其中一个妹子骑到我身上开始下一步,另一个则负责继续诱惑调情,后来又换另一个妹子做,最后受不了全部输出,很爽 ⭐ 评价程度:#很好 👍 优缺点:白,口活好

7

13 Sept 2025, 08:24 UTC≈2,580 views3 reactionsread 8 August 2026

报告 #68c5232c6b9b0f247120af13 合肥资源报告:https://t.me/hf_lsj 提交者:citywalker ⏰ 出击时间:2025-09-13 👩‍🏫 老师名称:#月月,四妹 🎂 目测年龄:25左右 📍 所在位置:蜀山 💰 修车水费:1000 💃 身高身材:中等偏瘦(159-165cm 偏瘦) 👩 颜值相似:8 🍈 罩杯胸型:B 🧼 卫生评价:非常干净 🛡️ 安全评价:比较安全 📋 服务项目:比课表多 📝 服务详情:两个妹子很漂亮热情的帮我洗澡,我们去床上先开始服务,她们舌头很软,从脖子开始到全身,酥酥麻麻,飘飘欲仙,然后其中一个妹子骑到我身上开始下一步,另一个则负责继续诱惑调情,后来又换另一个妹子做,最后受不了全部输出,很爽 ⭐ 评价程度:#很好 👍 优缺点:白,口活好

3

14 Aug 2025, 12:13 UTC≈6,550 views4 reactionsread 8 August 2026

报告 #689dce8645537eeadd1fc02c 合肥资源报告:https://t.me/hf_lsj ⏰ 出击时间:2025-08-14 👩‍🏫 老师名称:#月月 🎂 目测年龄:25左右 📍 所在位置:蜀山 💰 修车水费:1200 💃 身高身材:中等匀称(159-165cm 标准身材) 👩 颜值相似:8 🍈 罩杯胸型:B 🧼 卫生评价:干净 🛡️ 安全评价:比较安全 📋 服务项目:与课表一致 📝 服务详情:进门了很热情的打招呼给人舒服的感觉,我找的是月月和她的闺蜜两个人。她们帮我洗澡然后去倒床上两个人配合默契。分工明确。技术都很好,舌头很软。特别舒服,差点又点受不了。后来我们开始运动三个人互换,很不一样的感觉,经过几个回合我很满意的交枪 ⭐ 评价程度:#好 👍 优缺点:好

4

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

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

“wz071998” (@wz071998), 1,411 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/wz071998.

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.