Telegram RegisterThe public register of Telegram
Telegram profile photo for 佛山少女御姐报告集

Channel

佛山少女御姐报告集

@FSsvyjbgj

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry

16,017subscribers

+5,181 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1003656715330
TypeChannel
Username@FSsvyjbgj
Description报告模版: https://t.me/FSsvyjbgj/7 报告提交: @QST_mrlbot
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/FSsvyjbgj

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@NNnmmtlu/544822 Aug 2026, 09:49 UTC@FSsvyjbgj/1897 · this entry22 Aug 2026, 09:50 UTC0.9172 seconds
@NNnmmtlu/70914 Nov 2026, 15:53 UTC@FSsvyjbgj/2539 · this entry5 Nov 2026, 05:58 UTC0.8914 hours
@NNnmmtlu/557226 Aug 2026, 14:50 UTC@FSsvyjbgj/1947 · this entry26 Aug 2026, 15:45 UTC0.8655 minutes
@NNnmmtlu/57101 Sept 2026, 05:28 UTC@FSsvyjbgj/1999 · this entry1 Sept 2026, 07:43 UTC0.822.3 hours
@NNnmmtlu/721810 Nov 2026, 11:39 UTC@FSsvyjbgj/2587 · this entry11 Nov 2026, 04:50 UTC0.7717 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@NNnmmtlu5 (5/5 hand-verifiable sample passed)0.852.3 hours@NNnmmtlu (5–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 5 of the 5 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 378 comparable posts for this entry, running 5 August 2026 to 12 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the key clone_copy, last confirmed 13 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

9,90416,59713,250.516,0176 August 202612 November 2026
64 measurements spanning 98 days, net +5,181. 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 8,900–17,601 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
12 Nov 2026, 13:2116,017-11
10 Nov 2026, 10:5616,028-28
8 Nov 2026, 21:4616,056-58
7 Nov 2026, 10:3116,114-34
6 Nov 2026, 11:3616,148-37
5 Nov 2026, 10:0616,185-29
4 Nov 2026, 12:0616,214-34
3 Nov 2026, 14:5516,248-98
2 Nov 2026, 12:0016,346-20
1 Nov 2026, 12:2016,366-130
31 Oct 2026, 14:2716,496-101
30 Oct 2026, 15:5916,597+4,680
29 Oct 2026, 12:5711,917-60
28 Oct 2026, 15:2911,977-81
27 Oct 2026, 17:2512,058-70
26 Oct 2026, 18:4512,128-42
25 Oct 2026, 21:5512,170-63
25 Oct 2026, 00:2612,233-69
24 Oct 2026, 01:4812,302-76
23 Oct 2026, 00:1812,378first reading

Engagement

386 posts held, back to 5 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 70 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.69%
avg views ÷ 16,017 subscribers
Avg views / post
271
107 posts measured
Reaction rate
0.239%
reactions ÷ views · ER floor
Posts in window
107
of 386 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 107 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 13 November 2026
Posts held386 (5 August 2026 – 13 November 2026)
Views total28,982
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Nov 2026, 18:51 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

Links
≈2,510

Lifetime counters from Telegram’s own channel header, read 13 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

14 reactions across 12 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤14100.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 18 of the 386 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 14 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 386 most recent posts we hold, published 5 August 2026 to 13 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: 6 of 107 posts held from the last 30 days (5.61%) 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).

13 Nov 2026, 13:07 UTC44 viewsread 13 November 2026

【少御报告】https://t.me/FSsvyjhj 【老师艺名】#瑶瑶 【联系方式】@aaas5211 【所在位置】#禅城 【验证留名】卡拉 【验证时间】2026.11.8 【修车费用】700p 【颜值身材】颜值高,小妹妹的身材,小小的也很可爱 【服务内容】xcz 蛇 69 【服务态度】满分 【优点缺点】大蟒蛇,女上桩基,水娃 【推荐程度】10分 【体验细节】之前就被瑶瑶的频道吸引,挺说是个会喷水的可爱嫩妹,随去一探究竟,快到时间 遥控进入科室,瑶妹妹居然说还在打王者,我就静静看着她打完残局,初见妹妹妆容给我的感觉是比较高冷的,没想到洗完澡进入正题 异常的热情,妹妹带舌钉,口的也非常的卖力十分的舒服 ,🐍的时候会舔你的脖子和耳朵肥肠的涩情,进入后包裹感也很强,做的过程中也非常的投入,给我一种好像跟女朋友做的感觉,最后在 跟瑶瑶大战三百回合后也是顺利喷水,可惜我状态 不佳没出水,还被妹妹吐槽 哈哈哈,总之性格很好的妹子体验 …

