Channel
@csxinwen
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
135subscribers
+0 since we began measuring on 6 October 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003973845017 |
|---|---|
| Type | Channel |
| Username | @csxinwen |
| Description | 分享长沙有趣事和出击报告 |
| Created | Between 1 April 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 October 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 2 |
| On Telegram | t.me/csxinwen |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Oct 2026, 03:22 | 135 | no change |
| 6 Oct 2026, 02:47 | 135 | first reading |
5 posts held, back to 4 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 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 5 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 5 October 2026 |
|---|---|
| Posts held | 5 (4 October 2026 – 5 October 2026) |
| Views total | 3,667 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Oct 2026, 03: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.
Lifetime counters from Telegram’s own channel header, read 6 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
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.
2 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 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 1 of the 5 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 4 October 2026 to 5 October 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.
长沙岳麓区思琪&五道口院长 完整吃瓜事件报告 当事人男方：五道口院长（消费者方），态度强硬、拒不接受小额和解、坚持追责施压 当事人女方：思琪（岳麓区），事件弱势方，全程主动退让和解 第三方：群管理员，中立调解人，全程传话、组织对线、调解矛盾 事件起因： 双方线下私密交易约定400元服务，因女方感冒担心传染、临时拒绝亲密环节引发纠纷。双方各执一词，女方控诉男方揪头发、抢手机、限制人身自由。 男方控诉女方违约、拒不履约。经管理员多轮调解拉扯，女方反复退让，最终全额退还400元全款。但女方全程受委屈、遭遇拉扯争执，内心极度不服，在退款完毕后，直接反手报警处理本次纠纷，成为本次事件最大反转名场面。 趣味总结：从拉扯退款、对线互撕、卑微退让，到全额退款、委屈破防、反手报警，堪称年度最反转线下吃瓜罗生门！ 男方私聊管理员（纠纷初始） 五道口院长主动找管理员维权，不满女方服务问题，不认可对方说辞，坚决要求讨回钱款。直言自己不会白白吃亏…
❤2
老师要与狼友玉石俱焚，你不给我活路，大家就一起毁灭 狼友要求群主下榜 武道下榜了 扶贫也下榜了。老师报警了？
精神小妹 李知恩 跟人做爱的 #激情 视频被传出来 还是个白虎 #网曝门 #纹身 #平胸 #李知恩 #吃瓜
上个月的顺风车我竟然假正经了！
妻子趁丈夫上夜班 把情人带回家doi被拍
Showing the 5 most recent of 5 posts we hold for @csxinwen. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“长沙大事件” (@csxinwen), 135 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/csxinwen.
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.