Telegram RegisterThe public register of Telegram
Telegram profile photo for 绍兴抓龙筋科普好评

Channel

绍兴抓龙筋科普好评

@sxzlj666

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

272subscribers

+257 since we began measuring on 23 October 2026

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

Register entry

Telegram ID-1003892246625
TypeChannel
Username@sxzlj666
Created22 October 2026 — measured — dated from the channel’s first post
First recorded23 October 2026
Last confirmed live6 November 2026
Measurements held4
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/sxzlj666

Growth

15272143.523 October 2026 — 15 subscribers24 October 2026 — 15 subscribers30 October 2026 — 56 subscribers6 November 2026 — 272 subscribers23 October 20266 November 2026
4 measurements spanning 14 days, net +257. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Nov 2026, 08:21272+216
30 Oct 2026, 08:3656+41
24 Oct 2026, 04:2915no change
23 Oct 2026, 19:2215first reading

Engagement

5 posts held, back to 22 October 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
49.4%
avg views ÷ 272 subscribers
Avg views / post
134
4 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
5
of 5 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 23 October 2026
Posts held5 (22 October 2026 – 23 October 2026)
Views total537
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken23 Oct 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
14s

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.

Recent posts

Telegram’s own ‘edited’ marker: 1 of 5 posts held from the last 30 days (20.0%) 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).

23 Oct 2026, 13:52 UTC65 viewsread 23 October 2026

要上门,不愿意先付车费的就不要联系啦,浪费彼此时间!!

23 Oct 2026, 06:48 UTC164 viewsread 23 October 2026
Photo

🔥泰式古法抓龙筋🥰 龟责潮喷 寸止😘 丝足🦵延时脱敏💋 强制榨精 前列腺保养🫦 无限火力 控射训练😇 体验男高 潮P💦 重振男人雄风❤️ 绍兴最牛逼的抓龙筋首家 预约:@sxzlj111 频道:https://t.me/sxzlj666 交流群:https://t.me/sxzlj888 双向:@shaoxing123bot 地址:#绍兴 #柯桥区 #绍兴抓龙筋 #柯桥抓龙筋

22 Oct 2026, 13:51 UTC165 viewsread 23 October 2026
Video

#绍兴抓龙筋 #泰式抓龙筋 #前列腺保养 #按摩SAP 抓龙筋的独特魅力: 抓龙筋是一门融合中医经络与泰式按摩精髓的技艺,专为男性私密健康设计,不仅疗愈身体,更点燃内心深处的自信与活力。 抓龙筋五大核心益处: 1 改善前列腺健康 抓龙筋通过精准按摩三角区与前列腺,促进血液循环,缓解前列腺症夜尿频繁、尿液不畅等困扰。长期坚持可增强前列腺功能,减轻酸胀感,告别私密部位的隐秘不适,重拾身体的掌控感。 2 提升性功能持久力 独特的脱敏技法温和调节敏感区域的神经末梢,显著延长亲密时刻的时间,改善早泄问题。体验后,男性士能在亲密生活中更持久、更自信,享受更深层次的愉悦。 3 优化敏感度 通过细腻手法唤醒私密部位的神经末梢,抓龙筋实现敏感度的理想平衡.既不过于敏感,又能充分享受亲密时刻的愉悦,如星光股持久闪耀,提升亲密体验的质量。 4 释放压力,深度放松 结合精油芳香SPA按摩,抓龙筋缓解都市生活的焦虑与疲惫。酥麻的云端感受仿佛让您漂浮于…

22 Oct 2026, 13:47 UTC143 viewsread 23 October 2026
Photo

正宗泰式+国内情调,舒适到飞起! 我们的抓龙筋手法,100%正宗泰式,精准刺激三角区、前列腺、精索,促进血液循环,疏通淤堵,专为男土解决前列酸胀、泄、萎等频恼!但光正宗可不路,我们还迎合国内老板们的喜好,加入了异情调的温柔手法,让每一次按压都如星光流转,酥麻又不失温暖!!告别单调的传统按摩,我们的脱敏技法、三起三落节奏、前高引导层次分明,舒适感拉满,健康与享受两不误! 不断更新,只为更好的你! 走到现在,一直在钻研、完善,我们不仅保留泰式古法的精髓,还根据国内男土的需求优化手法节奏,让疗愈更贴心更到位!无论是想改善私健康,还是缓释压力、点燃自信,我们都用心对待每一位老板,等你来体验,感受这份专展男士的健康星光! 最后说一句 绍兴的帅气老板们,抛弃"打飞机"的杂念,抓龙筋是正宗的养生疗愈,专注前列腺养护、锻炼时间提开,我们用专业和热情,带你体验不一样的私密健康之旅,快来预约吧,健康与舒适,一个都不能少! #绍兴抓龙筋 #泰式SAP…

Showing the 5 most recent of 5 posts we hold for @sxzlj666. 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 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 6 November 2026 — this entry's latest reading, not the date you are reading this.

“绍兴抓龙筋科普好评” (@sxzlj666), 272 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/sxzlj666.

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.