Telegram RegisterThe public register of Telegram
Telegram profile photo for 红双喜俱乐部《车库》

Channel

红双喜俱乐部《车库》

@hsx66889

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

3,171subscribers

+1,217 since we began measuring on 16 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1003816170365
TypeChannel
Username@hsx66889
CreatedBetween 1 February 2026 and 30 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded16 August 2026
Last confirmed live7 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/hsx66889

Growth

1,9543,2512,602.516 August 2026 — 1,954 subscribers17 August 2026 — 2,195 subscribers20 August 2026 — 2,585 subscribers24 August 2026 — 2,770 subscribers27 August 2026 — 2,771 subscribers30 August 2026 — 2,852 subscribers3 September 2026 — 3,251 subscribers7 September 2026 — 3,171 subscribers3,17116 August 20267 September 2026
8 measurements spanning 22 days, net +1,217. 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”. The vertical axis spans 1,759–3,446 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 11:393,171-80
3 Sept 2026, 01:443,251+399
30 Aug 2026, 21:262,852+81
27 Aug 2026, 11:252,771+1
24 Aug 2026, 06:382,770+185
20 Aug 2026, 15:022,585+390
17 Aug 2026, 10:542,195+241
16 Aug 2026, 19:151,954first reading

Engagement

10 posts held, back to 15 August 2026the 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
8.92%
avg views ÷ 3,171 subscribers
Avg views / post
283
10 posts measured
Reaction rate
0.3%
reactions ÷ views · ER floor
Posts in window
10
of 10 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 4 of 10 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 16 August 2026
Posts held10 (15 August 202616 August 2026)
Views total2,830
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Aug 2026, 19:15 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
30s
Average length
6s

Measured directly from 5 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

4 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
375.0%
👍125.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 4 of the 10 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 10 most recent posts we hold, published 15 August 2026 to 16 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

16 Aug 2026, 18:25 UTC23 viewsread 16 August 2026
Photo

#粥粥 #1200pp #外卖 联系➡️ @hsx8866 双向联系 ➡️ @hsx8866bot 群链接 ➡️ @cdhsx820 报告链接 ➡️ @hsxbdpd1234

16 Aug 2026, 12:34 UTC295 views2 reactionsread 16 August 2026
Photo

🎰 成都红双喜嫩妹御姐洋酒工作室送福利 📮 参与条件: 🪪 必须设置用户名 🎫 加入-成都•红双喜•嫩妹群聊 🎫 加入-红双喜俱乐部《车库》 🎫 加入-BBW成都群➹🧸[大胸大屁股万岁] 🎫 加入-成都狼友出击指南 🎁 奖品内容: 💰️ 66元口令红包 × 2 💰️ 88元口令红包 × 1 💰️ 工作室pp优惠券200元 × 10 💰️ 工作室单p优惠券100元 × 10 💰️ 成都BBW群积分500 × 8 ⚠️ 抽奖说明: ⚠️ 抽奖说明: 1.炸号或中奖后退出抽奖的群组或频道不予兑奖; 2.中奖后需要在开奖后48时内找兑奖人兑奖,超时不予兑奖。 3.奖品均只能本人领取和使用,不可转让不可买卖; 4.工作室优惠券需要在领取后两周内出击使用,逾期则失效。 5、成都bbw群积分领取请联系 @xiaobaicaics 📅 开奖日期:(北京时间) 2026年08月22日 19时00分00秒

1👍1

16 Aug 2026, 06:49 UTC276 viewsread 16 August 2026
Photo

#米米 #15pp #外卖 联系➡️ @hsx8866 双向联系 ➡️ @hsx8866bot 群链接 ➡️ @cdhsx820 报告链接 ➡️ @hsxbdpd1234

16 Aug 2026, 05:37 UTC296 viewsread 16 August 2026
Photo

#玲玲酱 #12pp #东站 联系➡️ @hsx8866 双向联系 ➡️ @hsx8866bot 群链接 ➡️ @cdhsx820 报告链接 ➡️ @hsxbdpd1234

16 Aug 2026, 04:52 UTC311 viewsread 16 August 2026

成都.红双喜俱乐部《车库》 😝🤩😜🤪😄😄😄😄✈️ 🤕 8.16号开课老师列表 阳阳 7p-12pp 公元 伊伊 6p-11pp 泊里中心 波波 1300pp 外卖 巨乳 琳琳 6p-10pp 峰度天下 玲玲 7p-12pp 保利小户 千喜 1200pp 五大花园 巨乳 苏苏6p-1000pp 公元汇🉑 冉宝 1200pp 外卖 灵儿 1200pp外卖 张欣欣 12oopp 外卖 小冰 6p-11pp外卖 可可 1300pp 外卖 林夏 1300pp 外卖 樱桃 1200pp 外卖 娇娇 7p-12pp 誉峰 紫薇6p-11pp 外卖 文文 1200pp 外卖 云朵 1200pp 东郊记忆 荔枝 1200pp 外卖 楠楠 6p-10pp 天府一街 梦琪 1200pp 仁和春天 安然 7p-12pp 外卖 米米 1

15 Aug 2026, 15:26 UTC379 views0 reactionsread 16 August 2026
Photo

#梦琪 #1200pp #仁和春天 联系➡️ @hsx8866 双向联系 ➡️ @hsx8866bot 群链接 ➡️ @cdhsx820 报告链接 ➡️ @hsxbdpd1234

15 Aug 2026, 14:50 UTC343 viewsread 16 August 2026
Photo

#橘子 #12pp #外卖 联系➡️ @hsx8866 双向联系 ➡️ @hsx8866bot 群链接 ➡️ @cdhsx820 报告链接 ➡️ @hsxbdpd1234

15 Aug 2026, 14:50 UTC312 views1 reactionsread 16 August 2026
Photo

#雅典娜 #12pp #外卖 联系➡️ @hsx8866 双向联系 ➡️ @hsx8866bot 群链接 ➡️ @cdhsx820 报告链接 ➡️ @hsxbdpd1234

1

Showing the 10 most recent of 10 posts we hold for @hsx66889. 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 7 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.

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 7 September 2026 — this entry's latest reading, not the date you are reading this.

“红双喜俱乐部《车库》” (@hsx66889), 3,171 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/hsx66889.

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.