Telegram RegisterThe public register of Telegram
Telegram profile photo for 义乌 金华 永康 东阳 横店 在线榜

Channel

义乌 金华 永康 东阳 横店 在线榜

@GGDD1684

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

209subscribers

+181 since we began measuring on 18 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004332472481
TypeChannel
Username@GGDD1684
CreatedBetween 1 June 2026 and 18 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded18 August 2026
Last confirmed live11 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/GGDD1684

Growth

28209118.518 August 2026 — 28 subscribers18 August 2026 — 28 subscribers19 August 2026 — 38 subscribers26 August 2026 — 125 subscribers2 September 2026 — 185 subscribers11 September 2026 — 209 subscribers18 August 202611 September 2026
6 measurements spanning 24 days, net +181. 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–236 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 19:20209+24
2 Sept 2026, 07:04185+60
26 Aug 2026, 03:47125+87
19 Aug 2026, 00:1238+10
18 Aug 2026, 16:0028no change
18 Aug 2026, 15:4528first reading

Engagement

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

What this channel posts

Video runtime
10s
Average length
5s

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.

Recent posts

18 Aug 2026, 10:34 UTC26 viewsread 18 August 2026
Photo

地区: #义乌 北苑春盛小区 开工时间: 14:00~2:00 年龄:28 修车水费: #400P 是非验证过:未验证 服务内容:无套口 调情 啪啪 各种姿势配合 洗澡🛀 联系 ✈️ @miaomiao980 双向 @miaomiaoshshbot

18 Aug 2026, 06:27 UTC102 viewsread 18 August 2026
Photo

地区: #东阳 汉宁东路 开工时间: 13:00~1:00 年龄:22 修车水费: #400P 是非验证过:未验证 服务内容:无套口 调情 啪啪 各种姿势配合 洗澡🛀 联系 ✈️ @miaomiao980 双向 @miaomiaoshshbot

18 Aug 2026, 06:19 UTC95 viewsread 18 August 2026
Photo

地区: #东阳 汉宁西路 开工时间: 13:00~1:00 年龄:22 26 修车水费: #400P 是非验证过:未验证 服务内容:无套口 调情 啪啪 各种姿势配合 洗澡🛀 联系 ✈️ @miaomiao980 双向 @miaomiaoshshbot

18 Aug 2026, 06:15 UTC77 viewsread 18 August 2026
Photo

地区: #东阳 银泰城 开工时间: 13:00~1:00 年龄:19 22 26 修车水费: #600P 是非验证过:未验证 服务内容:无套口 调情 啪啪 各种姿势配合 洗澡🛀 联系 ✈️ @miaomiao980 双向 @miaomiaoshshbot

18 Aug 2026, 06:14 UTC74 viewsread 18 August 2026
Photo

地区: #东阳 #95 #半套 开工时间: 14:00~2:00 年龄:(不详) 修车水费: #500P 是非验证过:服务一流 真毒龙 顶缸 服务内容:图片上的服务 联系 ✈️ @miaomiao980 双向 @miaomiaoshshbot

18 Aug 2026, 06:12 UTC69 viewsread 18 August 2026
Photo

地区: #东阳 麻车 开工时间: 13:00~1:00 年龄:22 27 修车水费: #400P 是非验证过:验证过 身材好 服务可以 服务内容:无套口 调情 啪啪 各种姿势配合 洗澡🛀 联系 ✈️ @miaomiao980 双向 @miaomiaoshshbot

18 Aug 2026, 06:10 UTC65 viewsread 18 August 2026
Photo

地区: #东阳 麻车小区 开工时间: 18:00~3:00 年龄:22 修车水费: #500P 吹做600p一条龙69 是非验证过:已验证 本人 包满意 服务好态度好 服务内容:无套口 调情 啪啪 各种姿势配合 洗澡🛀 ✈️联系 @miaomiao980 ✈️

18 Aug 2026, 06:06 UTC60 viewsread 18 August 2026
Photo

地区: #义乌 上溪 开工时间: 14:00~1:00 年龄:28 修车水费: #400P 是非验证过:验证过 美颜 服务可以 服务内容:无套口 调情 啪啪 各种姿势配合 洗澡🛀 联系 ✈️ @miaomiao980 双向 @miaomiaoshshbot

Showing the 8 most recent of 8 posts we hold for @GGDD1684. 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 11 September 2026 — this entry's latest reading, not the date you are reading this.

“义乌 金华 永康 东阳 横店 在线榜” (@GGDD1684), 209 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/GGDD1684.

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.