Telegram RegisterThe public register of Telegram
Telegram profile photo for 苏州硬了么公开性息

Channel

苏州硬了么公开性息

@SZYLMgongkai

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

18,520subscribers

+2,236 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-1002344489022
TypeChannel
Username@SZYLMgongkai
Description频道更新苏州奇闻轶事以及骗子公开... 👙认证老师 → @sznewls 👙新秀老师 → @suzhouxinxiu 📢 客户反馈 → @SZZZJreport 💬 进群互动玩抽象 → @SuZhoulang 硬了么不敢承诺零踩雷,但我们一直在做的,就是尽量让你在百人斩的途中,99次都能安全下车。
CreatedBetween 1 September 2024 and 31 March 2025 — 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/SZYLMgongkai

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 53% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 2 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@suzhouxinxiu/131221 Jul 2026, 09:15 UTC@SZYLMgongkai/591 · this entry19 Aug 2026, 19:07 UTC1.0029 days
@suzhouxinxiu/154323 Aug 2026, 07:10 UTC@SZYLMgongkai/598 · this entry23 Aug 2026, 07:10 UTC1.00under a minute
@suzhouxinxiu/157925 Aug 2026, 11:37 UTC@SZYLMgongkai/613 · this entry25 Aug 2026, 11:37 UTC1.00under a minute
@suzhouxinxiu/17243 Sept 2026, 08:53 UTC@SZYLMgongkai/647 · this entry3 Sept 2026, 08:53 UTC1.00under a minute
@suzhouxinxiu/27636 Nov 2026, 15:23 UTC@SZYLMgongkai/847 · this entry6 Nov 2026, 15:23 UTC1.00under a minute
@suzhouxinxiu/284810 Nov 2026, 13:47 UTC@SZYLMgongkai/874 · this entry10 Nov 2026, 14:17 UTC1.0030 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@suzhouxinxiu7 (7/7 hand-verifiable sample passed)1.00under a minute@suzhouxinxiu (4–3)
@SZnewls7 (7/7 hand-verifiable sample passed)1.00under a minutethis entry (4–3)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 7 of the 7 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 56 comparable posts for this entry, running 7 July 2026 to 16 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the key clone_mutual, last confirmed 17 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

16,28418,72117,502.518,5207 August 202616 November 2026
66 measurements spanning 101 days, net +2,236. 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 15,918–19,087 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, 12:4018,520+75
13 Nov 2026, 03:4718,445+60
10 Nov 2026, 17:4518,385+91
9 Nov 2026, 05:5818,294+66
7 Nov 2026, 22:2218,228+50
6 Nov 2026, 19:1718,178+33
5 Nov 2026, 21:1018,145+31
4 Nov 2026, 20:4618,114+43
3 Nov 2026, 16:5818,071+14
2 Nov 2026, 19:2618,057+11
1 Nov 2026, 22:0618,046+13
31 Oct 2026, 22:4518,033+28
30 Oct 2026, 23:4818,005+18
30 Oct 2026, 00:4617,987+34
29 Oct 2026, 01:1117,953+34
27 Oct 2026, 23:3117,919+28
26 Oct 2026, 23:0017,891+30
26 Oct 2026, 00:4917,861+22
25 Oct 2026, 01:1717,839+4
24 Oct 2026, 03:0617,835first reading

Engagement

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

ERR · 30 days
12.7%
avg views ÷ 18,520 subscribers
Avg views / post
2,360
28 posts measured
Reaction rate
0.118%
reactions ÷ views · ER floor
Posts in window
28
of 103 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 17 of 28 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 held103 (7 July 2026 – 16 November 2026)
Views total65,949
Reactions total54
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 21:44 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
271
Videos
4
Links
33

Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
35s
Average length
35s

Measured directly from 1 video 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

265 reactions across 55 posts, in 10 distinct kinds. The most used accounts for 75.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤19975.1%
👍4115.5%
😭114.15%
😡41.51%
👏31.13%
🤯31.13%
💊10.377%
💯10.377%
😁10.377%
🤣10.377%

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

Measured over the 103 most recent posts we hold, published 7 July 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: 9 of 28 posts held from the last 30 days (32.1%) 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, 15:06 UTC785 views0 reactionsread 17 November 2026
Photo

