Telegram RegisterThe public register of Telegram
Telegram profile photo for 相见欢报告

Channel

相见欢报告

@xueshuqu

On this record: Growth · Engagement · Posts · Citations · Cite this entry

2,227subscribers

-5 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003540079259
TypeChannel
Username@xueshuqu
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 live16 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/xueshuqu

Growth

2,2272,2342,230.56 August 2026 — 2,232 subscribers7 August 2026 — 2,234 subscribers10 August 2026 — 2,232 subscribers13 August 2026 — 2,234 subscribers16 August 2026 — 2,227 subscribers6 August 202616 August 2026
5 measurements spanning 10 days, net -5. 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 2,226–2,235 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 19:542,227-7
13 Aug 2026, 11:232,234+2
10 Aug 2026, 09:022,232-2
7 Aug 2026, 15:242,234+2
6 Aug 2026, 22:462,232first reading

Engagement

22 posts held, back to 29 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
6.95%
avg views ÷ 2,227 subscribers
Avg views / post
155
3 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
3
of 22 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held22 (29 June 20267 August 2026)
Views total464
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 16:49 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.

Recent posts

7 Aug 2026, 11:01 UTC150 viewsread 7 August 2026

【深圳相见欢报告】 https://t.me/shenshengchujian 【出击群友】:史努比 【出击日期】:8.7 【老师名字】: 心怡 【课室地区】:南山 【联系方式】:@xinyimeimeid 【身材颜值】: 大长腿 胸大屁股翘 人照一致 【情绪价值】: 很不错 妹妹挺能聊天的 也很配合 【体验过程】: 已经去了六七次,很喜欢的一个老师,价格在南山很实惠,而且是个嫩妹的同时情绪价值很不错,身材还很好,168左右的身高,细腰翘臀,胸很有料很软,白白嫩嫩的。共浴舌吻丝袜六九服务很全,口的很认真时间很长,也是宝藏老师。会叫爸爸声音很甜,下面也很紧致,很推荐。 【优点不足】:身材好颜值高 服务不错舌吻管饱

7 Aug 2026, 05:16 UTC98 viewsread 7 August 2026

【深圳相见欢报告】 https://t.me/shenshengchujian 【出击群友】:史努比 【出击日期】:8.5 【老师名字】:乔伊伊 【课室地区】:福田 【联系方式】:@Qiao118801 【身材颜值】: 人照一致,老师很魅惑很会眼神勾引,胸屁股大身材匀称 【情绪价值】: 还不错,老师挺能聊天的,床上反馈也很好 【体验过程】: 被老师频道的视频吸引,老师真人也挺骚的,尤其在床上叫的很色,而且也在享受会让加速大力。老师屁股很大后入很爽,下面人工白虎观感也不错。口活很不错,尤其口的时候会抬头很魅惑的看着你,有种AV里的感觉,很不错的体验,挺过瘾的。而且可以拍小视频,拍了一小段还挺刺激。 【优点不足】: 服务很好床上很风骚,老师人不错聊天也挺开心

2 Aug 2026, 08:26 UTC216 viewsread 7 August 2026

【深圳相见欢报告】 https://t.me/shenshengchujian 【出击群友】:史努比 【出击日期】:8.2 【老师名字】:知意 【课室地区】:南山 【联系方式】:@zhiyi20048 【身材颜值】: 175的身材,天然胸没有科技,身材很不错不愧是锻炼过的,腰没有赘肉屁股很饱满,大长腿坐各种一字马姿势很性感,颜值在嫩妹和御姐之间 【情绪价值】: 很主动聊天很热情,准备了饮料 零食冰激凌什么的,床上很主动还玩角色扮演,很有趣的老师,反馈也不错 【体验过程】: 老师身高很高胸很饱满呼之欲出,很热情各个服务都很认真仔细,主动帮忙脱衣服去浴室洗澡,很主动亲吻多次主动亲亲。穿上丝袜体操服坐各种一字马姿势,真就是体操生知意还主动说玩角色扮演,假装日本电影里的体操生和老师。然后知意柔韧性真的很好,几种一字马姿势很轻松,口活很强可以深喉到底,甚至可以深喉到底用舌头舔,真的有爽到。传教姿势两条大长腿可以随便摆弄,最后在正面一字马的

18 Jul 2026, 17:27 UTC468 viewsread 7 August 2026

