Telegram RegisterThe public register of Telegram
Telegram profile photo for 王丝的丝足吃牛跌活日记

Channel

王丝的丝足吃牛跌活日记

@xaszcn

On this record: Growth · Engagement · Posts · Citations · Cite this entry

96subscribers

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

Register entry

Telegram ID-1004374807774
TypeChannel
Username@xaszcn
Created29 September 2026 — measured — dated from the channel’s first post
First recorded29 September 2026
Last confirmed live29 September 2026
Measurements held1
On Telegramt.me/xaszcn

Growth

Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.

Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Sept 2026, 18:2296first reading

Engagement

12 posts held, back to 29 September 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
281.0%
avg views ÷ 96 subscribers
Avg views / post
270
8 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
12
of 12 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 1 of 8 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 29 September 2026
Posts held12 (29 September 2026 – 29 September 2026)
Views total2,158
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Sept 2026, 18: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.

Recent posts

29 Sept 2026, 16:42 UTC129 viewsread 29 September 2026

草你妈的 越想越气 举报我你妈死了啊 别让逮到你个畜生

29 Sept 2026, 15:23 UTC297 viewsread 29 September 2026

这几天我会把之前推荐榜上还在岗未上岸的技师挪到新频道,以上岸的就不挪了。 还请兄弟们多多关注,我基本每天都在出击只是一般的不发推荐也懒得给写车评,不过以后本频道出丝足以外楼凤扫街甚至240/340快餐也会更新,以后尽量保证每周5更

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

“王丝的丝足吃牛跌活日记” (@xaszcn), 96 subscribers as measured 29 September 2026. Telegram Register, tgregister.com/channel/xaszcn.

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.