13 Nov 2026, 13:06 UTC80 viewsread 13 November 2026

【少御报告】https://t.me/FSsvyjhj 【老师艺名】小美玲 【联系方式】@MmeiLlin 【所在位置】南海 【验证留名】冰 【验证时间】11.13 【修车费用】500 【颜值身材】白嫩 【服务内容】课表一致 【服务态度】热情 【优点缺点】嫩嫩嫩,喜欢!! 【推荐程度】10 【体验细节】 皮肤好白,挺有清纯的。有专门的情趣衣服,交了水费聊了一会,老师陪洗好仔细,服务态度很好。躺在床上老师细心的帮你口,不喊停不停,口的好有节凑感 看着大白🦵早已硬梆梆,带上套套直接开干,几个姿势轮流干,小老师的喘息声很有感觉,小穴也很紧水多,在一声声喘息中出水。有机会一定返,老师人也不错的 温柔。 ♥️温馨提示: 以上仅代表个人体验,报告仅供参考! 报告提交: @QST_mrlbot

13 Nov 2026, 13:05 UTC138 viewsread 13 November 2026

【少御报告】https://t.me/FSsvyjhj 【老师艺名】顺德🌸吖吖 【联系方式】@Shundeyaya1 【所在位置】大良 【验证留名】门南 【验证时间】2026/11/12 【修车费用】600 【颜值身材】嫩妹 【服务内容】按课表 【服务态度】很健谈,不冷场,服务很好 【优点缺点】逼紧,水多,骚,服务好 【推荐程度】可以来试试 【体验细节】约好时间直接出击。先交水费。然后和吖吖老师共浴,直接回床上实在忍不住了直接亲吻老师。老师突然强攻。直接舔咪咪,不得不说老师舌功有点厉害。从未有过的舒服感,老师还会舔你的睾丸。再一口含住已一柱擎天,毫无齿感。问老师是否可以跪着舔。老师也听话换了位置。看着老师跪着舔的爽感不得不称赞。舔的差不多回床上试了一下69,吖吖老师下体没有任何异味,舔逼爱好者哪里能放过,一阵舔,把骚麦舔的骚叫连连。前戏做的差不多了。直接带套开工。一开始男上女下。然后调整了一下节奏。让老师观音坐莲。直到老师没力气…

13 Nov 2026, 09:12 UTC480 viewsread 13 November 2026

【少御报告】https://t.me/FSsvyjhj 【老师艺名】晴儿 【联系方式】@gjjjv689 【所在位置】#禅城区 【验证留名】Z先生没有肌肉 【验证时间】11.13 【修车费用】700p 【颜值身材】真人比照片还要好看N倍! 【服务内容】课表齐全 【服务态度】热情且温柔 【优点缺点】全是优点 像明星,身材好,比照片还要漂亮、皮肤超级好很嫩,很白,性感诱人。 【推荐程度】强烈推荐 【体验细节】遥控上楼之后,一进门看到老师穿的漂漂亮亮的,比照片上还要好看N倍。明星脸,虽然长得一副御姐样,但声音超级温柔御中带甜,甜中带御。梦幻女友类型。然后就洗刷刷,边洗边欣赏老师,真的看着人都要酥了,说话温柔,讲究卫生的人然后老师穿上战袍,开始服务。口才了得,口技很好,没有齿感,像看A片一样,那个真的手感很好,大小刚好,软硬度刚好,皮肤也好嫩嫩的。一边含着老师的大球,慢慢的感觉越来越刺激,开始进入啪起来的时候,激情四射,夹紧我的…

13 Nov 2026, 08:30 UTC174 viewsread 13 November 2026

【少御报告】https://t.me/FSsvyjhj 【老师艺名】七七 【联系方式】@qiqi2006o 【所在位置】#禅城区 【验证留名】巨蟹座的饮水机 【验证时间】十一月十号 【修车费用】700 【颜值身材】极品嫩妹 有我至爱的大屁股 【服务内容】全做 【服务态度】V立古[强] 【优点缺点】可爱,皮肤滑滑,吊感十足 【推荐程度】满分推荐 【体验细节】有幸提前约到妹妹的课,提前到达目的地等待,妹妹准备好以后按指示上楼。 重点来了,进入房间后初见七七,一眼乖巧可爱的样子,同时一身精致便装,也让妹妹的好身材暴露无疑。坐下与七七拉拉家常,氛围顿时轻松不少。 主题来了,妹妹贴心陪洗,口时认真投入,传统姿势,后入,女上不停切换,过程中大蟒蛇管够,太赞了。细节描述太多没有神秘感了,只有亲身体验才能体会,建议各位兄弟自行下场😊 总结下来就是三个字-棒棒哒 ♥️温馨提示: 以上仅代表个人体验,报告仅供参考! 报告提交: @QST_mrlb…

