Channel
@gghio345
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
92subscribers
+0 since we began measuring on 19 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003680794716 |
|---|---|
| Type | Channel |
| Username | @gghio345 |
| Description | 频道 https://t.me/gghio345 私聊 @xyy098 机器人 @yangyuoJ_bot |
| First recorded | 19 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/gghio345 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 17:22 | 92 | no change |
| 19 Sept 2026, 16:47 | 92 | first reading |
12 posts held, back to 14 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.
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.
| Window | Rolling 30 days · latest post in window 19 September 2026 |
|---|---|
| Posts held | 12 (14 May 2026 – 19 September 2026) |
| Views total | 1,033 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 19 Sept 2026, 17:22 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.
Lifetime counters from Telegram’s own channel header, read 19 September 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.
3 reactions across 3 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 100.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 3 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 3 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 May 2026 to 19 September 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.
东莞塘厦AKA TV 出击报告 [价格]：500 [老师名字]： #塘厦 #芋圆#@xyy098 [身高体型]：微胖，可爱型 [颜值人照]：8分 [特点和绝活]：服务好，胸大 [胸部大小颜色]：感觉c+吧奶头凹陷 [鲍鱼紧度颜色]：紧 [是否有🐍和69]：都有 [配合度（百分比%）]：99 [技术（SABCDE为等级）]：s [臻选综合评价（S ABCDE为等级）]：s [缺点（无完美之人，必须要有缺点）]：有点微微胖，只不过有肉感 您的出击建议：喜欢服务无脑冲，这个价格性价比很高了，肉肉的很舒服 塘厦臻选精品老师榜： https://t.me/aramii_dlakan 东莞塘厦TV S（禁止🚫老师）： https://t.me/+o7cT_mREgHBhYzU0 塘厦总交流群：https://t.me/+iEz20gByttViNDM1 老师榜单： https://t.me/+P_u…
东莞塘厦AKA TV 出击报告 [价格]：500 [老师名字]： #塘厦 [身高体型]：162 [颜值人照]：娃娃脸 [特点和绝活]：后入 [胸部大小颜色]：粉 [鲍鱼紧度颜色]：紧 [是否有🐍和69]：有 [配合度（百分比%）]：99 [技术（SABCDE为等级）]：S [臻选综合评价（S ABCDE为等级）]：S [缺点（无完美之人，必须要有缺点）]：左右凹凸 您的出击建议： 听话，要啥可以商量，非常的Ok 塘厦臻选精品老师榜： https://t.me/aramii_dlakan 东莞塘厦TV S（禁止🚫老师）： https://t.me/+o7cT_mREgHBhYzU0 塘厦总交流群：https://t.me/+iEz20gByttViNDM1 老师榜单： https://t.me/+P_uKnodU9yo0ZmY1 TV报告群： https://t.me/+hDj06D401…
开课啦
Photo, posted without a caption
开课啦
两天后开课
今天休息一天遭不住了
下班了
❤1
满课
❤1
Channel name was changed to «芋圆»
个人兼职，自带工作室 艺名 芋圆 身高 162cm 胸围 36D 体重 50kg 本人桑拿会所专业培训，正宗莞式一条龙服务！！！ 服务内容：鸳鸯浴 裸吹 6️⃣9️⃣ 互👅 丝袜诱惑 亲咪咪 👅蛋蛋 胸推 指滑 海底捞月 电动小马达 配合度高 女友式激情爱爱 胸大屁股翘口活超好 B紧💦多 能吸会夹 床上服务骚骚服务一流 敏感体质 易高潮 慢性子有耐心不催钟 玩的开 放的开 🉑🐍 🉑6️⃣9️⃣ 课程 500一次40分钟 1000两个90分钟 外出要两次➕车费，注先收车费 不议价 诚信约课 口嗨忽扰 服务过程中出水算一次 🈲无帽🈲酒课🈲药课🈲低素质
❤1
Channel created
Showing the 12 most recent of 12 posts we hold for @gghio345. 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.
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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“芋圆” (@gghio345), 92 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/gghio345.
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.