Telegram RegisterThe public register of Telegram
Telegram profile photo for 上海青浦区风骚老板娘小屋💋

Channel

上海青浦区风骚老板娘小屋💋

@jsjsj130

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

12,607subscribers

+6,025 since we began measuring on 17 August 2026

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

Register entry

Telegram ID-1003058941120
TypeChannel
Username@jsjsj130
CreatedBetween 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded17 August 2026
Last confirmed live3 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 3 September 2026
On Telegramt.me/jsjsj130

Growth

6,58213,76910,175.517 August 2026 — 6,582 subscribers17 August 2026 — 6,582 subscribers18 August 2026 — 6,596 subscribers20 August 2026 — 6,819 subscribers24 August 2026 — 6,747 subscribers27 August 2026 — 7,726 subscribers31 August 2026 — 13,749 subscribers31 August 2026 — 13,769 subscribers1 September 2026 — 13,203 subscribers3 September 2026 — 12,607 subscribers12,60717 August 20263 September 2026
10 measurements spanning 16 days, net +6,025. 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 5,504–14,847 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Sept 2026, 07:4812,607-596
1 Sept 2026, 22:1313,203-566
31 Aug 2026, 23:3813,769+20
31 Aug 2026, 02:3413,749+6,023
27 Aug 2026, 21:257,726+979
24 Aug 2026, 21:176,747-72
20 Aug 2026, 22:086,819+223
18 Aug 2026, 03:116,596+14
17 Aug 2026, 20:456,582no change
17 Aug 2026, 20:306,582first reading

Engagement

69 posts held, back to 16 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.58%
avg views ÷ 12,607 subscribers
Avg views / post
452
65 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
69
of 69 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 2 September 2026
Posts held69 (16 August 20262 September 2026)
Views total29,363
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Sept 2026, 20:24 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
1m 31s
Average length
13s

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

2 Sept 2026, 06:18 UTC373 viewsread 2 September 2026

https://t.me/shhylg02 【所在位置】青浦 【老师艺名】老板娘 【联系方式】 @yingtao170 【验证留名】达文西 【验证时间】9.1日 【上课价位】1700pp 【人照几成】9 【颜值分数】9 【身材分数】9 【课表服务】10 【态度分数】9 【优点缺点】非常喜欢的类型嫩妹加1 【推荐程度】10分 【体验细节】 提前订好酒店就等侯老师到来,自己订的酒店还是安全性拉满,老师进门给我洗干净后我门就开始翻云覆雨起来,立刻就给我吹了一下 吹得太爽了 我立刻叫停 怕交代了 然后来到床上 ls带上了我最爱的丝袜 这个是我提前交代的ls特意给我准备的 先是调情 舔我奶头 然后又给我小弟弟放在老师的嘴巴里 吹了起来 我摸着ls穿着丝袜的大腿 瞬间感觉受不了 然后带好t 撕开丝袜 放了进去 一股暖流传来 很紧 水很多 ls叫声很好听 叫我轻点 越是这样叫我就越兴奋 用力插 可能是太兴奋的原因 没有坚持多久 就

2 Sept 2026, 06:13 UTC336 viewsread 2 September 2026

https://t.me/jiangmemdadui 【所在位置】青浦 【老师艺名】老板娘 【联系方式】 @yingtao170 【验证留名】女枪 【验证时间】9.1日 【上课价位】1700pp 【人照几成】9 【颜值分数】9 【身材分数】9 【课表服务】10 【态度分数】9 【优点缺点】大胸无敌 【推荐程度】10分 【体验细节】 经师兄推荐,果断出击。开门看到门快要炸开衣服的大奶妹,年纪20多,皮肤看着就很白很滑嫩,颜值还不错,小狼也是饿了,立马交钱体验。身高不矮,脱下衣服去洗澡,两手摸上胸前那大胸。擦干净到床上,床上服务很到位,口感很好,舌头灵活,胸压在你身上特别踏实,带上帽子,穿上黑丝,传教士打开脚开日,胸在你面前来回乱晃,看着我都受不了了,俯身下去,连忙啃了几下,可惜最近缺乏锻炼,三二一冲刺出来了。总结: 大奶御姐,身体滑滑香香的,胸是够大的,D得有,匈奴人绝不错过,屁股有肉,但这个身材肯定有点肉,喜欢梨形身材的,颜

2 Sept 2026, 05:03 UTC327 viewsread 2 September 2026
Photo

🤝 我与春风皆过客,你携秋水揽星河🥫😀@yingtao170🤑

1 Sept 2026, 16:03 UTC532 viewsread 2 September 2026
Photo

🍑大哥说我服务好 奖励我吃榴莲😘 榴莲已收到 很开心❤️❤️

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

Mentions

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.

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

“上海青浦区风骚老板娘小屋💋” (@jsjsj130), 12,607 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/jsjsj130.

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.