今天休息了,明天再见。

Channel
福田新人有有
@gh66889
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
996subscribers
+72 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004280688541 |
|---|---|
| Type | Channel |
| Username | @gh66889 |
| Created | Between 1 May 2026 and 29 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/gh66889 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 05:37 | 996 | -12 |
| 2 Sept 2026, 19:05 | 1,008 | -9 |
| 30 Aug 2026, 18:03 | 1,017 | +40 |
| 22 Aug 2026, 18:44 | 977 | +52 |
| 14 Aug 2026, 08:18 | 925 | +1 |
| 13 Aug 2026, 20:19 | 924 | first reading |
Engagement
20 posts held, back to 29 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 13 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
6 reactions across 4 posts, in 4 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 💩 | 2 | 33.3% | |
| 🤮 | 2 | 33.3% | |
| ❤ | 1 | 16.7% | |
| 👎 | 1 | 16.7% |
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 4 of the 20 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 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 29 July 2026 to 13 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
今天天气有风.没那么蒙热了。有人来么。今天暂时全空
下午好.🈶🈶🈶🈶🈳
今天休息了。。
今天开始上班了。暂时还是一天三个有缘人。有缘聚!
今天开始休假了,我的消息就不一一回复了,等假后回来,再见。大概8天
今天够了 休息了。改天见
今天周日休息了哈。可以约明天三位。
报告频道 https://t.me/+yq4wThY62nBhZmYx 置顶老师体验报告 #福田有有 出击时间:7月15日 出击课程:pp 出击体验:老师人很温柔,身材和皮肤都比较好,下面也很紧。 惊喜的是的 pp 中间有精油按摩,身心放松,整体体验佳,下次还来. 私聊老师: @gh998866 BBW高性价比聊天群: @bbwtalk002
休息了 。明天见。
今天休息了。。明天见
报告频道 https://t.me/+yq4wThY62nBhZmYx 置顶老师体验报告 #福田有有 出击留名:#探花Mi 出击时间:7月31日 出击课程:500p(目前优惠价) 出击体验:妹子软软糯糯的声音好听,服务真的很好,户型紧致,口活耐心,态度极好,完全不催,体验极好,以后必反(老师一天只接三个,注意预约)。 背景:朋友推荐说女友感爆棚,极致服务体验,还说老师可能近期想换课室,怕约不到,于是趁着昨天下雨,有点空闲,赶紧约起。 前:路上有有就温柔的提示今天我是最后一个,不要着急,慢慢开车。到楼下停好车,让有有给了入户邀请码 果断上楼,进去发现有有穿着黑色紧身衣,黑色热裤,眼彩淡妆,比照片好看,果断交水费洗澡。老师态度贼好,很快脱光一起洗,助浴过程用mimi在身上蹭,蹭的我小兄弟高昂着头。 递浴巾,帮着擦干,纯纯全自动。双方洗完老师换上了黑色战斗服。 中:👅了胸然后往下到了我兄弟。口活很好,果断选择69,仔细欣赏有有老师粉嫩…
❤1
Showing the 12 most recent of 20 posts we hold for @gh66889. 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 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.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“福田新人有有” (@gh66889), 996 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/gh66889.
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.