Telegram RegisterThe public register of Telegram
Telegram profile photo for 苏州桃花坞报告

Channel

苏州桃花坞报告

@thwbaogao

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

48,833subscribers

+32,862 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002840806474
TypeChannel
Username@thwbaogao
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/thwbaogao

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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 2 other registered channels. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@THWLSB/643712 Aug 2026, 15:10 UTC@thwbaogao/5220 · this entry12 Aug 2026, 15:10 UTC1.00under a minute
@thwbaogao/5229 · this entry12 Aug 2026, 16:06 UTC@THWLSB/644813 Aug 2026, 09:58 UTC1.0018 hours
@THWLSB/645014 Aug 2026, 08:54 UTC@thwbaogao/5248 · this entry14 Aug 2026, 08:54 UTC1.00under a minute
@THWLSB/646218 Aug 2026, 12:35 UTC@thwbaogao/5304 · this entry18 Aug 2026, 12:35 UTC1.00under a minute
@THWLSB/647422 Aug 2026, 13:06 UTC@thwbaogao/5363 · this entry22 Aug 2026, 13:06 UTC1.00under a minute
@thwbaogao/5406 · this entry27 Aug 2026, 05:18 UTC@THWLSB/649428 Aug 2026, 11:05 UTC1.0030 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
@THWLSB7 (7/7 hand-verifiable sample passed)1.00under a minute@THWLSB (4–3)
@thwxqpd6 (6/6 hand-verifiable sample passed)1.00under a minute@thwxqpd (5–1)

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. 9 of the 9 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 523 comparable posts for this entry, running 6 August 2026 to 14 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).

Of the group of 3 channels, the one whose matching posts we hold earliest is @THWLSB. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual, last confirmed 15 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.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

12,11049,12730,618.548,8337 August 202613 November 2026
64 measurements spanning 97 days, net +32,862. 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 6,557–54,680 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
13 Nov 2026, 03:0748,833-40
10 Nov 2026, 20:1048,873+6
9 Nov 2026, 06:3748,867-4
7 Nov 2026, 21:4648,871-17
6 Nov 2026, 23:0048,888-4
5 Nov 2026, 23:2548,892-2
5 Nov 2026, 02:0748,894+1
4 Nov 2026, 00:3848,893-17
3 Nov 2026, 03:5148,910+3
2 Nov 2026, 01:3148,907-22
31 Oct 2026, 23:5848,929-19
31 Oct 2026, 02:0048,948-99
30 Oct 2026, 00:4649,047+3
29 Oct 2026, 04:0949,044-39
28 Oct 2026, 00:4649,083+21
26 Oct 2026, 23:4849,062+47
26 Oct 2026, 02:4149,015-40
25 Oct 2026, 04:1649,055-14
24 Oct 2026, 06:3549,069-58
23 Oct 2026, 04:2649,127first reading

Engagement

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

ERR · 30 days
2.49%
avg views ÷ 48,833 subscribers
Avg views / post
1,220
299 posts measured
Reaction rate
0.059%
reactions ÷ views · ER floor
Posts in window
299
of 573 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 54 of 299 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 15 November 2026
Posts held573 (6 August 2026 – 15 November 2026)
Views total363,359
Reactions total44
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Nov 2026, 12:23 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
≈4,720
Videos
≈81
Links
≈1,100

Lifetime counters from Telegram’s own channel header, read 15 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.

Video runtime
1m 10s
Average length
12s

Measured directly from 6 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

64 reactions across 54 posts, in 5 distinct kinds. The most used accounts for 93.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤6093.8%
🎄11.56%
👍11.56%
💩11.56%
😴11.56%

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 77 of the 573 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 64 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 573 most recent posts we hold, published 6 August 2026 to 15 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: 7 of 299 posts held from the last 30 days (2.34%) 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).

15 Nov 2026, 11:49 UTC≈1,060 viewsread 15 November 2026
Photo

【时间】:2026-11-15 【老师】:汤圆 【留名】:狍子布鲁斯 【人照】:8 【颜值】:8 【身材】:8 【服务】:7 【态度】:7.5 【环境】:8 【综合】:7.75 【过程】:妹妹身材蛮高的,168,身材匀称,不瘦不胖,有胸有屁股,右臂大花臂,脸还有点婴儿肥,皮肤浅黄皮 洗澡陪浴主动,人也比较健聊,说是从武汉过来的,舔胸吮吸感足,口活卖力,不让停不停的,有点小需求也满足 舌吻浅舌,没有69,下面可以摸,逼是真的紧,也很湿润,是嫩妹穴的感觉 传教士,侧入,躺入,后入,怕趴入,有点累了,妹妹女上,挺会摇的,比一般嫩妹好多了,摇出感觉了,还是我上去,边🐍边操,顺利出货 【总结】:嫩,服务不多

15 Nov 2026, 10:52 UTC≈1,090 viewsread 15 November 2026
Photo

