Telegram RegisterThe public register of Telegram
Telegram profile photo for 无锡大圈【精品推荐】

Channel

无锡大圈【精品推荐】

@WUXIGAODUANZHENXUAN

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

1,667subscribers

+19 since we began measuring on 15 August 2026

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

Register entry

Telegram ID-1003719329458
TypeChannel
Username@WUXIGAODUANZHENXUAN
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live26 September 2026
Measurements held9
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/WUXIGAODUANZHENXUAN

Topic

Adult — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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

1,6481,6671,657.515 August 2026 — 1,648 subscribers16 August 2026 — 1,650 subscribers23 August 2026 — 1,649 subscribers25 August 2026 — 1,655 subscribers4 September 2026 — 1,657 subscribers10 September 2026 — 1,652 subscribers13 September 2026 — 1,651 subscribers17 September 2026 — 1,653 subscribers26 September 2026 — 1,667 subscribers15 August 202626 September 2026
9 measurements spanning 42 days, net +19. 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,645–1,670 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Sept 2026, 04:421,667+14
17 Sept 2026, 16:381,653+2
13 Sept 2026, 17:161,651-1
10 Sept 2026, 04:391,652-5
4 Sept 2026, 18:011,657+2
25 Aug 2026, 19:231,655+6
23 Aug 2026, 05:181,649-1
16 Aug 2026, 15:451,650+2
15 Aug 2026, 08:011,648first reading

Engagement

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

What this channel posts

Video runtime
16s
Average length
4s

Measured directly from 4 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

1 reaction across 1 post, in 1 kind.

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

Measured over the 4 most recent posts we hold, published 15 August 2026 to 15 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

15 Aug 2026, 04:15 UTC32 viewsread 15 August 2026
Photo

🏠工作室: #梁溪区东岭锡上 😓艺名: 美美 😋介绍: 无锡纯爱女友 Age年龄/05年 •eight身高/165 • eight/体重 90 • •Bust胸围/D • 刚↓ 氵嫩泬白翠 • 笔直长腿 天然0整 • 温柔听话 不催不事 待客温柔如初恋 • S身材 皮肤雪白 性格温柔 来一场女友式的体验 • 🉑🐍纹🉑🚗🉑69✌️登记 🥰:2200/P 🥰: 4400/PP ✈️能否外出:🉑 🔤🔤预约私聊妲己🔤🔤 限制私聊: @WUXIDAJI_bot 点击查看总资料合集 🖥 预约流程大全📱 验证报告合集 ️ 一键关注所有资源 无锡交流总群

15 Aug 2026, 04:14 UTC28 views1 reactionsread 15 August 2026
Photo

📱:骚蜜 介绍:能舌吻会夹,💦多活好 😦:#梁溪区 🤪:2200/P 4400/PP 🔈大圈内容: 基本三件套➕ 妹子硬件 情绪价值 ➕ 顶配私密高雅环境! 🔤🔤预约私聊妲己🔤🔤 限制私聊: @WUXIDAJI_bot 点击查看总资料合集 🖥 预约流程大全📱 验证报告合集 ️ 一键关注所有资源 无锡交流总群

❤1

15 Aug 2026, 04:14 UTC24 viewsread 15 August 2026
Photo

昵称:妙妙 介绍:• 𝐇𝐞𝐢𝐠𝐡𝐭. 168 • 𝐖𝐞𝐢𝐠𝐡𝐭. 98 • 𝐁𝐮𝐬𝐭. D • 𝐀𝐠𝐞. 06 服务:可69🐍💋🉑✌️🉑双 😦:#新吴区公园九里 🤪:2200/P 4400/PP 🔤🔤预约私聊妲己🔤🔤 限制私聊: @WUXIDAJI_bot 点击查看总资料合集 🖥 预约流程大全📱 验证报告合集 ️ 一键关注所有资源 无锡交流总群 🔥验证报告A: https://t.me/WUXIYH/32336

15 Aug 2026, 04:13 UTC25 viewsread 15 August 2026
Photo

昵称:白幼纯(🉑双飞 🉑✌️) 地址:#梁溪区 料金:2200P 4400PP 妹子预约流程如下! A: 工作室 可外出 B: 无锡大圈预约制度 !提前找妲己预定好时间! C: 告诉妲己几点可以到达妹子工作室以及次数! D:大圈服务: 基本三件套➕💋 主要是妹子硬件➕情绪价值 ➕顶配私密高雅环境! 🔤🔤预约私聊妲己🔤🔤 限制私聊: @WUXIDAJI_bot 点击查看总资料合集 🖥 预约流程大全📱 验证报告合集 ️ 一键关注所有资源 无锡交流总群

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

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

“无锡大圈【精品推荐】” (@WUXIGAODUANZHENXUAN), 1,667 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/WUXIGAODUANZHENXUAN.

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.