Telegram RegisterThe public register of Telegram
Telegram profile photo for 甜甜🫧岛

Channel

甜甜🫧岛

@aguoguocq

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

2,537subscribers

+0 since we began measuring on 6 October 2026

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

Register entry

Telegram ID-1003992337176
TypeChannel
Username@aguoguocq
Description思甜 无需多言! 定课: @ggcq131314 双向: @guoguo68Bot
CreatedBetween 1 April 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 October 2026
Last confirmed live7 October 2026
Measurements held2
On Telegramt.me/aguoguocq

Growth

2,5376 Oct 2026, 23:47 — 2,537 subscribers7 Oct 2026, 00:22 — 2,537 subscribers6 Oct 2026, 23:477 Oct 2026, 00:22
2 measurements taken within a single day. 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 2,534–2,540 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Oct 2026, 00:222,537no change
6 Oct 2026, 23:472,537first reading

Engagement

20 posts held, back to 31 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.

ERR · 30 days
89.5%
avg views ÷ 2,537 subscribers
Avg views / post
2,270
8 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
8
of 20 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 28 September 2026
Posts held20 (31 August 2026 – 28 September 2026)
Views total18,160
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Oct 2026, 00: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.

What this channel posts

Photos
30
Videos
15
Links
19

Lifetime counters from Telegram’s own channel header, read 7 October 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
23s
Average length
12s

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

26 Sept 2026, 14:52 UTC≈1,690 viewsread 7 October 2026

最近发烧休息两天忘记发公告了不好意思各位哥哥🌹

22 Sept 2026, 05:20 UTC≈2,790 viewsread 7 October 2026

今天发烧了一直没退休息一天哦,一会儿要去打针🐭

22 Sept 2026, 04:27 UTC≈2,670 viewsread 7 October 2026

【嫩妹社】 @chongqingnenmei1 【老师艺名】思甜 【车 牌】@ggcq131314 【留 名】@Max_wellperformance 【水 费】11pp 【硬 件】8(依然是精致面容,但是我个人还是更喜欢素颜的她) 【服 务】10(依然是我的最爱) 【态 度】10(好到爆) 【体验细节】 快到约定时间了,一直没回复我,以为要被水了,还有10分钟不到的时候回我了,吓死我了…进门还是熟悉的她,抱住。还是那些熟悉的动作,但是每次都是新鲜的她。我会珍惜每次和她在一起的时光。 ♥️温馨提示: 以上仅代表个人体验,报告仅供参考!

20 Sept 2026, 06:01 UTC≈2,480 viewsread 7 October 2026
Video

顶级劳模思甜开课啦需要预定的哥哥可以开始预定21到25得课了奥🌹

7 Sept 2026, 06:29 UTC≈3,630 viewsread 7 October 2026

先休息来姨妈了今天定课的别出发了奥🌹

7 Sept 2026, 06:28 UTC≈3,610 viewsread 7 October 2026

【嫩妹社】 @chongqingnenmei1 【老师艺名】思甜 【车 牌】@ggcq131314 【留 名】@Max_wellperformance 【水 费】11pp 【硬 件】8(今天是素颜的她,第一次见素颜的她,特别有感觉,加分) 【服 务】10(依然到位) 【态 度】10(好到爆) 【体验细节】 进门发现这次的房间环境比之前的好很多。地是软的,房间里灯光也很温馨明亮,还有大大的落地镜。她今天是完全素颜,没睡醒且时不时打哈欠的她,我格外喜欢…交米。在沙发上搂着她,亲吻着她的小脸蛋,那种感觉很奇妙。寒暄一阵后,我们脱衣洗澡,我一直盯着素颜的她,想了很多…流程不再描述了,和之前差不多,这次出了一🔥后,感觉我整个人被抽空了一样…我们在沙发上坐了好一会,我感觉都没缓过来,和她说就这样吧,我们直接去洗洗就好。结语:我会好好珍惜每一次和她在…

6 Sept 2026, 12:20 UTC≈2,940 viewsread 7 October 2026

涪陵 渝中 大渡口 江北 沙坪坝 九龙坡 南岸 北碚 渝北 巴南 江津 合川 永川 南川 万州 大足 璧山 铜梁荣昌綦江长寿开州梁平奉节云阳巫山大多区县都有资源 https://t.me/+Yk4qE5sQnmJmNTBl

Showing the 12 most recent of 20 posts we hold for @aguoguocq. 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 2 registered channels — 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.

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

“甜甜🫧岛” (@aguoguocq), 2,537 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/aguoguocq.

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.