开课了敬业了。

Channel
上海普陀杉杉紫全能自聊
@linlin116328
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
4,773subscribers
+6 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002250616690 |
|---|---|
| Type | Channel |
| Username | @linlin116328 |
| Created | Between 1 September 2024 and 28 February 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/linlin116328 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 18:04 | 4,773 | +6 |
| 11 Aug 2026, 19:30 | 4,767 | first reading |
Engagement
14 posts held, back to 15 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 2 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 29.7%
- avg views ÷ 4,773 subscribers
- Avg views / post
- 1,420
- 13 posts measured
- Reaction rate
- 0.092%
- reactions ÷ views · ER floor
- Posts in window
- 13
- of 14 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 5 of 13 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 14 (15 July 2026 – 12 August 2026) |
| Views total | 18,444 |
| Reactions total | 8 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 07:34 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
- 5s
- Average length
- 5s
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
8 reactions across 3 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 8 | 100.0% |
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 5 of the 14 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 8reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 15 July 2026 to 12 August 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
还有一个尾单有要约的吗
现在有空了宝子们
开课了老公们雨也停了台风也过了出来嗨呀
台风休息一天
【妹子艺名】: 杉杉紫 【妹子飞机】: @qiaoqiao7777777 【颜值相似度】:9 【身材相似度】:9 【修车水费】:1400 【出击狼友】:深僧 【出击日记】:人照大概给9分,在小区倒是挺好的。妹子很热情,长的很骚很诱惑!进门就看到一双黑丝短裙诱惑力十足啊。进门后老师给了瓶水还寒暄了几句我迫不及待的叫老师开始把,脱完去浴室洗澡老师全自动洗完出来又拿浴巾给我全身擦干。进入房价老师先舔奶头然后主动舌吻(大蟒蛇)然后再帮我口,口了会把老师摸敏感了就直接带套进入主题,刚进去就发现老师的水真多啊。止不住的水多很爽。先传教了一会然后后入。再传教再女上再传教老师一点都没催。后面就123了再去洗澡也是老师全自动我没动手。因为是我的菜进门没看设备,后面看了设备也没问题。抽了根烟走之前老师还特意要了抱抱。有机会继续二刷。 【车评求证】:上海【繁花】狼友聊天群
❤2
♡ 星野严选 ♡ ⌚️ 评价时间:2026-08-04 👩🏻🎓 服务老师:杉杉紫 👨🏻💻 留名:匿名 颜值:9 环境:9 身材:9 态度:10 服务:10 人照:9 综合:9.33 💌 服务过程 : 关注老师好久了,终于有时间了,约好时间,来到小区,进去非常安全,一进门看到杉杉紫的魔鬼身材,看得我想立马上去嗦一口,下身JJ火辣辣的硬挺起来,马不停蹄交水费。客厅沙发上缠绵了好久,舌吻不停的吸我阳气。下面硬的不行就去了浴室,我选了杉杉紫陪浴。 浴室中火辣的身材再次展现在面前,蜂腰美腿,皮肤光滑嫩白,两腿之间肥鲍若隐若现,进入浴室开始帮我搓洗全身,给我的下体打上沐浴露轻轻的搓洗,突然感觉一身的疲惫一扫而空,此刻就全身心的享受杉杉紫姐姐的服务, 下身JJ坚硬如铁,我和老师在浴室边调情边洗澡,感觉像久别重逢的情人,享受着这美妙的时刻。洗完澡后,来到衣柜边,我躺在床上,看着老师在我身前换上情趣内衣,我再次欣赏并抚摸着她诱人的酮…
https://t.me/shxyls/28735?single
https://t.me/yishuzanlanhui/30744
https://t.me/tgxbdd/70421
❤2
https://t.me/xcdd_bd/34212
https://t.me/laoahihaixuan/25318
Showing the 12 most recent of 14 posts we hold for @linlin116328. 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.
Citation-graph rank
Citation-graph rank — 732,278 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
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 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.
Names
Channels on the register whose handles appear in this channel's posts.
@ccxkshww · 5,0391 post野寻·上海修车档案
@chasesh_lsda · 7,1541 post韩信上海精选榜
@hxshjxb · 3,7561 post韩信上海优选榜
@hxshyx · 18,6611 post上海目录老师榜单🧾
@laoahihaixuan · 42,8111 post韩信上海优选榜备用
@shhxyxb · 9651 post上海【学院】总榜
@shxyls · 68,8601 post上海精选榜单报告(中转)
@tgxbdd · 28,6531 post上海修车大队(中转站)
@xcdd_bd · 33,5671 post上海艺术展览会榜单
@yishuzanlanhui · 56,7311 post
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“上海普陀杉杉紫全能自聊” (@linlin116328), 4,773 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/linlin116328.
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.