13 Nov 2026, 08:19 UTC51 viewsread 13 November 2026

【少御报告】https://t.me/FSsvyjhj 【老师艺名】#艾拉 【联系方式】@GD_aila 【所在位置】#金沙洲 【验证留名】螺蛳粉薯条 【验证时间】11.10 【修车费用】P 【颜值身材】人照八分 【服务内容】全套服务 【服务态度】很配合,热情 【优点缺点】服务认真耐心,不催 【推荐程度】90分 【体验细节】提前和老师约好,按照指引来到教室,见面第一眼,就知道是个知心大姐姐 果断交水费,老师拿拖鞋一起去洗澡 老师前后面洗的很认真,结束了,躺在床上,老师开始调情,我享受 先是老师用她的熊在我身上蹭过去蹭过来,然后一边亲我熊一边指滑身体 (我比较怕痒)然后老师下去口我二弟,老师的口技了的 感觉就像把我的二弟当个棒棒糖吃一样,很刺激 受不了了戴套开干 老师先女上慢慢蹭就是不进去本狼受不了了果断进入,进入的一瞬间感觉好烫好紧,做了两下 换成传统姿势,一边爱爱一边吃着老师的熊,老师全程像个八爪鱼一样抱着我,还各种骚话连篇 …

13 Nov 2026, 08:04 UTC295 views1 reactionsread 13 November 2026

【少御报告】https://t.me/FSsvyjhj 【老师艺名】#芯怡 【联系方式】@xyiyiyi12 【所在位置】#禅城 【验证留名】油油大人 【验证时间】11.9 【修车费用】800p 【颜值身材】颜值身材顶呱呱 【服务内容】xcz,蛇 【服务态度】9分 【优点缺点】大长腿 颜值太顶了,自己去体会 【推荐程度】一百昏 【体验细节】一见面就觉得这颜值是在线的,完全不让人有距离感。老师主动帮我洗得很仔细,洗完直接拉着我上床,开始服务后,老师舌头真的特别灵,先是轻轻舔着奶头,那种酥酥麻麻的感觉直接把人搞得不行,老弟瞬间就硬得发疼。口活也很会,尤其是吸蛋蛋那一下,刺激得我差点直接缴械。实在忍不住就带套开干了,正面看着她的时候居然有那么一丢丢的罪恶感,摸着老师立挺挺的奶传教士,老师下面很紧调整第二次才进入,窝趣直接被秒,好失落,但好舒服,可能是好久没近女色原因吧,洗完澡又跟老师闲聊了一会儿,感觉整个人都放松下来了,收拾东西下楼的…

❤1

13 Nov 2026, 07:41 UTC27 viewsread 13 November 2026

【少御报告】https://t.me/FSsvyjhj 【老师艺名】杏子 【联系方式】@xinzi535 【所在位置】金沙洲 【验证留名】忙碌先生 【验证时间】11月头头 【修车费用】700 【颜值身材】天然C,手感很柔软。身材匀称 【服务内容】三件套、舌吻、制服 【服务态度】热情 【优点缺点】保养不错颜值耐看,健谈很热情主动调情,水多较紧爱爱主动反馈很好 【推荐程度】88 【体验细节】属于颜值较好的御姐,态度好热情健谈,服务较多认真细致,身材属于前凸后翘胸大屁股有肉,还有一大堆制服可以选择搭配身材更加分,皮肤白手感光滑,胸C乳头小粉褐色,馒头粉褐色毛量正常,水多很紧爱爱敏感水多反馈好,总体属于颜值身材服务都不错的六边形御姐 ♥️温馨提示: 以上仅代表个人体验,报告仅供参考! 报告提交: @QST_mrlbot

12 Nov 2026, 11:11 UTC236 viewsread 13 November 2026

【少御报告】https://t.me/FSsvyjhj 【老师艺名】:芷一 【联系方式】 @zhiyiAA0 【所在位置】:金沙洲 【验证留名】:仔仔最爱吃鲍鱼 【验证时间】:2026年11月11日 【修车费用】:P 【颜值身材】 人照大概8.8 【服务内容】 课表都有 【服务态度】 热情 【优点缺点】 优点:嫩、听话配合、乖乖女、可拍小视频 缺点:金沙洲塞车,建议早啲出发 【推荐程度】 9分 【体验细节】 今日金沙洲天气唔算差,但系塞车严重,早咗少少出门先到得切。提前一日约咗芷一头课,跟住指引顺利入到去。 进门妹妹笑住打招呼,仲递咗樽水,好热情。坐低倾咗几句就除衫一齐冲凉。冲完互相揽住锡,佢开始服务,先舔胸再口,吞吐好快,刺激到差点交货。 之后反过来服务佢,挑逗个乳头,伸手摸下去已经湿晒,阴蒂都露咗出嚟。毛少,直接用舌头对付,佢反应好大,呻到停唔到。弄咗几分钟自己都顶唔住,戴套正面插进去,包裹感好强,仲会夹,夹到好爽。 继…

