Telegram RegisterThe public register of Telegram

Channel

苏州亚洲头条榜

@gdgdgffbd

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

20,176subscribers

-84 since we began measuring on 12 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002889943845
TypeChannel
Username@gdgdgffbd
Description交友 约车赛好去处 唯一管理: @wq88777bot 认证资源: @gdgdgffbd 本群域名: @wdgx4
CreatedBetween 1 June 2025 and 31 August 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live15 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/gdgdgffbd

Growth

20,16120,26020,210.512 August 2026 — 20,260 subscribers12 August 2026 — 20,260 subscribers14 August 2026 — 20,161 subscribers15 August 2026 — 20,176 subscribers20,17612 August 202615 August 2026
4 measurements spanning 2 days, net -84. 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 20,146–20,275 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 08:4220,176+15
14 Aug 2026, 00:5920,161-99
12 Aug 2026, 23:0020,260no change
12 Aug 2026, 22:4920,260first reading

Engagement

7 posts held, back to 27 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 6 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
22.0%
avg views ÷ 20,176 subscribers
Avg views / post
4,440
7 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
7
of 7 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 13 August 2026
Posts held7 (27 July 202613 August 2026)
Views total31,060
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 20:06 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
224
Videos
56
Links
26

Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
33s
Average length
8s

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.

Recent posts

13 Aug 2026, 07:00 UTC610 viewsread 15 August 2026
Photo

全国林妹高端外围【大⭕️】 #定金预约 本群可担保 💎专注各市区修车 🈶洋马,空姐,少妇,萝莉, 御姐等高素质高颜值🉑上门 🈶教室 ✡️奢华的环境、全套服务、至尊享受、帝王体验 ♏️联系客服情妹: @lingmei888168 ♏️双向客服林妹: @wai998bot ♒️总频道: https://t.me/yewuzuvip #本群推荐信誉客服

6 Aug 2026, 11:11 UTC≈3,250 viewsread 15 August 2026
Photo

#潘姐高端极品【大⭕️】 #诚信客服 已验证 #定金预约 群管已担保 💎专注特区一线城市修车,纯一手资源 只有你想不到的,没有我没有的。 ✡️奢华的环境、全套一条龙服务、至尊享受、帝王体验 ♒️总频道: @hnanjingjujidi ♏️客服潘姐: @panjie888168bot

3 Aug 2026, 03:38 UTC≈4,350 viewsread 15 August 2026
Photo

🟡昵称: 阿依古丽 🕐地区:吴中区 🚀电报:@Z850527 🔔频道: https://t.me/ay850527 🔴水费:📤课表查看图📤 🔴标签 #可放心出击 #已验证 #车费定金狼友自己随意不超过100

2 Aug 2026, 05:07 UTC≈4,530 viewsread 15 August 2026
Photo

#苏州 全区都可以安排 微信扫码查看资料 只做精品 不做一次性生意 各种选择任君挑选 一次交易终生朋友 中午 12:00 — 晚上11:00 外卖 上班时间 下午 06:00 — 凌晨 3:00 每天300人在线选择 低端 4米快餐 6米全套 中端 6米快餐 8米全套 高端10-12米全套 外围探花24-30 09/10年嫩妹可供选择 可以选择自己合适的价格 扫码查看资料 联系:@Suzhoumomo 双向机器人🤖:https://t.me/Suzhoumomobot 群组:https://t.me/suzhou985985 频道:https://t.me/suzhou857857

30 Jul 2026, 06:37 UTC≈5,620 viewsread 15 August 2026
Photo

🟡昵称: 悦悦 🕐地区:#吴中区 🤖双向加 @szyy696bot 🚀电报:@riley_6676257 🔔频道: https://t.me/https_6257 🔴水费:📤课表查看图📤 🔴标签 #可放心出击 #已验证 #车费定金狼友自己随意不超过100 #老师狼友请看下方评论区⬇️

28 Jul 2026, 05:54 UTC≈6,090 viewsread 15 August 2026
Photo

欢迎来到 👌球哈体育👌 全球领先的一体化体育娱乐平台 ❤️☺️☺️☺️☺️☺️☺️ 不只是娱乐,更是属于顶级玩家的竞技世界。 ❤️ 在这里,速度、安全与体验,被重新定义 ❤️ 原生 APP 直连体验 丝滑流畅,极速响应,海量赛事一键即达。 ❤️ USDT 极速存提 专属加密通道,秒速到账,安全稳定,真正实现零等待。 ❤️超高返水机制 体育最高 🔤🔤🔤🔤|电子最高 🔤🔤🔤🔤 1 元起返,让每一次热爱都更具价值。 ❤️ 全维度娱乐生态 🔘😉😅😚🔘🙈😏😝🔘😏😍😀🔘😞😱😀 🔘😄😃😃🔘😊😅😏🔘😄🙃😢🔘 全天候精彩不断,尽享沉浸式娱乐体验。 ➡️ 立即加入 球哈体育 开启属于您的巅峰之旅! ❤️❤️❤️❤️❤️❤️❤️❤️❤️❤️❤️❤️❤️ 信誉为本,实力护航 💰 ⸻ ❤️ 电子, 真人无审核包出款. ❤️ U存U提出款无上限 日出亿U. 🔖 官方网址: 15095.COM 🔖 官方网址: QH0088.COM 🔖

27 Jul 2026, 07:26 UTC≈6,610 viewsread 15 August 2026
Photo

🟡昵称: #困困 🕐地区: #姑苏区 🤖双向:@kunkun1680_Bot 🚀电报:@kkun0168 🔴水费:📤课表查看图📤

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

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

“苏州亚洲头条榜” (@gdgdgffbd), 20,176 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/gdgdgffbd.

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.