Telegram RegisterThe public register of Telegram
Telegram profile photo for 苏州参考馆

Channel

苏州参考馆

@olddriver_subbb

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry

33,826subscribers

+147 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-1001944679344
TypeChannel
Username@olddriver_subbb
Description群主 @olddriver_sub 找我上榜 @szgod_bot 苏州公榜群 https://t.me/olddriver_szb 我是专属机器人🤖 旗下: 参考 公榜 评价 足浴 色色 五大频道,投稿|投诉提交:时间 地点位置人物 TG号 TG名称 店家商户名 ,消费记录 (账单 导航记录 聊天 支付任意一作为参考) 起因 经过 结果 抓住重点经过简单描述, 我收到会第一时间回复你。感谢信任 愿您我真诚到永远
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live20 October 2026
Measurements held43
Confirmed unchanged1 time, most recently 20 October 2026
On Telegramt.me/olddriver_subbb

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 9 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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.

Growth

33,62533,85333,7397 August 2026 — 33,679 subscribers7 August 2026 — 33,679 subscribers8 August 2026 — 33,662 subscribers9 August 2026 — 33,654 subscribers11 August 2026 — 33,645 subscribers12 August 2026 — 33,653 subscribers13 August 2026 — 33,643 subscribers14 August 2026 — 33,625 subscribers15 August 2026 — 33,628 subscribers17 August 2026 — 33,630 subscribers18 August 2026 — 33,625 subscribers19 August 2026 — 33,629 subscribers20 August 2026 — 33,650 subscribers21 August 2026 — 33,666 subscribers22 August 2026 — 33,690 subscribers24 August 2026 — 33,672 subscribers25 August 2026 — 33,666 subscribers26 August 2026 — 33,665 subscribers27 August 2026 — 33,669 subscribers28 August 2026 — 33,675 subscribers29 August 2026 — 33,671 subscribers30 August 2026 — 33,680 subscribers31 August 2026 — 33,674 subscribers1 September 2026 — 33,684 subscribers3 September 2026 — 33,694 subscribers4 September 2026 — 33,692 subscribers6 September 2026 — 33,676 subscribers10 September 2026 — 33,805 subscribers12 September 2026 — 33,811 subscribers14 September 2026 — 33,818 subscribers15 September 2026 — 33,840 subscribers17 September 2026 — 33,853 subscribers29 September 2026 — 33,780 subscribers5 October 2026 — 33,781 subscribers9 October 2026 — 33,782 subscribers13 October 2026 — 33,800 subscribers14 October 2026 — 33,804 subscribers15 October 2026 — 33,805 subscribers16 October 2026 — 33,794 subscribers17 October 2026 — 33,798 subscribers18 October 2026 — 33,805 subscribers19 October 2026 — 33,808 subscribers20 October 2026 — 33,826 subscribers33,8267 August 202620 October 2026
43 measurements spanning 74 days, net +147. 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 33,591–33,887 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 43
Measured (UTC)SubscribersChange
20 Oct 2026, 16:1933,826+18
19 Oct 2026, 17:4933,808+3
18 Oct 2026, 18:1833,805+7
17 Oct 2026, 14:3933,798+4
16 Oct 2026, 15:4533,794-11
15 Oct 2026, 18:2733,805+1
14 Oct 2026, 21:2833,804+4
13 Oct 2026, 15:3833,800+18
9 Oct 2026, 17:2033,782+1
5 Oct 2026, 11:1633,781+1
29 Sept 2026, 13:2033,780-73
17 Sept 2026, 20:3833,853+13
15 Sept 2026, 20:1733,840+22
14 Sept 2026, 02:1633,818+7
12 Sept 2026, 06:4133,811+6
10 Sept 2026, 04:1733,805+129
6 Sept 2026, 18:5833,676-16
4 Sept 2026, 10:1533,692-2
3 Sept 2026, 00:5433,694+10
1 Sept 2026, 22:3833,684first reading

Engagement

56 posts held, back to 23 June 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 132 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
26.9%
avg views ÷ 33,826 subscribers
Avg views / post
9,090
4 posts measured
Reaction rate
0.061%
reactions ÷ views · ER floor
Posts in window
4
of 56 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 8 October 2026
Posts held56 (23 June 2026 – 8 October 2026)
Views total36,360
Reactions total22
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Oct 2026, 23:09 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
≈3,010
Videos
≈221
Links
≈504

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

771 reactions across 50 posts, in 13 distinct kinds. The most used accounts for 32.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤25132.6%
😱16921.9%
🤡10113.1%
👍8410.9%
🤬344.41%
😁324.15%
👎283.63%
🖕283.63%
🤣162.08%
🔥131.69%
🎉81.04%
🤮60.778%
💯10.13%

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

Measured over the 56 most recent posts we hold, published 23 June 2026 to 8 October 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

8 Oct 2026, 09:01 UTC≈9,280 views10 reactionsread 20 October 2026

===== 评论区 ===== Vires: 这种为啥要曝光地址呢,是不是有病啊 Vires: 你的也算大,谁给你的自信啊 妄自(每周一击联盟): 我真的想笑还有偷拍的暴地址的吗 嫖娼不需要素质的……觉得贵的谁让你去了 只撸管不做爱: 人美逼受罪😂 鼠鼠特工(真抓实干): 景慧这种暴露地址,去过的狼友不得吓死😂 Chill: 舔狗真几把多 别秒我🌝『及时行乐的黄Sir🫡...: 国庆期间差点就去了🥲还好没去,不然哪天被顺藤摸瓜了🤣 James: 偷拍+暴地址确实是有毛病。 sleeping: 牛逼 Norbert Evans: 挺好的就应该把地址发出来 不然人家不做了群里老哥找对象万一接盘了彩礼啥的还得给

