Telegram RegisterThe public register of Telegram
Telegram profile photo for 深圳雷师榜

Channel

深圳雷师榜

@szlsbb

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

26,233subscribers

+4,885 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002094277915
TypeChannel
Username@szlsbb
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 November 2026
Measurements held66
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/szlsbb

Topic

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

Growth

21,34826,23323,790.57 August 202616 November 2026
66 measurements spanning 101 days, net +4,885. 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 20,615–26,966 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
16 Nov 2026, 22:4026,233+142
13 Nov 2026, 15:0926,091+200
11 Nov 2026, 02:5925,891+66
9 Nov 2026, 08:0125,825+22
7 Nov 2026, 22:4025,803+45
6 Nov 2026, 21:4025,758+47
5 Nov 2026, 20:5625,711+37
4 Nov 2026, 23:2625,674+31
3 Nov 2026, 21:0625,643+63
2 Nov 2026, 17:4025,580+57
1 Nov 2026, 17:0525,523+32
31 Oct 2026, 19:1925,491+11
30 Oct 2026, 20:5625,480-2
29 Oct 2026, 17:4525,482+21
28 Oct 2026, 17:5625,461+74
27 Oct 2026, 14:1725,387+60
26 Oct 2026, 13:5525,327+50
25 Oct 2026, 12:4825,277+21
24 Oct 2026, 13:0425,256+63
23 Oct 2026, 12:5525,193first reading

Engagement

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

ERR · 30 days
10.7%
avg views ÷ 26,233 subscribers
Avg views / post
2,810
85 posts measured
Reaction rate
0.172%
reactions ÷ views · ER floor
Posts in window
85
of 216 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 74 of 85 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 16 November 2026
Posts held216 (3 August 2026 – 16 November 2026)
Views total238,653
Reactions total373
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 21:11 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

Video runtime
21m 31s
Average length
13s

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

1,341 reactions across 178 posts, in 17 distinct kinds. The most used accounts for 54.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤73254.6%
👍33024.6%
🤣16011.9%
🫡463.43%
🙈231.72%
👏141.04%
😱120.895%
🔥60.447%
🤔40.298%
😁30.224%
😨30.224%
😭20.149%
🙉20.149%
😈10.075%
😡10.075%
🤗10.075%
🥰10.075%

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 191 of the 216 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 1,341 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 216 most recent posts we hold, published 3 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: 6 of 85 posts held from the last 30 days (7.06%) 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).

16 Nov 2026, 08:15 UTC≈1,520 views4 reactionsread 16 November 2026
Photo

伤兵留名:灰烬 雷师花名:酥酥(萝莉) 踩雷时间:2026年11月15日 城市坐标:深圳 罗湖 踩雷支出:来回时间+路费+周末心情 踩雷经历:在某群拍卖的工兵券,本来约的11月14号9点p,妹子接工兵券不情不愿的,还让给定金。我说明了工兵不需要给定,并且找了群管理沟通反馈情况。妹子这才隔了快半小时回复我说14号的9点已经约了pp,让我当天再联系。这个说法摆明是中介不愿意兑半价,我就拿了小号测试了一下约相同的时间,你猜怎么着? 秒回,秒约上,甚至都不用定金。我把聊天截图反馈给群管理,经过群管理协调,妹子给我定15号下午4点。 到了15号下午,不回消息,等快要下午3点才说,要改到晚上9点才能约。我都已经在路上了,难道过去等她五个小时吗?我想大概是中介接到原价单了,我和中介说把来回车费赔了,这事算了。结果她态度极差,还说没让我出发,你自己出发干嘛?聊到这里我已经对她没什么好说的了,不拿工兵的时间当时间,约课不情不愿,随意更改约定时…

👍3❤1

16 Nov 2026, 08:09 UTC≈1,430 views2 reactionsread 16 November 2026
Photo

伤兵留名:佚名 骗子花名:兔兔 被骗时间:2026.11.13 所在城市:深圳 龙华 被骗损失:100定金+路程2h 被骗经历:交了100定金到了指定位置,要交900才能上楼。跟骗子拉扯一番后开车回去了。 骗子TG:@kdjndbs