【深圳相见欢报告】 https://t.me/shenshengchujian 【出击群友】:格兰 【出击日期】:7.14 【老师名字】:云朵糖 【课室地区】:福田 【联系方式】:@YDTydtydt_sz 【身材颜值】:S 【情绪价值】:高 【体验过程】:约了好久云朵糖,一直没对上时间,老师前段时间出了车祸,加红休回来都是大半月以后了,老师之前的号炸了,用了个新号在群里聊天,我看老师在群里冒泡赶紧联系,没想到居然约上了,还是回来的第一课,第二天上午抓紧定了张动车票匆匆回深,在约定时间到达老师的课室,课室环境干净整洁,很温馨,老师身材高挑,长相甜美,身高约170左右,两人相拥在沙发上闲聊,闲聊得知老师还是大三的学生,来深圳实习,抽着空来开课,每日最多3-4课,我看聊的差不多,就和老师进浴室冲洗,老师认真帮忙清洁,由于浴室空间有点小,就没让老师口萧,擦拭完毕转床上,口活起手,轻微的齿感,看的出来老师做这行没太久时间,纯纯刚入行,我

12 Jul 2026, 11:10 UTC452 viewsread 7 August 2026

【深圳相见欢报告】 https://t.me/shenshengchujian 【出击群友】:安东尼 【出击日期】:7.11. 【老师名字】:千雪 【课室地区】:宝安 【联系方式】:@SzQianxue8 【身材颜值】:人照几成9成。一米七,身材好。大D胸 【情绪价值】:不错 【体验过程】:胸大,敏感很容易出水,亲两下奶子水直流,拉丝了直接,服务这一块都可以该做的项目没有漏一个,事后按摩,重点很会夹口活很屌!!差点直接被秒,缺点的话个人暂时没有,身材属于bbw,不是坦克那种,肚子没有赘肉,韵味够够的 【优点不足】:大🐻 服务好 热情 身材非常棒

7 Jul 2026, 08:11 UTC488 viewsread 7 August 2026

【深圳相见欢报告】 https://t.me/shenshengchujian 【出击群友】:zame 【出击日期】:7.5 【老师名字】:星星 【课室地区】:南山 【联系方式】:@xingxing0622 【身材颜值】:甜妹脸,身材天然巨乳,前凸后翘 【情绪价值】:高 【体验过程】:看到很多人推荐星星,而且她快要走了赶忙约了她,果然名副其实,长相甜美,身材优越,而且态度很好,情绪价值高,进门抱着聊了一会之后陪洗,竟然还有水中萧,然后到床上抱着开始亲,舌头软软的,很灵活,抱着大白兔舔了一会,还尝试了一下乳交,毕竟这么大的胸太少见了,然后开始享受服务,亲咪咪舔蛋蛋都有,口技不错,口的很深,于是戴套进入,水很多,边舔胸边输出,后入大屁股也很爽,又尝试了一下女上,感觉女上要被秒,于是换后入出水。可惜她后面要离开一段时间再回来了,下次约估计要等一段时间 【优点不足】:颜值高身材好,服务好,情绪价值高

7 Jul 2026, 02:07 UTC348 viewsread 7 August 2026

【深圳相见欢报告】 https://t.me/shenshengchujian 【出击群友】:gin sang 【出击日期】:7.6 【老师名字】:妮蔻 【课室地区】:福田 【联系方式】:@FTnkou 【身材颜值】:9.5/10 【情绪价值】:9.5/10 【体验过程】:先前在频道看视频和照片就已被勾得欲火焚身,那胸大腰细的黄金比例简直是人间凶器。今天满怀期待依约前往,开门的瞬间,直接被真人惊艳到——大眼睛、高鼻梁,那张纯欲交织的精致脸蛋活脱脱就是从抖音里走出来的极品网红,真实感带来的视觉冲击让小弟当场立正,话不多说,立马付水费开战! 💦 湿身前戏:水中玉箫的极致温柔 洗浴时,跨进浴缸的那一刻,才是好戏的开始。她一丝不挂地贴上来,丰满的巨乳在水波中荡漾、挤压着我的胸膛。她顺势蹲下,温热的口腔瞬间包裹住小弟,在温水的滋润下,水中箫的吸吮感紧致而绵密,那种冷热交替的包裹感,差点让人在浴室就缴械。 👙 视觉盛宴:JK制服与极品马

6 Jul 2026, 17:03 UTC≈1,940 viewsread 7 August 2026