❤10

8 Oct 2026, 09:01 UTC≈9,200 views5 reactionsread 20 October 2026
Photo

#景慧 @free70124 #正荣国领77幢 # 800P 1500PP #颜值确实不错,其他就很一般,#胸很小 #皮肤不滑,特别胸前有红疹一样的点点,看着头皮发麻,最想吐槽的就是 #逼太松了,我的也算大的了,插进去一点感觉没有,纯纯日空气,舌吻倒是没停,太松了后面软了,8百体验很一般,典型的人美逼遭罪,太松了

❤5

8 Oct 2026, 08:50 UTC≈8,890 views2 reactionsread 20 October 2026

===== 评论区 ===== Vires: 真实名啊 手机号不像 你老公在家吗 Ba: 哪个老师 爱吃 折耳根: 苏州狼友咋这么暴躁??成都,重庆的圈子其乐融融,多好咋 zhu tao: 树洞上面有过节奏。 ouuvvv: 好奇 这信息都是从哪里看到的 王也青 Q: 怎么每次都这个手机号啊,鸡头啊? faiz: 真的假的? Jessica Thompso...: 老师没有进去。举报人不是人、傻逼,怎么不去四、垃圾

❤2

8 Oct 2026, 08:50 UTC≈8,990 views5 reactionsread 20 October 2026
Photo

#群友实名举报 #狼友实名举报 #查处案件涉及5人 #婉儿 #九盛里璟园 #九盛里璟园20栋1单元2302号 #受理单位:郭巷派出所 #被抓被举报八月份记录

❤5

10 Sept 2026, 16:00 UTC≈19,100 views6 reactionsread 20 October 2026
Photo

#无锡市 #梁溪区 #红豆人民路9号 # 370元 95 BT 半套 中项 口爆 毒🐉 #店名简悦 (美团 高德地图都能搜到)

❤6

10 Sept 2026, 16:00 UTC≈20,100 views10 reactionsread 20 October 2026

===== 评论区 ===== b bi: @jogle_channel_bot妞好看吗,有微信吗? b bi: 我看美团25年后就没人评论了 G G: (➤b bi) 这家店身处闹市 有点危险

❤8👍2

10 Sept 2026, 15:25 UTC≈17,200 views9 reactionsread 20 October 2026

===== 评论区 ===== 骚包张奶子: 有幸去过,丑的一比,完全没有身材可言,皮肤很黑也不光滑服务也很潦草, 白桃: 在忙的时候也不上tg,没有及时回复你确实对不起。没有鸽你,没有给准确的位置,就没有约成功。 檀木: 那你可以什么呢?找个像样的借口不行吗 Shi Jordan Ⅱ: (➤白桃) 哎呦,当事人出来了,可以就是可以,不可以就是不可以,臭逼自己不会合理安排,浪费别人时间,找什么借口 Shi Jordan Ⅱ: (➤AAAAAA 五a笔刷) 龟男滚,你帮他说话也不会有免费臭逼草的 Shi Jordan Ⅱ: (➤AAAAAA 五a笔刷) 论你妈逼,你这个乌龟竟然还长膝盖,那么爱下跪。从来没有什么报地址才算约成功的规矩,报地址是妓女的义务,不报就是她的问题,从来只有收钱的迁就付钱的,付钱的迁就收钱的算什么道理? 叶落葬红尘: 我去感觉还可以,挺不错的 要吃鱿鱼吗: (➤骚包张奶子) 见人下菜典型,黑 没什么服…

❤9

10 Sept 2026, 15:25 UTC≈14,900 views2 reactionsread 20 October 2026
Photo

#被鸽子🕊️ #14点57分到15点15分 明确确认约的19点,17点04分到18点13分追问地址,被告知约满了 #提前约好时间,一直不发地址,距离约好的时间不到一小时,突然说约满了,直接把我鸽了 #白桃 @baitaoszly

❤2

10 Sept 2026, 02:58 UTC≈15,000 views6 reactionsread 20 October 2026

===== 评论区 ===== shuai: 厉害 霸王 🦍: 防内射保证金😂 We Ew: 苏州也有我刚被骗,一个叫西米的,处男破处还要有保证金 Calandra Kobler: 张家港有没有靠谱的店呢? 恢恢: 人都没见到就付钱啊,你记住个人的见面付钱,去店里的玩完付钱 刘璇 玑: 还有个江阴第1茶楼,我去过了,也是骗子

😁5❤1

10 Sept 2026, 02:56 UTC≈15,300 views34 reactionsread 20 October 2026
Photo

@GOGOBMW456 #避坑 #避雷 #鸡头群 #被骗188元定金 #投稿避雷张家港修车大队这个组所有的人,这个群全是骗子,全是被骗🐔头在聊天,没有女的真人,各种手段骗你交定金,开门前还要收费,这个组创立到现在全是骗子。前两天在另一个群里看一个兄弟同样被骗我的人又被骗了,发出来让大家避雷一下,最好大家能把这个组举报了

👍20❤6🤡6😁2

8 Sept 2026, 06:22 UTC≈16,500 views131 reactionsread 20 October 2026
Photo

#星健中心4号楼206室 #徐阳花园13幢1503室 办事单位 : 苏锦派出所 澄阳派出所 共计三位电报老师 三位狼友 , #苗苗 #卡戴珊 #陈音音 六月被抓记录 芙儿 洛儿

😱109❤9😁5👍4👎4

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

@olddriver_subbb edited 6 posts 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
22 August 2026
Most recent edit
19 October 2026

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

“苏州参考馆” (@olddriver_subbb), 33,826 subscribers as measured 20 October 2026. Telegram Register, tgregister.com/channel/olddriver_subbb.

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.