工兵专用模板: 【时间】:20261115 【老师】: @didien001 【留名】:江南不再深情 【人照】:9 【颜值】:8 【身材】:8 【服务】:9 【态度】:9 【环境】:9 【综合】 老牌公寓,人照无差,异域风情,,毛发旺盛,眼睛亮,像新疆人,频道视频都挺真实。黄皮,无纹身。毛多,黑森林,皮肤有点毛糙,应该是刮过腿毛和摸胡子一样,奶头偏黑。微胖有小肚子,估计有110斤上。舌吻69不抗拒,口活无齿感。很骚会浪叫,妹妹全自动,舔完咪咪牛子,戴套自己坐上来,压着我舌吻,快速结束战斗。

15 Nov 2026, 07:53 UTC≈1,140 viewsread 15 November 2026
Photo

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_5640240885

15 Nov 2026, 07:53 UTC≈1,120 views1 reactionsread 15 November 2026
Photo

【时间】:2026.11.14 【老师】:棒棒糖 【留名】:哈吉哈 【人照】:7 【颜值】:7 【身材】:7 【服务】:7 【态度】:3 【环境】:7 【综合】 :6.3 【过程】 :时隔一个多月的出击,拉了一坨大的,体验贼差,后入的时候上下滑动一下准备插入,稍微碰到一下菊花边边,跟TM被电了一样叫起来说不能插菊花,你TM菊花是被扩过吗,合不起来是吧,夹不住屎?一下就能滑进去?一惊一乍的,还TM两次,能不软点我敬你是个人物,中途还要跑一边去说要休息一下。人照有差,蜡黄皮,后入有味儿。喜欢吃屎的去吧。 哦还有,全程浑身抖个不停,我甚至怀疑磕了,拉完了。

❤1

15 Nov 2026, 04:08 UTC158 viewsread 15 November 2026
Photo

【时间】:2026-11-14 【老师】:西西 【留名】:情兽 【人照】:8.8 【颜值】:8.8 【身材】:9 【服务】:9.2 【态度】:9.5 【环境】:8 【综合】:8.88 【过程】:联系好进门,躲门后一个BBW女孩!有着眼睛大大的,确实厚乳肥臀很欧美~内向小男孩寒暄两句赶紧脱衣洗澡,浴室较小蹲不下俩人,不过有帮洗和水中萧,抬头用大眼睛骚骚的看着,把我整害羞了,上床B面西西先给自己大奶涂上油,在上下蹭说要把自己蹭高潮~然后毒龙真往里钻!赶紧翻到正面,摸着大奶69,逼逼很肥美,准备舔喷,可惜没实力,戴套开凿,123~一股强流把我小几把都冲出来了~放正继续123~把持不住,泄~可惜后入没体验到 【总结】:真是爱笑的BBW女孩~

15 Nov 2026, 03:08 UTC≈1,180 viewsread 15 November 2026
Photo

工兵专用模板: 【时间】:2026.11.14 【老师】: 慧慧 @T_ti_mi 【留名】:🐟小小 【人照】:8.8 【颜值】:8.5 【身材】:8 【服务】:8.8 【态度】:9 【环境】:8.5 【综合】: 8.6 【过程】:约的老师尾课,课室位于公寓楼,从正面走要刷卡,经老师引导从货梯可直接上楼到达教室。开门老师害羞躲在门后,1米7的御姐一枚。里面空间挺大,老师开着空调温度适宜,就是淋浴间略小,所以洗浴时老师全程站外面,但全程不用动手由老师来洗的干干净净。完事后上床,先开始 B 面服务,老师不愧是会所出来的,一整套服务流程行云流水,先是手按,再是🐻推,然后涂湿后背用👅开始吸皮,从背到脚,舒舒服服。毒🐲也很专业,拿👅用力的顶,随后翻过来 A 面,舔到二弟周边,先舔🥚后舔根最后没入整根二弟,好不快活。等二弟完全硬起来后,戴套进入,先女上后传教,奈何本🐺状态一般,后续边舔奶子边手打出货,🐍在老师柰子上,完事后先休息会,进…

14 Nov 2026, 16:47 UTC≈2,210 viewsread 15 November 2026
Photo

工兵专用模板: 【时间】:2026.11.15 【老师】:棒棒糖 @bangbangtang1314 【留名】:挑杆无罪 【人照】:8 【颜值】:8 【身材】:8 【服务】:9 【态度】:9 【环境】:9 【综合】:8.5 【过程】: 约的老师尾课,老师热情迎接,个子是非常小一个,也很瘦,感觉适合抱操。实话实说人照是有点差距的,皮肤不像照片那样白,没有照片漂亮,皮肤属于黑黄皮,没什么胸。 有一套jk制服和丝袜。服务有陪浴,然后69口和做。口活嫩妹水平,有点用力过猛。指导了一下学的挺快,然后时间也长让停才停。戴套做爱正常松紧,逼是粉红的。叫床和姿势都挺配合的。态度这一块是挺好的,努力服侍我的感觉。性格是东北那种大大咧咧的,聊天一直在说好听话给情绪价值。送客也不像有的嫩妹做完就不管你了,一直把我送到门口然后道别,让我注意安全,说期待下次见面。总体还是不错的。

14 Nov 2026, 16:31 UTC≈2,290 viewsread 15 November 2026
Photo