❤1👍1

16 Nov 2026, 08:07 UTC≈1,380 views6 reactionsread 16 November 2026
Photo

伤兵留名:路明非 雷师花名:诗诗 踩雷时间:11月14日 城市坐标:深圳 光明 踩雷支出:一张半价券和来回路费和3小时时间 颜值身材:跟频道照片完全不一样,用的就是完完全全的假照网图 踩雷经历:去到了发现,完全跟频道不一样,甚至那技师看起来比我还老,反正我肯定不会想着来都来了,虽然真的耗了很久的时间,在此我奉劝各位狼友,避雷光明所有的技师,感觉大部分都是假照,甚至我怀疑他们背后的中介都是同一个,因为在这件事情发生之后,我去问了其他比如中了光明的半价券的,什么光明莹莹也是假照来的,实际就是大妈也是跟频道完全不相符,而且别看他们都没有差评,那是因为根本没人去,频道里面的报告都没几个,全是假报告,感觉光明就是随机发货,全是中介,究极避雷这个地方了,以后再也不会去了 雷师TG @yangmeiiii

👍5❤1

14 Nov 2026, 12:42 UTC≈3,080 views10 reactionsread 16 November 2026
Photo

伤兵留名:开车不喝酒 雷师花名:深圳老王 踩雷时间:2026年11月14 城市坐标:深圳 踩雷支出:22张 踩雷经历:找中介约的一个深圳大圈LS,介绍写得173,实际166,照片7张6张用的是网红图,但是中介强推,说服务和体验以及长相绝对ok,于是相信中介打车一小时到地方,进去后,发现LS确实很白,来都来了给了2200现金,脱衣服后发现老师背后全是小红点,从屁股一路到脖子,当场吓软,走人,但钱是要不回来了。 结尾:现在已经在做检查了 雷师TG @ww6699996

❤5👍5

14 Nov 2026, 10:50 UTC≈2,910 views0 reactionsread 16 November 2026
Photo

伤兵留名:扣你鸡娃 雷师花名: 夏楚楚 踩雷时间:11.13 城市坐标:深圳南山 踩雷支出: 时间加上罚站2h 踩雷经历: 中介,约了8:00,罚站到8:40,完全货不对版,气死了 雷师TG: @xixixi2006

14 Nov 2026, 10:13 UTC≈2,170 viewsread 15 November 2026
Photo

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

14 Nov 2026, 10:13 UTC≈2,210 views2 reactionsread 15 November 2026
Photo

深圳雷师榜|🔥 古鲁特自助烤肉8周年庆,44元实现烤肉自由! 最近古鲁特自助烤肉搞8周年庆活动,只要 44元,肉类、蔬菜、甜品、冰淇淋、小吃、饮料全部随便吃!虽然价格便宜,但食材新鲜度还是不错的。 榜主已经连续吃了一星期了,只能说一个字:爽! 每次都是扶墙进、扶墙出,吃得那叫一个满足。 这个价位也就不惦记什么牛肉了,榜主每次过去基本都是以五花肉为主。先把五花肉烤到两面没有血色,再拿剪刀剪成小块,继续烤到表面微微焦脆,最后裹上麻酱,配上生蒜片,入口嘎嘎香! 每次过去少说也要干掉一斤多肉、半斤小吃,再配上四五瓶饮料,主打一个吃到尽兴。 说实话,榜主特别喜欢自助烤肉这种氛围,自己动手,边烤边吃,想吃多少就吃多少。尤其是44元这个价格,能吃得这么满足,确实没什么好挑剔的了!😋

❤2

14 Nov 2026, 09:51 UTC≈2,370 views3 reactionsread 15 November 2026
Photo

