Telegram 中文圈搜索引擎,积木 JIMU 帮你查询任何您想要的群组、频道(不论公开与私密) 🧩 积木:@jimu · @jimux · @jimuxx 👉 所有入口都能助力提升排名🚀

Channel
福田顶美的生活日记
@sghsjsksmd6687
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry
6,147subscribers
+2,732 since we began measuring on 29 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1003710700035 |
|---|---|
| Type | Channel |
| Username | @sghsjsksmd6687 |
| Created | 29 August 2026 — measured — dated from the channel’s first post |
| First recorded | 29 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/sghsjsksmd6687 |
Topic
Adult — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 15 September 2026 and assigned it the closest of 31 fixed categories, at 85% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 17:44 | 6,147 | -256 |
| 3 Nov 2026, 13:01 | 6,403 | -367 |
| 31 Oct 2026, 09:21 | 6,770 | -457 |
| 28 Oct 2026, 17:17 | 7,227 | -654 |
| 25 Oct 2026, 20:05 | 7,881 | +171 |
| 22 Oct 2026, 18:07 | 7,710 | +120 |
| 19 Oct 2026, 12:50 | 7,590 | -191 |
| 16 Oct 2026, 07:27 | 7,781 | -500 |
| 13 Oct 2026, 05:28 | 8,281 | +2,733 |
| 6 Oct 2026, 22:36 | 5,548 | -235 |
| 29 Sept 2026, 15:39 | 5,783 | +1,131 |
| 15 Sept 2026, 18:59 | 4,652 | +501 |
| 11 Sept 2026, 19:39 | 4,151 | -186 |
| 7 Sept 2026, 11:56 | 4,337 | -14 |
| 2 Sept 2026, 07:24 | 4,351 | +953 |
| 30 Aug 2026, 04:16 | 3,398 | -17 |
| 29 Aug 2026, 19:30 | 3,415 | first reading |
Engagement
27 posts held, back to 29 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 7 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 13.7%
- avg views ÷ 6,147 subscribers
- Avg views / post
- 840
- 17 posts measured
- Reaction rate
- 0.089%
- reactions ÷ views · ER floor
- Posts in window
- 19
- of 27 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 2 of 17 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 4 November 2026 |
|---|---|
| Posts held | 27 (29 August 2026 – 4 November 2026) |
| Views total | 14,275 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Nov 2026, 11:09 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.
Reaction mix
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1 | 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 2 of the 27 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 27 most recent posts we hold, published 29 August 2026 to 4 November 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
Telegram’s own ‘edited’ marker: 0 of 19 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
福田顶美的生活日记 pinned a photo
老家 真好清静 怀念小时候🥰🥰🥰
👍1
宝宝们 回老家一趟家里有点事。 回来了联系哟 回来了我会提前说的 🥰🥰
Telegram 中文圈搜索引擎,积木 JIMU 帮你查询任何您想要的群组、频道(不论公开与私密) 🧩 积木:@jimu · @jimux · @jimuxx 👉 所有入口都能助力提升排名🚀
集团每日五折工兵劵,更多现金大奖期待您的参与 深圳集团狼友交流群组:https://t.me/+T_cG2VyxBB8xYzU1 深圳集团老师公开榜: https://t.me/ShenZhen_68 深圳集团老师广告群: https://t.me/Shenzokba 深圳集团老师报告参考: https://t.me/yeshanghai96 ‼️📢投诉上榜建议: @bbca12
Telegram 中文圈搜索引擎,积木 JIMU 帮你查询任何您想要的群组、频道(不论公开与私密) 🧩 积木:@jimu · @jimux · @jimuxx 👉 所有入口都能助力提升排名🚀
来大姨妈了 宝宝们最近先休息了 🤨 🥰🥰🥰🥰🥰🥰
15:00 营业要的预约有头客 还在哟🥰🥰🥰🥰先到先得
福田顶美的生活日记 pinned Deleted message
【时间】:2026-10-23 【老师】:椰子 【留名】:穆 【评价】:👍 好评 【人照】:10 【颜值】:9 【身材】:9 【服务】:8.5 【态度】:9 【环境】:8.5 【综合】:9 【过程】:妹子身上的香气如其名,淡淡的椰子香气,蛮好闻的 养了好几天身子,感觉能干翻一头牛,昨夜吃完小艺意犹未尽,今天还得喝个椰子才能满足😌 依旧福田知名景点了,妹妹亲自下楼接,刚开电梯门就认出来是椰子,人照还是蛮一致的 身材:奶子很大,是那种宽广的丰满,一只手抓不过来,好久没吃过这么大的奶子了,上次吃我记得还是上周,一日不操真的如隔三秋啊 Do的过程:丰满小嫩妹一枚,下面毛发不多,bb好舔无异味,且又是很紧致的逼,大力抽插的时候mm会使劲把你往里面吸,新奇又刺激的屌感,越干越上头,套套都冒泡了,最后一手抓着妹子的巨乳一手按着腰侧冲刺,很顺畅的释放,推荐推荐;结束后聊天发现妹子进了很多群,一个月近w营销费用…给妹子科普下深圳集团,顺便劝劝小女…
#芳华报告 老师名字: #椰子福田36C 学生留名: # 云飞青 联系方式: @yzyz52 时间: 26.10.23 地址:福田 价格:1080元1p减优惠券 上课过程: 老师下来接我的,说实话其实没有多大期待,不过电梯开门的一瞬间,我就知道从广州到深圳跑过来没错!老师穿着白衣服白裤子好看,然后带我上去进门,进门环境也不错,敞亮,和老师刷了个牙,接下来就是经典的洗吹做还有舌吻,老师吹完之后还流水了,水嫩,可以。 老师也很好不是什么事逼,也有耐心,现实中人感觉比照片好看,颜值和身材还有态度都还不错,可以推荐,胸奴强烈推荐,做的时候胸前一晃一晃的,特别是侧入的时候,你才会领略什么叫做侧成峰,胸奴肯定会喜欢的,可以冲。 👫加入芳华群聊 🏆芳华频道 📖芳华报告 ⬆️恰同学少年 唯一上榜: @fanghua88_bot 报告投稿: @fanghuabgbot
Showing the 12 most recent of 27 posts we hold for @sghsjsksmd6687. 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.
Posts recorded as deleted after publishing
We recorded 4 posts on @sghsjsksmd6687 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
- First seen missing
- 4 November 2026
- Most recent seen missing
- 4 November 2026
- Median time before seen missing
- 4 days
- Seen missing in the last 30 days
- 4
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 5 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.
@jimu · 100,4506 posts深圳东莞公开榜
@ShenZhen_68 · 23,2152 posts春朝报告
@Chunzhaobaogao · 3,1711 post春朝频道
@ChunZhaoChannel · 38,0501 post又见芳华
@FanghuaB · 32,6661 post芳华报告
@fanghuagb · 3,2161 post恰同学少年
@fanghuaR · 15,1981 post深圳东莞老师开课广告群
@Shenzokba · 12,6311 post深圳东莞集团报告(仅供参考)
@yeshanghai96 · 6,5581 post
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“福田顶美的生活日记” (@sghsjsksmd6687), 6,147 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/sghsjsksmd6687.
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.