Telegram RegisterThe public register of Telegram
Telegram profile photo for 佛山18小萝莉抓龙筋

Channel

佛山18小萝莉抓龙筋

@ahehh555

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

1,285subscribers

+24 since we began measuring on 25 August 2026

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

Register entry

Telegram ID-1004309943704
TypeChannel
Username@ahehh555
CreatedBetween 1 June 2026 and 7 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded25 August 2026
Last confirmed live3 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 3 September 2026
On Telegramt.me/ahehh555

Growth

1,2611,2901,275.525 August 2026 — 1,261 subscribers26 August 2026 — 1,271 subscribers28 August 2026 — 1,284 subscribers31 August 2026 — 1,290 subscribers3 September 2026 — 1,285 subscribers1,28525 August 20263 September 2026
5 measurements spanning 9 days, net +24. 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,257–1,294 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Sept 2026, 13:011,285-5
31 Aug 2026, 12:151,290+6
28 Aug 2026, 16:221,284+13
26 Aug 2026, 00:071,271+10
25 Aug 2026, 10:001,261first reading

Engagement

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

ERR · 30 days
74.9%
avg views ÷ 1,285 subscribers
Avg views / post
963
9 posts measured
Reaction rate
0.071%
reactions ÷ views · ER floor
Posts in window
11
of 11 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. It is computed over the 5 of 9 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 25 August 2026
Posts held11 (7 August 202625 August 2026)
Views total8,665
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken25 Aug 2026, 10:00 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

Video runtime
57s
Average length
14s

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.

Reaction mix

4 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
375.0%
🥰125.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 5 of the 11 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 7 August 2026 to 25 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.

Recent posts

25 Aug 2026, 09:20 UTC28 viewsread 25 August 2026
Forwarded from @GZFYLBPhoto

艺名:小萝莉 地区:#南海 标签:嫩 泰式抓龙筋 消费: A套餐598 B套餐798 C套餐998 红人榜 视频已验证 联系:@AA52568 频道:https://t.me/ahehh555

25 Aug 2026, 08:38 UTC82 views0 reactionsread 25 August 2026
Photo

🎰 南海桂城 小萝莉抓龙筋的半价优惠 📮 参与条件: 🎫 加入-佛山18小萝莉抓龙筋 🎫 加入-广州凤吟修车茶馆备用群 🎫 加入-广州凤吟修车娱乐资源私密1 🎫 加入-广州凤吟修车茶馆 └ 🎟️ 发言数大于 38 条 🎫 加入-广州凤吟修车娱乐资源 🎁 奖品内容: 💰️ A套餐半价券 × 1 ⚠️ 抽奖说明: 半价免定,中奖者主动联系老师,不得转手转卖,兑奖必须写报告,五天内有效,逾期回收至兑换区。 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年08月29日 20时00分00秒

18 Aug 2026, 02:01 UTC≈1,100 views0 reactionsread 25 August 2026

#联邦报告 <https://t.me/gzafua> 【出击留名】: 匿名 【出击时间】:2026-8中 【老师艺名】:#小萝莉 【联系方式】:@AA52568 【开课位置】:#桂城 【上课费用】:A套餐 【颜值身材】:颜值如图一模一样,身材如图一模一样。真人是真萝莉。 【身高体重】:看着160左右,感觉42kg。 【胸杯紧度】: B 紧度不详 【老师类型】:#嫩妹 【服务种类】:课表自己看 【情绪态度】:主动、有礼貌、夹子音、愉悦 【优点缺点】:优点:顶级萝莉可爱无比,按得认真规范。是萝莉按摩第一人。人畜无害,但是异常认真专注。 缺点: 可惜是龙筋咯。 【自由描述】:龙筋一直想去,看到萝莉龙筋去看看。扫雷探密,准时到达,准时开门。真人如图,一模一样0差距。夹子音很有礼貌,见到客厅还有另外一个老师上榜有的。老师穿萝莉,热情礼貌。洗澡要自己洗。洗好自己躺下,老师开始工作,非常认真非常努力,还挺专业。应该是萝莉届最会按摩的,

10 Aug 2026, 08:05 UTC≈1,590 views2 reactionsread 25 August 2026
Photo

💐💐💐开奖了💐💐💐 【府上 小萝莉 抽奖活动】开奖了 本期总参与人数:176 嫩妹币加成数:37 1、DanielWu(消息数32 加成数0)获得:半价/p 2、继续努力(消息数31 加成数0)获得:100优惠 3、joranss(消息数114 加成数1)获得:100优惠 4、在春天游泳鸭(重生版)(消息数31 加成数0)获得:100优惠 兑奖请联系 @AA52568 谨祝中奖用户大吉大利万事如意 更多资讯请关注

2

8 Aug 2026, 12:05 UTC≈1,520 views1 reactionsread 25 August 2026
Video

如果我拿出这套战袍,哥哥又该如何面对?

🥰1

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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.

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

“佛山18小萝莉抓龙筋” (@ahehh555), 1,285 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/ahehh555.

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.