『推荐指数:⭐️⭐️⭐️⭐️⭐️(参照末尾星级评判标准)』 【验 证 人】:章鱼哥 【日 期】:2026年11月16 【美女昵称】:迪士尼 【所属频道】:https://t.me/hfgkb_101/2953 【地 区】:包河 【见面感觉】:(满分10分) 【身材曲线】:10 【风情指数】:9 【技术含量】:8 【年 龄】:19 【身 高】:大概1.7米左右 【凶 器】C 【肤 色】美白 【人照相似】:真人好看过照片 【服务内容】:口 做 洗澡 舌吻 【服务过程】:上楼进门之后看到老师第一印象很惊讶,长得又高身材又好,感觉真人比照片有气质,然后开始洗澡,洗完澡上床老师开始服务,不过老师好像比较腼腆害羞,但是很听话,老师口完果断带T开始CJ,换了好几个姿势,老师叫床声音也很好听,持续半个小时战斗终于发射,然后简单冲了一下走人,整个过程很…
Channel
合肥学报告榜2.0
@csbgb_103
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry
7,271subscribers
+1,196 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002305432441 |
|---|---|
| Type | Channel |
| Username | @csbgb_103 |
| Description | 上榜联系 @shxsl_bot 群聊 @hfxsh_123 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 13 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 13 November 2026 |
| On Telegram | t.me/csbgb_103 |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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 |
|---|---|---|
| 13 Nov 2026, 20:47 | 7,271 | +39 |
| 9 Nov 2026, 09:54 | 7,232 | +21 |
| 6 Nov 2026, 06:36 | 7,211 | +31 |
| 3 Nov 2026, 08:28 | 7,180 | +24 |
| 31 Oct 2026, 07:36 | 7,156 | +24 |
| 28 Oct 2026, 11:36 | 7,132 | +28 |
| 25 Oct 2026, 16:19 | 7,104 | +45 |
| 22 Oct 2026, 23:09 | 7,059 | +25 |
| 19 Oct 2026, 23:47 | 7,034 | +25 |
| 16 Oct 2026, 13:28 | 7,009 | +18 |
| 13 Oct 2026, 22:14 | 6,991 | +78 |
| 8 Oct 2026, 06:40 | 6,913 | +74 |
| 1 Oct 2026, 22:21 | 6,839 | +198 |
| 16 Sept 2026, 19:21 | 6,641 | +71 |
| 12 Sept 2026, 13:57 | 6,570 | +85 |
| 8 Sept 2026, 04:57 | 6,485 | +65 |
| 3 Sept 2026, 01:28 | 6,420 | +27 |
| 31 Aug 2026, 09:28 | 6,393 | +59 |
| 28 Aug 2026, 07:16 | 6,334 | +46 |
| 25 Aug 2026, 11:53 | 6,288 | first reading |
Engagement
101 posts held, back to 4 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 27 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 14.2%
- avg views ÷ 7,271 subscribers
- Avg views / post
- 1,030
- 80 posts measured
- Reaction rate
- 0.115%
- reactions ÷ views · ER floor
- Posts in window
- 80
- of 101 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 37 of 80 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 101 (4 August 2026 – 16 November 2026) |
| Views total | 82,551 |
| Reactions total | 52 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Nov 2026, 15:46 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
- ≈2
- Links
- ≈1,600
Lifetime counters from Telegram’s own channel header, read 16 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
86 reactions across 44 posts, in 2 distinct kinds. The most used accounts for 95.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 82 | 95.3% | |
| 👍 | 4 | 4.65% |
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 52 of the 101 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 86 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 101 most recent posts we hold, published 4 August 2026 to 16 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: 1 of 80 posts held from the last 30 days (1.25%) 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).
2026-11-12 CC 推荐指数:⭐️⭐️⭐️⭐️ 【验 证 人】:不吃青菜@HudecTransformer 【日 期】:2026年11月12日 【美女昵称】:CC 【所属频道】:https://t.me/hfgkb_101/2940 【地 区】:瑶海 【见面感觉】:10 【身材曲线】:9 【风情指数】:9 【技术含量】:9 【年 龄】:18 【身 高】:1米7 【凶 器】:A 【肤 色:正常嫩妹肤色 【人照相似】:真九分 【服务内容】:口 做 洗澡 舌吻 【服务过程】: “抽象的好看妹子” 进门看瘦瘦高高的嫩妹一枚。脸是好看的,妆造也可以,身高1米7,讲话嫩妹抽象感,平胸,喜欢穿圆头小白鞋。 过分紧窄,进不去,原准备放弃,妹子急了,自己抓着JJ硬怼进去。行,被夹就完事了。明白了“箍“”字怎么写。 喜欢好看、紧窄和平胸的冲 …
『推荐指数:⭐️⭐️⭐️⭐️⭐️(参照末尾星级评判标准)』 【验 证 人】:匿名 【日 期】:2026年11月14日 【美女昵称】:十七 【所属频道】:https://t.me/hfgkb_101/2554 【地 区】:滨湖区 【见面感觉】:8 【身材曲线】:8 【风情指数】:9 【技术含量】:8 【年 龄】:大概20不到 【身 高】:大概一米6 【凶 器】AB之间 【肤 色】挺白 【人照相似】:相似度8分朝上 【服务内容】:口 做 洗澡 69 【服务过程】:很久没做了,心血来潮看到榜单上有新来的妹妹,看照片和视频是我喜欢的类型,遂约了个包时,由于路程较远加上堵车,迟到了半小时,妹妹也表示理解。到楼下根据指引,进入房间就看到妹妹穿着情趣内衣,很满意,付水费,和妹妹一起洗了个澡就上楼了,妹妹问我要什么制服,我说随便,她穿了个jk过来了,…
『推荐指数:⭐️⭐️⭐️⭐️⭐️(参照末尾星级评判标准)』 【验 证 人】:休 【日 期】:2026年11月16日 【美女昵称】:迪士尼 【所属频道】:https://t.me/hfgkb_101/2953 【地 区】:包河 【见面感觉】:8(满分10分) 【身材曲线】:8 【风情指数】:7 【技术含量】:8 【年 龄】:19左右吧 【身 高】:大概一米七几,身材苗条 【凶 器】C 【肤 色】正常黄 【人照相似】:人照6.7分 【服务内容】:口 做 洗澡 【服务过程】:看到学生会新上个妹妹好评挺多的,约了一下成功约上。到了先罚站了10分钟,说是拿外卖去了。我先到一步到了门口,过了5.6分钟走来一个女生,也没打招呼也没跟我说话,直接开了门,我站旁边心里以为自己走错地方了?看她进去没关门,才问了一句是这个?她点头说是的,我才一脸懵逼的跟着…
『推荐指数:⭐️⭐️⭐️⭐️⭐️(参照末尾星级评判标准)』 【验 证 人】:匿名 【日 期】:11月16日 【美女昵称】:泠泠 【所属频道】:https://t.me/hfgkb_101/2601 【地 区】:包河区 【见面感觉】:10(满分10分) 【身材曲线】:10 【风情指数】:10 【技术含量】:10 【年 龄】:19左右吧 【身 高】:165 苗条 【凶 器】C 【肤 色】美白 【人照相似】:真人好看过照片 【服务内容】:口 做 洗澡 舌吻 【服务过程】: 优点:看了很多朋友之前的报告,都描述的很好,去了之后发现朋友们还是保守了,回来的路上思来想去不知该怎么说,最后只挤出了几个字,结束了不亚于分手了。发到群里看很多朋友都说这个评价很妙,可能也引起了大家的共鸣吧,具体的内容和细节也就不在此班门弄斧了,先前的朋友们都写的很棒…
『推荐指数:⭐️⭐️⭐️⭐️⭐️(参照末尾星级评判标准)』 【验 证 人】:心态崩了 【日 期】:11.13 【美女昵称】:泠泠 【所属频道】:https://t.me/hfgkb_101/2601 【地 区】:包河 【见面感觉】:9 【身材曲线】:9 【风情指数】:9 【技术含量】:9 【年 龄】:19 【身 高】:166cm 【凶 器】C 【肤 色】黄皮偏白 【人照相似】:8分相似 【服务内容】:口 做 洗澡 舌吻 【服务过程】:看到泠泠在线,和泠泠约了一下晚上的课 ,提前到达, 过了几分钟,她也来了,我勒个豆,这不就是我路上遇到的那个黑色大衣妹子😂,然后一起上的楼,坐下,聊了一会天,然后老师给我去放热水,放完水,交了水费,然后我俩一起脱衣服,脱完衣服,身材是真的不错,奶子也大,比照片感觉还瘦一点, 主动给我洗身体,洗完擦后背,上…
『推荐指数:⭐️⭐️⭐️⭐️⭐️(参照末尾星级评判标准)』 【验 证 人】:匿名 【日 期】:10.16 【美女昵称】:曦曦 【所属频道】:https://t.me/hfgkb_101/2546 【地 区】:滨湖区 【见面感觉】:(满分10分) 【身材曲线】:10 【风情指数】:9 【技术含量】:10 【年 龄】:19左右吧 【身 高】:大概一米六7,御姐类型 【凶 器】C 【肤 色】美白 【人照相似】:7.8成相似 【服务内容】:口 做 舌吻 69 【服务过程】: 优点:优点:很会口活,服务质量和态度非常好。 服务细节:到了地方,等了曦曦老师10分钟,一开始还以为这下完犊子了,哥布林要被罚站咯。但是幸好只等了10分钟。 上一个老客桩基终于离开了,进门老师穿的是黑丝,直接让我做沙发上休息一会,拿了瓶百岁山水给我喝。我脱下衣…
推荐指数:⭐️⭐️⭐️⭐️⭐️ 【验 证 人】:未央 【日 期】:2026年11月15日 【美女昵称】:十七 【所属频道】:https://t.me/hfgkb_101/2554 【地 区】:滨湖 【见面感觉】:10 【身材曲线】:10 【风情指数】:10 【技术含量】:10 【年 龄】:19 【身 高】:1米58 【凶 器】:B 【肤 色:白 【人照相似】:真人好看过照片 【服务内容】:口 做 洗澡 舌吻 【服务过程】: 肯定要给到夯,根据老师引导进了房间,里面收拾的很干净,进来就看老师穿着情趣内衣,瞬间就立正了,在沙发上跟老师聊天,抽了根烟就进入了正题,老师陪我一起洗的澡,洗完问我要穿啥战袍,选了个JK,上楼后老师特别热情,上来就是大蟒蛇管饱,然后就开始口,在嫩妹中绝对最顶级,差点就出来了,没忍住让老师带上帽子就开始了,观音坐莲水…
『推荐指数:⭐️⭐️⭐️⭐️⭐️(参照末尾星级评判标准)』 【验 证 人】:奶白的雪子 【日 期】:2026年11月16日 【美女昵称】:迪士尼 【所属频道】:https://t.me/hfgkb_101/2953 【地 区】:包河 【见面感觉】:(满分10分) 【身材曲线】:10 【风情指数】:9 【技术含量】:8 【年 龄】:19左右吧 【身 高】:大概一米七几,身材苗条 【凶 器】C 【肤 色】美白 【人照相似】:真人好看过照片 【服务内容】:口 做 洗澡 【服务过程】:最近几天由于工作和一些琐事心情有点烦躁,出击找一个情绪价值高的老师缓解一下,跟迪士尼约好时间来到楼下进门就是一个大拥抱,进屋坐下跟老师聊了许久,老师非常耐心,而且态度很好说话也温柔,随后在缠绵了一会之后脱去衣服来到浴室,(老师要求配浴我没同意习惯自己)出浴发现老…
推荐指数:⭐️⭐️⭐️⭐️⭐️ 【验 证 人】:不吃青菜@HudecTransformer 【日 期】:2026年11月13日 【美女昵称】:十七 【所属频道】:https://t.me/hfgkb_101/2554 【地 区】:蜀山 【见面感觉】:10 【身材曲线】:10 【风情指数】:10 【技术含量】:10 【年 龄】:20 【身 高】:1米6 【凶 器】:!B 【肤 色:开灯显白 【人照相似】:真人好看过照片 【服务内容】:口 做 洗澡 舌吻 【服务过程】: 在滨湖嫩妹里她仍是最能打的那个 再见面再见面,还是那个说话温温柔柔的样子,一进门就被拉进去,“看,答应你了穿女仆装,好看吗?““更好看了,就是有点烧”“算你会说” 看着她穿着女仆装,白丝,洛丽塔小皮鞋的样子,脑补了一会反差的样子。 我“那就不用洗了,省的还要脱要穿”,…
『推荐指数:⭐️⭐️⭐️⭐️⭐️』 【验 证 人】:cc 【日 期】:2026-11-15 【美女昵称】:迪士尼 【所属频道】:https://t.me/hfgkb_101/2953 【见面感觉】:10(满分10分) 【身材曲线】:10 【风情指数】:9 【技术含量】:8 【年 龄】:不到20 【身 高】:真实一米7,身材苗条有料 【凶 器】C 【肤 色】正常 【人照相似】:真人好看过照片 【服务内容】:口 做 洗澡 【服务过程】:老师东北嫩妹,身高颜值都是大美级别,模特身材,服务极度热情,老师一边陪洗浴一边聊天,结束了上床开始服务,躺在床上老师让我选战服,打开柜子我一看惊呆了,有点眼花撩乱,随后选了一件我心意的让老师穿上,开始阶段老师舔着我的胸我也摸着老师的胸,很是舒服,老师的口没有一点齿感,属于一流水平,带上套先开始女上位,说实话差点被秒,随后…
『推荐指数:⭐️⭐️⭐️⭐️⭐️(参照末尾星级评判标准)』 【验 证 人】:奶油热可可 【日 期】:11月15号 【美女昵称】:曦曦 【所属频道】: https://t.me/hfgkb_101/2546 【地 区】:蜀山区 【见面感觉】:(满分10分) 【身材曲线】:10 【风情指数】:9 【技术含量】:8 【年 龄】:20左右吧 【身 高】:大概一米六几,身材苗条 【凶 器】C 【肤 色】美白 【人照相似】:照片比真人白,带美颜 【服务内容】:口 做 洗澡 舌吻 69 【服务过程】:《曦曦》 11月15号,飞机上闲逛,不知道找谁,想起了曦曦,果断联系,一开始开课比较晚,所以没约上,后来又联系上提前开课了,立马约上头课,按照位置指引,到达房间。 进门第一眼,偏御姐风一点,少妇之下的感觉,老师个子算高的了,身材正好,照片带了美颜美白,…
Showing the 12 most recent of 101 posts we hold for @csbgb_103. 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 @csbgb_103 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
- 9 November 2026
- Most recent seen missing
- 9 November 2026
- Median time before seen missing
- 2 days
- Seen missing in the last 30 days
- 1
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@csbgb_103 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 12 August 2026 – 13 August 2026
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.
“合肥学报告榜2.0” (@csbgb_103), 7,271 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/csbgb_103.
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.