Telegram RegisterThe public register of Telegram
Telegram profile photo for 苏州昆山快乐屋老师榜

Channel

苏州昆山快乐屋老师榜

@suzhoukunshanbang

On this record: Growth · Engagement · What this channel posts · Posts · Cite this entry

228subscribers

+9 since we began measuring on 27 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003705156668
TypeChannel
Username@suzhoukunshanbang
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 September 2026
Last confirmed live4 October 2026
Measurements held3
Confirmed unchanged1 time, most recently 4 October 2026
On Telegramt.me/suzhoukunshanbang

Growth

219228223.527 September 2026 — 219 subscribers27 September 2026 — 219 subscribers4 October 2026 — 228 subscribers27 September 20264 October 2026
3 measurements spanning 7 days, net +9. 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 218–229 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Oct 2026, 20:56228+9
27 Sept 2026, 19:22219no change
27 Sept 2026, 18:48219first reading

Engagement

4 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 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
197.4%
avg views ÷ 228 subscribers
Avg views / post
450
1 post measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
1
of 4 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 18 September 2026
Posts held4 (4 August 2026 – 18 September 2026)
Views total450
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 19:22 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
14s
Average length
7s

Measured directly from 2 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.

Recent posts

18 Sept 2026, 10:50 UTC450 viewsread 27 September 2026
Photo

🧸 老师名称: CC 📍 老师地区: 吴江—昆山市 💰 服务价格:4 快餐 500p 700PP 🏷 老师服务: #舌吻#69 🗝 老师标签: #大胸御姐 👜 联系老师:@cc1314521000

6 Sept 2026, 12:12 UTC771 viewsread 27 September 2026
Photo

🧸 老师名称: 雲朵 📍 老师地区:昆山花桥 💰 服务价格:600p 1200PP 🏷 老师服务: #舔蛋#69 🗝 老师标签: #大胸#嫩妹 👜 联系老师:@yunduozmy

2 Sept 2026, 12:22 UTC744 viewsread 27 September 2026
Photo

🧸 老师名称: 小洋 📍 老师地区: 苏州(可上门昆山) 💰 服务价格:700p 1400PP 🏷 老师服务: #舌吻#69 🗝 老师标签: #大胸#嫩妹 👜 联系老师:@yandjdjd

4 Aug 2026, 09:26 UTC≈1,250 viewsread 27 September 2026
Photo

🧸 老师名称: 初瑶抓龙筋 📍 老师地区: 昆山市 💰 服务价格:398 🏷 老师服务: #抓龙筋#精油 🗝 老师标签: #嫩妹 👜 联系老师:@chuyao147

Signed 小小 嘿

Showing the 4 most recent of 4 posts we hold for @suzhoukunshanbang. 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.

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

“苏州昆山快乐屋老师榜” (@suzhoukunshanbang), 228 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/suzhoukunshanbang.

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.