伤兵留名: qqqq 雷师花名: 许如意 踩雷时间: 2026.11.14 城市坐标: 深圳 前海凯y 踩雷支出: 损失100定+罚站20分钟 踩雷经历:观望了很久的一个所谓的空姐,看着一直声称真空姐想着贵点也就认了,约了4点半 pp 2500,结果到了之后特别不耐烦一直说有事,然后还说社区检查,笑死,等了20分钟走了。做中介都不会做,态度很差,罚站也没有补偿方案,好像别人时间路费不值钱 雷师TG @Szxzy0

❤3

13 Nov 2026, 06:27 UTC≈2,500 views8 reactionsread 14 November 2026
Photo

伤兵留名:黄鹤 雷师花名:CC 踩雷详情:今天高高兴兴,准备出击,约了cc老师,没看清楚价格,以为是1800pp,直接就约了,约好了拍小视频加300,给了100定金,到了以后又给了2000现金,干完了第一次以后,就去买烟,然后又给了200,然后她就准备走了,我说不是两次吗,她说是一次啊,我瞬间心里面就不高兴了,很奇怪2300干一次,后来我才发现他是2100的pp,原来的车震加500他没给我说,我要是知道以她的个人条件加500我也不来,后来我又提议给她再加300,她说不行,要再加500,然后我就让她回去了,我还送她到他家楼下 雷师条件:有轻微狐臭,翘嘴,辣条音 总结就是:1100干一次,500的车震费用,拍小视频300,然后我不知道的200小费(给钱的时候她以为是我多给小费),和我主动给的200,2300干一次,小视频我也不准备发出来了,恶心死了,实锤这个是个中介妹 雷师TG @ccqaq1

👍5❤3

13 Nov 2026, 06:11 UTC≈2,480 views3 reactionsread 14 November 2026
Photo

该雷师真是又抽象又双标!既然加钟可以随心所欲,那还约什么时间?还好意思要求别人不要迟到?规矩全是你定的,想怎么改就怎么改,合着规则只约束别人,不约束自己是吧? 雷师TG @xiliyou 二进宫

👍2❤1

12 Nov 2026, 07:21 UTC≈3,650 views8 reactionsread 14 November 2026
Photo

伤兵留名:梦境织影 雷师花名:西丽优优 踩雷时间:2026.11.11 城市坐标:深圳 南山 西丽 踩雷支出:来回路费 踩雷经历:群里换的半价,原价700p,半价350,老师说要400,想想也就同意了,还交代了不要迟到不要鸽子。8.22给我发有人包时要求我换时间,我已经明确说了我人在路上再半小时就到了,让她去取消那个要临时加单的。出击本来就是这样的啊,你真喜欢又想加时间也得看老师后面还有没有客人,如果有肯定加不了啊,如果老师是自聊的大概率也不会这样乱安排,而且也一定会非常诚恳道歉或者让前面那个人走了。我个人猜测还是中介为了赚大单放弃了小单。本来看频道图都是AI生图就很忐忑了,这下好了不用出击了。老师还说350p不加价,尼玛本来就是350p啊,说的好像天大的便宜一样。现在非常生气,兄弟们自行斟酌。 雷师TG @xiliyou

❤8

11 Nov 2026, 06:49 UTC≈4,550 views3 reactionsread 14 November 2026
Video

伤兵留名: henry 雷师花名: 爱你的呆呆 踩雷时间: 11月9日 所在城市: 深圳 南山 踩雷支出: 900 踩雷经历:俩姐妹,约了想要的那个,到了之后和我说想要的姐妹卸妆睡了,给我安排了妹妹。付完钱脱衣服后发现是个猪排,很肥肚子一堆游泳圈。最重要的是没有服务,口都口不硬人😭。我插两下 看着她死鱼那样 我就软了 雷师TG @wstty2

❤3

Showing the 12 most recent of 216 posts we hold for @szlsbb. 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 8 posts on @szlsbb 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
26 August 2026
Most recent seen missing
26 October 2026
Median time before seen missing
31 hours
Seen missing in the last 30 days
3

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

“深圳雷师榜” (@szlsbb), 26,233 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/szlsbb.

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.