12 Nov 2026, 09:00 UTC541 viewsread 13 November 2026

【少御报告】https://t.me/FSsvyjhj 【老师艺名】#贝瑶 【联系方式】@beiyao1688 【所在位置】禅城 【验证留名】沙二Go学长 【验证时间】11月10日 【修车费用】P500 【颜值身材】御姐。够骚,奶大 【服务内容】洗吹做、69、舌吻、毒龙..课表齐 【服务态度】超级热情 【优点缺点】情绪价值拉满,主动 【推荐程度】8.9 【体验细节】遥控进门,第一眼看到老师样子是我喜欢的御姐型,身材非常好,见面直接交了水费,然后老师开始帮忙洗澡,洗的很认真,一点也不含糊,而且老师身体非常软滑。接着就进行服务了,先躺着,课表里的服务都会有,是真的都会有,之前有一些课表有但是到了后就不一样了,什么胸滑 69啥的都有,全程就享受就可以了,而且每项服务时长都是满中满,还有毒龙,说实话之前没遇到过服务这么好的老师,然后就是正面,各种吹箫技巧老师都会,而后开始风云迭起,各种姿势,都非常配合,非常有感觉,我换了几个姿势,老师也…

12 Nov 2026, 08:39 UTC99 viewsread 13 November 2026

【少御报告】https://t.me/FSsvyjhj 【老师艺名】#瑶瑶 【联系方式】@aaas5211 【所在位置】#佛山禅城 【验证留名】我有一只哒哒ya 【验证时间】11.7号 【修车费用】700 【颜值身材】小只马,可爱 【服务内容】xcz+大蟒蛇🐍 【服务态度】五星好评 【优点缺点】反差妹妹、真实、紧致 【推荐程度】10 【体验细节】观察瑶瑶良久,照片和穿衣风格是我喜欢的类型,好评不断,并联系约课,运气好,时间和下班时间无缝衔接!没想到牛马被召唤导致最终迟到些许,瑶瑶也没说什么!根据指引到达教室,见到瑶瑶,果然没失望,真人比照片要好看太多,尤其是小脸蛋,可爱又有点飒的感觉,毫不犹豫付完水费,一起陪洗,擦水上床开始享受服务,很听指挥,让做什么就做什么,奈何状态不佳,很快的就成为瑶瑶的手下败将!过程 非常的配合、给力!完事后,也没催,还和瑶瑶聊了一会天才走,总体来说很愉快的一次体验! ♥️温馨提示: 以上仅代表个人体验…

12 Nov 2026, 08:27 UTC≈1,020 viewsread 13 November 2026

【少御报告】https://t.me/FSsvyjhj 【老师艺名】晴儿 【联系方式】@gjjjv689 【所在位置】#禅城区 【验证留名】挖掘野生美少女 【验证时间】11.10 【修车费用】700p 【颜值身材】邻家小姐姐,皮白貌美 身材劲爆 【服务内容】课表齐全 【服务态度】情绪价值挺高的 推荐! 而且老师挺能聊的 【优点缺点】爱爱反馈真实,大蟒蛇 【推荐程度】99.99 【体验细节】已经好一段时间没有出击了,压抑许久,终于在今天爆发! 果断联系晴儿,跟晴儿约好时间,出发到课室,在晴儿引导下来到课室,课室温馨且干净,看见本人那刻已经知道不虚此行了,坐在沙发闲聊片刻,二弟已按捺不住,立马沐浴快快进入正题,简单冲洗后舒服地躺下,感受着晴儿的小嘴与二弟强烈地互动,让欲火进一步高涨。从女上开始,能感受到小穴紧紧地与二弟包裏着,强烈的视觉与触觉冲击让人很想缴械,只好轻缓节奏,能感受到晴儿也喜欢温柔的撞击,直到两人微微出汗,才全情投入,…

Showing the 12 most recent of 386 posts we hold for @FSsvyjbgj. 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 1 post on @FSsvyjbgj 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
24 August 2026
Most recent seen missing
24 August 2026
Median time before seen missing
12 hours
Seen missing in the last 30 days
0

Forward network

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 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.

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

“佛山少女御姐报告集” (@FSsvyjbgj), 16,017 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/FSsvyjbgj.

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.