👩雷师艺名: #洲洲 🆔雷师TG: @nwtcse 💣💣💣踩雷过程: 机车下菜女,高度怀疑准备年前捞钱后跑路,对评价持无所谓态度,所以有恃无恐 🪖伤兵留名: 匿名 💣雷报区: 北京 上海 杭州 深圳 广州 ------------------------- 🌲树洞导航 🤖写雷报
❤5

Channel
@shudongleibao_hz
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,670subscribers
+106 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002979516746 |
|---|---|
| Type | Channel |
| Username | @shudongleibao_hz |
| Created | 20 October 2025 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/shudongleibao_hz |
Other / unclassifiable — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 75% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 06:38 | 1,670 | +14 |
| 13 Sept 2026, 06:40 | 1,656 | +7 |
| 9 Sept 2026, 02:57 | 1,649 | +31 |
| 3 Sept 2026, 10:16 | 1,618 | +5 |
| 31 Aug 2026, 03:44 | 1,613 | +5 |
| 27 Aug 2026, 18:45 | 1,608 | +5 |
| 24 Aug 2026, 19:06 | 1,603 | +16 |
| 21 Aug 2026, 02:58 | 1,587 | +11 |
| 18 Aug 2026, 02:03 | 1,576 | +12 |
| 15 Aug 2026, 00:17 | 1,564 | +9 |
| 11 Aug 2026, 22:22 | 1,555 | -7 |
| 8 Aug 2026, 18:55 | 1,562 | -2 |
| 8 Aug 2026, 02:17 | 1,564 | first reading |
11 posts held, back to 20 October 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 11 posts for this entry, the most recent from 6 February 2026. An engagement rate over an empty window would be a number about nothing.
36 reactions across 4 posts, in 4 distinct kinds. The most used accounts for 55.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 20 | 55.6% | |
| 👍 | 13 | 36.1% | |
| 😁 | 2 | 5.56% | |
| 🔥 | 1 | 2.78% |
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 6 of the 11 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 36 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 20 October 2025 to 6 February 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.
👩雷师艺名: #洲洲 🆔雷师TG: @nwtcse 💣💣💣踩雷过程: 机车下菜女,高度怀疑准备年前捞钱后跑路,对评价持无所谓态度,所以有恃无恐 🪖伤兵留名: 匿名 💣雷报区: 北京 上海 杭州 深圳 广州 ------------------------- 🌲树洞导航 🤖写雷报
❤5
👩雷师艺名: #尤奚 🆔雷师TG: @yoxihz 💣💣💣踩雷过程: 人照不符,妥妥的假照 🪖伤兵留名: 匿名 💣雷报区: 北京 上海 杭州 深圳 广州 ------------------------- 🌲树洞导航 🤖写雷报
👩雷师艺名: #优优 🆔雷师TG: @youyou0712 💣💣💣踩雷过程: 1进门穿着后妈裙,人照差距大,黄黑皮,有点龅牙,看脸和皮肤褶皱程度应该有35,进门态度挺热情,就没有漂移 2交水费脱衣服,我说一起洗吧,她说她洗过了,我就自己洗完。擦干躺床上,老师贴了过来,两个人抱了一会儿,我说开始吧,老师说她还有点冷,再躺一会儿。中间老师说她很想要,直接干吧,我说前戏服务还没做呢,快开始吧。老师开始起来吸奶,舔了一会儿又说咱们直接做吧,我说还没口呢。然后老师刚含住鸡巴,老师就说不舒服,要去上厕所。当时心里无语极了,头次碰见还有上课中间上厕所的。老师上了五六分钟厕所回来,我跟老师说,你要是不舒服就钱退给我,咱们各忙各的吧。老师又说她好些了,能上课。然后又是刚含住鸡巴还没动,又说什么扁桃体发炎,痛,口不了,说帮我撸。撸的半硬半软就带套要开始女上,硬度还不到位,根本就放不进去。她就又开始撸,撸硬了再开始,但这个时候套套已经干了,我说套套…
❤7👍7🔥1
👩雷师艺名: #小雨 🆔雷师TG: @xxy666555 💣💣💣踩雷过程: 鸡婆,看人下才菜。1.到了啥也没有,水也没,说刚搬第二天什么东西都没。我认了。 2.让我自己去冲洗,我以为她洗好了,后来我洗完她也去洗了。 3.课表上服务基本无,躺床上敷衍舔胸,然后就戴套啪了。 3.包夜35,然后第一发来完说太困了先休息下。好的,我也CD。CD完差不多一点了,摸胸开始,然后说再睡会,那我就问号了。我是来干嘛的?就这样到三点,外面放烟花醒了,我想着差不多了吧,摸胸,不给摸,还要睡。又到了四点,直接抱上了,然后说肚子痛,去拉屎。拉完屎玩手机,问了她还行不行。她说还痛。我就呵呵呵了,走人。这下菜下的。 我特么来回三小时车来看她下了一晚上菜。 🪖伤兵留名: 我不是呀(岸半年) 💣雷报区: 北京 上海 杭州 深圳 广州 ------------------------- 🌲树洞导航 🤖写雷报
❤6👍6😁2
👩雷师艺名: #酥酥 🆔雷师TG: @qtwy7 💣💣💣踩雷过程: 网图,是个骗子,骗定金的 🪖伤兵留名: 匿名 💣雷报区: 北京 上海 杭州 深圳 广州 ------------------------- 🌲树洞导航 🤖写雷报
5
2
3
🌲洞主有话说: 清一色高分好评的老师也不一定对你胃口,反之即使有过低差评的老师也总有人喜欢这一款,所以还是自己喜欢最重要。 💪树洞宗旨(修车圈的大众点评): 致力于给普通狼友创建一个发声的平台,这里没有控评、自由开源,去中心化。树洞希望成为您的CJ指南、一个本地修车圈的情报站、一个有趣的吃瓜平台,一个在Telegram中文社区特别的存在! 最后,还是玩的开心最重要! 💣雷报区: 北京 上海 杭州 深圳 广州 🌲导航 | 📒百科 | 🥷🏻情报站 | 👤管理
❤2
1
Channel created
Showing the 11 most recent of 11 posts we hold for @shudongleibao_hz. 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.
Named by 7 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.
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.
@shudongleibao_hz named 2 handles 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.
References a handle that is not a live channel — we have no record it ever was one.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“树洞雷报杭州” (@shudongleibao_hz), 1,670 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/shudongleibao_hz.
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.