⚔️ 【EXP阵营争霸赛|新赛季正式开启】 新赛季全面改版,本次仅设立两大阵营,由两位队长正面交锋! 夏目队 🆚 水漫姑苏队 本赛季取消多队混战,改为双队巅峰对决! 所有成员通过完成每日、每周任务获取 EXP,为所属阵营积累贡献,争夺赛季冠军。 【本赛季奖励】 冠军队伍将获得专属荣誉,带队夺冠的队长额外奖励 500元软妹币! 【参与方式】 机器人:@suzhouylmgamebot 参与方式: 私聊机器人发送 /start 加入随机队伍 领取每周任务 回群完成任务、赚取 EXP 本赛季拼的不只是个人实力,更是整个队伍的凝聚力! 两位队长已经就位,接下来就看各位狼友站哪边了。 本赛季改动:叛离原生家庭所需的EXP更改为1500EXP,且叛离原生家庭的1500EXP将不会留在原生家庭,1500EXP将会被77私吞。以及抽奖几率更新,榜十的几率较上个赛季增加了2%-5%,500以下减少了2%-5%;以及升级所需的EXP上调; 夏目…

16 Nov 2026, 07:07 UTC928 views1 reactionsread 17 November 2026

本次队伍赛季已经圆满结束!开启下一个赛季! ⚔️ 【阵营争霸赛|小队长重新招募】 新一轮 EXP 阵营争霸赛即将开启,现面向全群重新招募各阵营小队长! 队长职责: 招募队员、组织任务、带领阵营冲击 EXP 排行榜第一。 冠军奖励: 带队夺冠的小队长,额外奖励 500元软妹币! 有实力、有号召力、愿意带队的狼友,欢迎报名! 报名联系:@suzhouyinglemebot 这次不仅争荣誉,更争真金白银! 本次赛季已经结束,继续做任务的exp会被清空,请不要继续做任务

❤1

15 Nov 2026, 13:15 UTC≈1,170 views0 reactionsread 17 November 2026

🚀 【全新版本预告|机器人系统全面升级】 兄弟们,这次真的要放大招了! 本次硬了么大出血!机器人迎来一次全面升级,后台系统、运行架构及功能体验全部焕新! 但最重要的是:本次升级采用无感迁移,大家几乎不需要重新适应! 原来的操作方式、使用习惯、功能入口全部保持不变,还是熟悉的配方,还是熟悉的操作。 本次重点升级内容: 🔥 一、机器人系统全面升级 底层架构重新优化,运行更加稳定,功能体验进一步提升。 🎮 二、全新游戏系统正式加入 新增游戏大厅,后续还会持续更新更多游戏玩法。 💎 三、最重磅的升级来了! 以后成员可以直接使用群内积累的 米青作为游戏余额,在本群上手 PG 游戏!准备好成为 PG小子 了么! (原有米青和金币都会无缝继承) 这次不只是换了个新系统,而是给整个群增加了一套全新的娱乐体验。 老功能照旧,新玩法上线。 兄弟们,准备好迎接新版本了吗? 新系统即将登场,敬请期待!

13 Nov 2026, 18:54 UTC≈1,600 viewsread 17 November 2026
Photo

⚡️【S16 决赛竞猜提醒|GEN vs BLG】⚡️ 群置顶的 S16 冠军竞猜正在进行中,还没上车的狼友抓紧了! 👉 点群顶部【置顶消息】按钮即可跳转机器人私聊下注,单人不限额度,赢取的 EXP 自动结算到账并同步计入小队总 EXP,帮队伍更快解锁下一档红包抽奖! ⏰ 今晚(11月15日凌晨 02:00)准时自动封盘,每人仅限一次机会,看好哪队赶紧冲!🔥 下注GEN胜利点我 下注BLG胜利点我

11 Nov 2026, 09:27 UTC≈2,100 views1 reactionsread 17 November 2026

由于原积分机器人目前正在维护,积分功能暂时由其他机器人接替使用。 ⚙️ 临时规则如下: 1️⃣ 发言规则保持不变,原有积分获取方式照常执行。 2️⃣ 每日积分获取上限仍为 500分。 3️⃣ 积分查询方式不变,依旧使用 「米青」 查询。 4️⃣ 待原机器人修复完成后,将统一把大家在临时机器人中积累的积分转移至原机器人数据中。 ⚠️ 请大家放心,临时更换机器人不影响现有积分规则,后续会统一处理数据转移。 感谢大家的理解与配合!

