位置:南城 艺名:安安/慕南 一节课:600 两节课:1100 #🉑双飞 私聊: @hjjjhhjjbj 频道: https://t.me/Jjkkhhhkjhh 双向:@ananmuna_bot
❤6

Channel
@ZGG004
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
23,679subscribers
-2,675 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002240552865 |
|---|---|
| Type | Channel |
| Username | @ZGG004 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 3 September 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 3 September 2026 |
| On Telegram | t.me/ZGG004 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Sept 2026, 17:36 | 23,679 | -350 |
| 2 Sept 2026, 13:24 | 24,029 | -362 |
| 1 Sept 2026, 15:16 | 24,391 | -249 |
| 31 Aug 2026, 17:02 | 24,640 | -243 |
| 30 Aug 2026, 15:07 | 24,883 | -276 |
| 29 Aug 2026, 16:24 | 25,159 | -330 |
| 28 Aug 2026, 17:17 | 25,489 | -25 |
| 27 Aug 2026, 19:07 | 25,514 | -10 |
| 26 Aug 2026, 18:32 | 25,524 | -33 |
| 25 Aug 2026, 20:13 | 25,557 | -34 |
| 24 Aug 2026, 23:48 | 25,591 | -47 |
| 23 Aug 2026, 13:14 | 25,638 | -51 |
| 22 Aug 2026, 03:08 | 25,689 | -39 |
| 20 Aug 2026, 19:23 | 25,728 | -42 |
| 19 Aug 2026, 17:57 | 25,770 | -8 |
| 18 Aug 2026, 19:02 | 25,778 | -51 |
| 17 Aug 2026, 19:23 | 25,829 | -86 |
| 16 Aug 2026, 14:06 | 25,915 | -96 |
| 14 Aug 2026, 19:44 | 26,011 | -29 |
| 13 Aug 2026, 07:57 | 26,040 | first reading |
9 posts held, back to 20 July 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 58 pages 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. It is computed over the 3 of 5 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 26 August 2026 |
|---|---|
| Posts held | 9 (20 July 2026 – 26 August 2026) |
| Views total | 9,690 |
| Reactions total | 13 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 10:42 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.
Measured directly from 3 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.
27 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 77.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 21 | 77.8% | |
| 👍 | 6 | 22.2% |
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 9 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 27 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 20 July 2026 to 26 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.
位置:南城 艺名:安安/慕南 一节课:600 两节课:1100 #🉑双飞 私聊: @hjjjhhjjbj 频道: https://t.me/Jjkkhhhkjhh 双向:@ananmuna_bot
❤6
纯狼友交流群:https://t.me/+9wECdwpjB6s0NGM1 东莞修车大群:https://t.me/ZGG003
惠州石湾近东莞!新店开业,独立卫浴冲凉房帮洗澡!带水床🛏️躺着水床帮洗澡 直接在水床上开启服务,刺激不可言说,欢迎品鉴 本人亲自在店接待安排!消费透明服务全程跟踪售后处理!专业靠谱! 【会所定位】主店石湾水床 #惠城 #石湾水床 ☞ 惠莞极品 94服务 性感妩媚、颜值在线 私密环境、顶级服务 本会所承诺所有技师都是经过严格筛选把关,尽其所能,让每一位客户玩的开心,玩的尽兴,玩的安全,每天百味佳丽任君挑选,全心全意打造惠莞最强大的会所 特色:全裸.任选! 争取做到你躺着一动不动,小妹妹全自动,保证让您满意,100%让你够有所值,过来提前发信息,预约时间,中午11点~凌晨6点。非诚勿扰,全新服务,大型免费停车,免费过夜。有服装要求的现场选特色服装,角色扮演,欲擒故纵小主专宠小奶狗,情趣猫女郎调教角色扮演师,扑倒征服,专治不服,手撕丝袜,亲🦶,👅足足交,刺激缸顶。 398 半裸☞熊手足任选出一次 538…
❤7
Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_8467257083
📱📱📱📱📱📱📱📱📱📱 东莞深圳😄高端😄高颜值海选😄全裸4T🤑 东莞深圳按摩/4推/海选/推油/4T #东莞 #东莞会所 #松山湖 👇 👇 👇 👇 👇 大朗 厚街 南城 塘厦 樟木头 👇 👇 👇 👇 👇 长安 寮步 东城 虎门 横沥 石排 #深圳#深圳全区会所# 🌝🌝🌝🍎🍎🍎🍎🍎🌝🌝🌝 预约价格:398 498 528 全程全裸 全程骚柔慢 🐻波推+ 👃鼻吸慢指💅划哈气👅 👂耳 魔音骚叫+浑身酥麻流动 +👅尖漫游每一寸肌肤(全程蛇🐍尖漫游+专攻小哥哥敏感区,免费提供:丝足调情 + 果冻舔🥚➕果冻🐲 🐻推,👅棍棍,(五分钟以上)🍑推,👋推,🦵推+慢tiao ,💃小 姐姐 配合度高. 有特殊癖好可用🦶/🐻/脚关节出💧。 列腺龙筋保健手法让您一出一收紧,排除精管内剩余积液,身心愉悦,欢迎小哥哥前来品鉴及调教 ,主打小姐姐配合度 开放式服务,我们的小姐姐…
位置:南城 艺名:招财 一节课:600 两节课:1200 私聊: @Aas12333 频道: https://t.me/hdbdjsjsbau 双向:@sxjqr7262bot
❤5
位置:虎门 艺名:可可 一节课:380 两节课:680 私聊: @keke095 频道: https://t.me/kekeke8202 双向机器人🤖@keke8820bot
❤1
没上榜,没见到人就索要定金的都是骗子,被骗不要叫 我厌蠢
👍6
位置:大朗 艺名:涵涵 一节课:600 两节课:1200 私聊: @hanhan18899 频道: https://t.me/GHanHan8 双向:@Han188_bot
❤2
Showing the 9 most recent of 9 posts we hold for @ZGG004. 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.
@ZGG004 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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.
@ZGG004 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 3 September 2026 — this entry's latest reading, not the date you are reading this.
“东莞修车TV公开榜” (@ZGG004), 23,679 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/ZGG004.
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.