【深圳相见欢报告】 https://t.me/shenshengchujian 【出击群友】:格兰 【出击日期】:7.5 【老师名字】:落落 【课室地区】:南山 【联系方式】:@luoluo5522 【身材颜值】:S 【情绪价值】:高 【体验过程】:反的最多的老师,熟到都像认识多年的老朋友,进屋要拉着我去洗澡,我让她在沙发等我,我自己去冲洗,洗完下楼抱着老师上下其手在沙发聊天,聊着聊着兴致起来,老师帮我口硬开始传教士进入,湿润紧致的通道,层峦叠嶂,深入时包裹着龟头让我沉迷不能自拔,进出不自觉地收缩,让我陶醉,差点被秒,深吸了口气,转成后入,满背的凤凰再次让我着迷,对着凤凰使劲冲刺,这凤凰冲多少次都冲不腻,老师呻吟声渐大收缩越来越明显,高亢的叫声突然停滞了几秒伴随着阴道的抽搐老师应该来了,我停下动作抱着老师抚摸着凤凰纹身,老师扭头亲了下我的唇,让我躺平,转身开始女上,前后左右的旋转摇摆,幅度越来越大,老师在我身上起伏,还不忘刺激我

6 Jul 2026, 16:59 UTC246 viewsread 7 August 2026

【深圳相见欢报告】 https://t.me/shenshengchujian 【出击群友】:匿名 【出击日期】:7.3 【老师名字】:夏夏 【课室地区】:福田 【联系方式】:@sns1688 【身材颜值】:8 【情绪价值】:7 【体验过程】:进门后和老师简单聊了一会后洗澡。老师身材很好,胸很大,陪洗过程也洗的比较细心。之后去到床上简单🐍了一会,老师开始一些简单的服务。然后反过来推到老师,亲了会胸🐍了会后带上tt,直接冲击老师,老师doi反应很真实,会有喘息声。也很配合 【优点不足】:无

6 Jul 2026, 16:56 UTC224 viewsread 7 August 2026

【深圳相见欢报告】 https://t.me/shenshengchujian 【出击群友】:格兰 【出击日期】:7.5 【老师名字】:星星 【课室地区】:南山 【联系方式】:@xingxing0622 【身材颜值】:颜值S,真胸D 【情绪价值】:高 【体验过程】:近期大火的老师,几个相熟的群友都在大力推荐,头像照片原本看的无感,耐不住大家的一致好评,提前两天约的老师,因为是周末比约定时间早了20分钟到达老师科室楼下,由于前面的学生拖了会堂,我进门时间是有点火,见到老师那刻火就消了一大半,老师的颜值身材都长在我的点上,板着脸交完水费,由于还在生着拖堂的气就没有寒暄,老师过来脱我衣服,让我去洗澡,手哆哆嗦嗦的帮我脱者T恤,看老师那样心生不忍,牵着老师手进浴室,老师帮忙认真清洗,擦拭,也没让老师水萧,直接转床上,老师三点舔吸,我看口硬就直接带套传教起手,进入凿了几下老师开始大声浪叫,真是个尤物啊,转成后入老师的声音越叫越大,担心影响

6 Jul 2026, 16:33 UTC221 viewsread 7 August 2026

【深圳相见欢报告】 https://t.me/shenshengchujian 【出击群友】:杂鱼 【出击日期】:6.6 【老师名字】:米朵 【课室地区】:福田 【联系方式】:@futianmiduo 【身材颜值】:9 【情绪价值】:9.5 【体验过程】:群里看到老师色到无比的视频,一口酸奶一口🐔,激动问时间,下雨就是适合出击,一问就有位置 一进门感觉相识已久,姐姐上手就乱搓,洗澡同时提到了下午视频,老师说刚好有要不要试一试,吹头发的时候,老师和我说吹一下,吹那? 吹头发啊!然后在吵杂的吹风声中直接给我就吹上了!?! 本质色狼了,直接满嘴跑火车,来到客厅对镜又是一顿乱吃,来到正餐,不枉下雨天跑出来,一顿操作,深喉,69感觉🐔要爆炸了,换上丝袜一段乱撞,太湿了,好久没有去过这种老师了 【优点不足】:很配合,情绪价值相当到位

6 Jul 2026, 16:30 UTC206 viewsread 7 August 2026

【深圳相见欢报告】 https://t.me/shenshengchujian 【出击群友】:M 【出击日期】:7.5. 【老师名字】:木子 【课室地区】:宝安 【联系方式】:@Szmuzi8 【身材颜值】:颜值比照片好多了,科技d胸,皮肤很滑 【情绪价值】:可以的 【体验过程】:进门聊天,然后老师帮我洗澡,然后开始服务,从头开始舔,舔我耳朵和脖子太痒受不了,老师反而有成就感。随后进攻小弟,有节奏模拟先浅后深,挺有趣的,我手也是不停摸她的提子。然后轮到我进攻,最后带帽攻击。体验很好 【优点不足】:有纹身,除此没啥问题

Showing the 12 most recent of 22 posts we hold for @xueshuqu. 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.

Citation-graph rank

Citation-graph rank — 313,293 of 1,481,306entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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

“相见欢报告” (@xueshuqu), 2,227 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/xueshuqu.

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.