❤1

11 Nov 2026, 07:10 UTC≈2,060 views1 reactionsread 17 November 2026
Photo

报告功能已经恢复,直接发送 写报告 给资源查询机器人 @SuzhouSearchbot 就可以写,但是目前没有米青奖励,另外所有的功能都可以用,但是需要自己手打字发给机器人 比如:写报告/找老师 /附近/找报告/出勤 我的报告/机器人教程/出鸡指南/狼友印象 全部需要自己手动输入才可以唤醒机器人!!

❤1

10 Nov 2026, 14:17 UTC≈1,970 views2 reactionsread 17 November 2026

🐺 【硬了么|临时约课通知】 🤖 正值机器人集体罢工期间,但是不能耽误各位狼友出击! 🔥 今日正在开课的老师,直接前往: 👉 @suzhouyingleme ✅ 实时查看今日开课信息 ✅ 无需再去榜单逐个查找 ✅ 开课群内即可查看联系方式,直接预约 ⚠️榜单暂停使用,无法在榜单获取老师联系方式,请直接前往实时开课群找老师

❤1👍1

10 Nov 2026, 02:12 UTC≈2,220 viewsread 17 November 2026

正值机器人崩坏之际,我们终于不用再为了那点米青绞尽脑汁地扯犊子,也不用为了完成任务硬凑话题了。 兄弟们,终于可以卸下积分的枷锁,敞开心扉,有啥说啥! 许久未曾交心,今日咱们不谈米青,只谈兄弟情义! 另外,榜单联系方式即将陆续恢复! ⚠️ 本次仅恢复正在开课老师的联系方式,休息中的老师暂不恢复。 想知道哪些老师正在开课,请前往 @suzhouyingleme 查询。

9 Nov 2026, 08:24 UTC≈2,330 views1 reactionsread 17 November 2026
Photo

小沐验证工兵券竞拍 位置: 姑苏区 竞拍地点:@suzhoulang(群内发小沐竞拍) 时间:11月9日 16.30-18.00

❤1

8 Nov 2026, 04:14 UTC685 viewsread 8 November 2026
Photo

廷廷验证工兵券竞拍 位置: 相城区 (群内发廷廷竞拍) 时间:11月8日 13.40-14.40 小朵验证工兵券竞拍 位置: 姑苏区 (群内发 小朵竞拍) 时间:11月8日 14.45-15.45 招财猫验证工兵券竞拍 位置: @zhaocaimiao7788 姑苏区 (群内发招财猫竞拍) 时间:11月8日 16.00-17.00 瑶一瑶验证工兵券竞拍 位置: @danainailala 姑苏区 (群内发瑶一瑶竞拍) 时间:11月8日 17.10-18.10 甜甜圈验证工兵券竞拍 位置: @tiantianquanx 姑苏区 (群内发甜甜圈竞拍) 时间:11月8日 18.20-19.20

7 Nov 2026, 11:34 UTC≈2,590 views1 reactionsread 17 November 2026

🚨 阵营洗牌即将开启 当前各阵营的 EXP 差距已经达到重组条件。 为了避免强弱差距持续扩大,也让后续阵营任务更公平、更有悬念,系统将根据当前队伍 EXP,对全部成员进行一次重新分配。 旧阵营的故事暂告一段落, 新的队友和对手即将出现。 这不是结束,而是新一轮阵营之战的开始!⚔️

❤1

7 Nov 2026, 08:35 UTC616 views1 reactionsread 7 November 2026
Photo

小猫验证工兵券竞拍 位置: 姑苏区 竞拍地点:@suzhoulang(群内发小猫竞拍) 时间:11月7日 16.30-18.00

❤1

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

@SZYLMgongkai edited 3 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
18 August 2026
Most recent edit
5 November 2026

Posts recorded as deleted after publishing

We recorded 9 posts on @SZYLMgongkai 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
8 August 2026
Most recent seen missing
5 November 2026
Median time before seen missing
24 hours
Seen missing in the last 30 days
5

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

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.

“苏州硬了么公开性息” (@SZYLMgongkai), 18,520 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/SZYLMgongkai.

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.