🔥 每晚直播狂欢|统一开播 直播时间:每晚 19:00-22:00 单次开放 4个直播名额 · 先到先得 名额满后自动排队,有人结束 · 下一位接档开播⚡️ 😄档位一|充值300 - 5000 充值即享 30%加赠 最低 0.6元/注 · 直播至少 30分钟 完成 (本金+彩金)×8倍有效流水 😃档位二|充值5000元+ 充值即享 50%加赠 最低 2元/注 · 直播至少 30分钟 完成 (本金+彩金)×8倍有效流水 直播群号: @xgsm8888 🧧 直播结束再享奖励🎁 🌟全额亏损|救援20%⚡️ 开播后 30分钟内本金全额亏损 平台额外救援 本金20% 🌟盈利完成 开播后 30分钟内完成 规定流水并盈利提款 额外赠送 58元彩金 ⚡️参与要求🌟 1,本人账号充值及游戏,开播前✅😃😄客服 @qtcy888 ✅申请报备;18:30结束报名 2,直播期间须保持正常游戏及互动。【申请的优惠未按要求,影响出款】 3,9…

Channel
999听说文案馆|冷暖自知
@tinsuo899
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
43,459subscribers
+40,650 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1003975354843 |
|---|---|
| Type | Channel |
| Username | @tinsuo899 |
| Created | Between 1 April 2026 and 4 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 25 October 2026 |
| Measurements held | 44 |
| Confirmed unchanged | 1 time, most recently 25 October 2026 |
| On Telegram | t.me/tinsuo899 |
Topic
Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Oct 2026, 14:09 | 43,459 | -849 |
| 24 Oct 2026, 17:30 | 44,308 | -1,757 |
| 23 Oct 2026, 17:47 | 46,065 | -935 |
| 22 Oct 2026, 21:18 | 47,000 | -1,122 |
| 21 Oct 2026, 17:00 | 48,122 | -1,961 |
| 20 Oct 2026, 14:01 | 50,083 | -1,641 |
| 19 Oct 2026, 14:36 | 51,724 | -2,611 |
| 18 Oct 2026, 11:37 | 54,335 | -1,035 |
| 17 Oct 2026, 12:16 | 55,370 | -927 |
| 16 Oct 2026, 15:37 | 56,297 | -467 |
| 15 Oct 2026, 16:06 | 56,764 | -493 |
| 14 Oct 2026, 15:10 | 57,257 | -406 |
| 13 Oct 2026, 03:40 | 57,663 | -360 |
| 8 Oct 2026, 23:16 | 58,023 | -668 |
| 4 Oct 2026, 15:41 | 58,691 | -1,444 |
| 26 Sept 2026, 11:38 | 60,135 | -928 |
| 19 Sept 2026, 11:55 | 61,063 | -162 |
| 16 Sept 2026, 21:01 | 61,225 | -175 |
| 14 Sept 2026, 22:41 | 61,400 | -389 |
| 13 Sept 2026, 08:20 | 61,789 | first reading |
Engagement
837 posts held, back to 4 August 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 166 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 1.55%
- avg views ÷ 43,459 subscribers
- Avg views / post
- 675
- 522 posts measured
- Reaction rate
- 0.125%
- reactions ÷ views · ER floor
- Posts in window
- 522
- of 837 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 9 of 522 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 25 October 2026 |
|---|---|
| Posts held | 837 (4 August 2026 – 25 October 2026) |
| Views total | 352,454 |
| Reactions total | 8 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 25 Oct 2026, 07:27 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
- 1h 19m
- Average length
- 16s
Measured directly from 306 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.
Reaction mix
16 reactions across 15 posts, in 4 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 8 | 50.0% | |
| 👍 | 6 | 37.5% | |
| 🙏 | 1 | 6.25% | |
| 🤣 | 1 | 6.25% |
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 17 of the 837 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 16 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 837 most recent posts we hold, published 4 August 2026 to 25 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.
Recent posts
你也会随着天气变冷吗. 商务合作:@tg37appbot
什么时候才能赚够苹果18pormax 2TB的钱啊 商务合作:@tg37appbot
照顾好自己 你好我就好 不管见不见面 你都在我心里 商务合作:@tg37appbot
看到太多的装和演 内心早不再波澜起伏 只想远离或淡淡的一句算了. 商务合作:@tg37appbot
攀登的过程也许漫长,但巅峰的风景是值得的。 #励志 他们都说我不行 我偏要一条路走到穿 商务合作:@tg37appbot
很认同的一句话: “穷游 富游 都不如少年游,因为欲买桂花同载酒,终不似少年游! 商务合作:@tg37appbot
现在的狗不简单,还会唱歌了 商务合作:@tg37appbot
希望你以后遇到的人都让你觉得错过我是值得的 商务合作:@tg37appbot
太阳出现叫天晴 你的出现叫一见钟情 商务合作:@tg37appbot
#တောင်မိုးတောင် 投稿铃铛:@we13333
不要急着让生活给予你所有的答案,有时候,你要拿出耐心等等。生活的美好,总在你不经意的时候,盛装莅临。 有偿投稿 免费红包 投稿👉 :@hai89788 @hai89788 投稿铃铛: @kaia3535 商务合作:@c37appbot
Showing the 12 most recent of 837 posts we hold for @tinsuo899. 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 3 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.
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.
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 25 October 2026 — this entry's latest reading, not the date you are reading this.
“999听说文案馆|冷暖自知” (@tinsuo899), 43,459 subscribers as measured 25 October 2026. Telegram Register, tgregister.com/channel/tinsuo899.
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.