工兵专用模板: 【时间】:11.14 【老师】: 兔子涵 @Tuzihanbaobao 【留名】:吉吉国王 【人照】:9 【颜值】:9 【身材】:8.5 【服务】:8.5 【态度】:9 【环境】:9 【综合】 课室位于小区,环境很不错,健康又卫生!老师颜值中上,但是身材微微胖。老是洗过澡,没有陪浴,工兵洗澡后,开始正题。嫩妹服务三件套,口活一般,需要加强。老师皮肤偏白,光滑,没有纹身,胸器很大,很软,很舒服,是我喜欢的,老师下面也很润,毛毛不多,摸起来很有感觉。硬了后,直接带套开干,三分钟一局,巨爽巨解压!工兵还是一如既往地,123完事。整个过程还不错,老师态度很好,很听话,不催不事,全程配合,逼感不错,做爱有反馈,挺不错的一次出击!

14 Nov 2026, 13:28 UTC≈2,230 viewsread 15 November 2026
Photo

🎰 夜猫女仆重生抽奖 📮 参与条件: 🪪 必须设置用户名 🎫 加入-苏州桃花坞今日开课资源群 🎫 加入-苏州夜猫私影女仆mmk 🎫 加入-苏州夜猫私影女仆mmk相册 🎫 加入-苏州桃花坞 └ 🎟️ 发言数大于 30 条 🎫 加入-苏州桃花坞新人榜 🎫 加入-苏州桃花坞报告 🎁 奖品内容: 💰️ 100优惠卷 × 5 💰️ 28.8红包 × 3 💰️ 66红包 × 1 💰️ 女仆加时半价卷 × 2 💰️ 女仆半价卷 × 2 📅 开奖日期:(北京时间) 2026年11月19日 18时00分00秒

14 Nov 2026, 10:54 UTC≈2,360 views0 reactionsread 15 November 2026
Photo

工兵专用模板: 【时间】:11.14 【老师】: 锦毛鼠 @Jinmaoshu2026 【留名】:不用爱你 【人照】:9 【颜值】:9 【身材】:9 【服务】:8.8 【态度】:9 【环境】:8.7 【综合】 课室位置特别好找,环境也很不错,开门看到老师的瞬间就被吸引住了。身材比例非常协调,黑丝的衬托下妩媚动人,再说到妆容,淡淡彩妆,眼睛特别有神,水灵灵的看着你有些情人的感觉。付水费洗澡,老师一直跟着身边帮洗帮擦,洗完让老师换上情趣黑丝,一转身看到老师结实的翘臀我小弟弟一下就给我发出了信号。老师让我躺床上,课表上的服务都有做使我神魂颠倒,接着开始给我安抚小弟,老师口的很卖力,眼神拉丝的同时还时不时的问我舒不舒服,时不时的轻声低吟让我沉醉,忍不住了让老师带上套套。开始先是女上,再换我在上面,再换了后入的姿势,能感觉到老师阴道里的紧缩,被深深的吸附住。整个过程气氛很好不冷场。

14 Nov 2026, 10:43 UTC≈2,370 viewsread 15 November 2026
Photo

【时间】:2026-11-14 【老师】:知夏 【留名】:天天 【人照】:8.6 【颜值】:8.7 【身材】:9 【服务】:9 【态度】:10 【环境】:9 【综合】:9.05 【过程】:根据指引上楼,在一个小区相对比较安全,进门递水态度很好,之后流程洗澡开始服务,课表上服务都有,可惜没有舌吻,很听话可以换姿势配合,经过十分钟努力后完美释放,然后洗洗聊会天就走了,较好的体验 【总结】:推荐

14 Nov 2026, 10:43 UTC≈2,170 views0 reactionsread 15 November 2026
Photo

【时间】:2026-11-14 【老师】:葡萄糖 【留名】:荼豆 【人照】:9.5 【颜值】:9 【身材】:9 【服务】:8.5 【态度】:8.5 【环境】:9 【综合】:8.92 【过程】:提前约好,遥控上楼。地处小区,位置偏僻安静。身着包臀群,一上门容易上头的感觉。身材苗条,个头高挑,170+,屁股很翘,看着就很有想法,频道滤镜很重,脸比照片好看。服务类似spa的服务,全身过水,胸推,水中萧,b面胯下萧,无毒龙。口活包裹感紧致,感觉到位立即打伞。刚进入明显感觉到入口紧,能明显感受到褶皱摩擦感,没一会儿结束。 【总结】:身材很顶,屁股翘有肉,大蟒蛇,会所级服务。皮肤有痘,排课较紧。总结还是挺爽的

Showing the 12 most recent of 573 posts we hold for @thwbaogao. 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 edited after publishing

@thwbaogao edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
9 November 2026
Most recent edit
9 November 2026

Posts recorded as deleted after publishing

We recorded 2 posts on @thwbaogao 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
3 November 2026
Most recent seen missing
9 November 2026
Median time before seen missing
30 hours
Seen missing in the last 30 days
2

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

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

“苏州桃花坞报告” (@thwbaogao), 48,833 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/thwbaogao.

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.