Telegram RegisterThe public register of Telegram
Telegram profile photo for 杭州💎橙橙茶馆

Channel

杭州💎橙橙茶馆

@chenchenchaguan1

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

6,577subscribers

+1,600 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003903426553
TypeChannel
Username@chenchenchaguan1
Description全杭州覆盖,一二线城市大圈!中大圈无套/学生妹/洋酒/莞式两次/特服/处/转运珠...spa4T可上门,可包夜! 无定金,满意付妹子! 客服 @su6357069 双向 @su6357069bot
CreatedBetween 1 April 2026 and 6 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live9 November 2026
Measurements held27
Confirmed unchanged1 time, most recently 9 November 2026
On Telegramt.me/chenchenchaguan1

Topic

Adult — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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 the other topics.

Growth

1,2597,6354,4476 August 2026 — 4,977 subscribers6 August 2026 — 4,977 subscribers7 August 2026 — 4,984 subscribers10 August 2026 — 5,049 subscribers13 August 2026 — 5,134 subscribers16 August 2026 — 5,150 subscribers19 August 2026 — 5,187 subscribers23 August 2026 — 5,202 subscribers25 August 2026 — 5,223 subscribers28 August 2026 — 1,259 subscribers1 September 2026 — 5,975 subscribers4 September 2026 — 6,461 subscribers10 September 2026 — 6,844 subscribers14 September 2026 — 7,635 subscribers18 September 2026 — 7,291 subscribers28 September 2026 — 1,758 subscribers6 October 2026 — 1,503 subscribers12 October 2026 — 1,722 subscribers16 October 2026 — 1,728 subscribers19 October 2026 — 2,978 subscribers21 October 2026 — 3,435 subscribers25 October 2026 — 2,990 subscribers28 October 2026 — 6,556 subscribers31 October 2026 — 6,948 subscribers3 November 2026 — 1,769 subscribers6 November 2026 — 3,506 subscribers9 November 2026 — 6,577 subscribers6,5776 August 20269 November 2026
27 measurements spanning 95 days, net +1,600. 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 303–8,591 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
9 Nov 2026, 14:556,577+3,071
6 Nov 2026, 07:443,506+1,737
3 Nov 2026, 06:391,769-5,179
31 Oct 2026, 17:016,948+392
28 Oct 2026, 07:456,556+3,566
25 Oct 2026, 01:292,990-445
21 Oct 2026, 23:403,435+457
19 Oct 2026, 02:372,978+1,250
16 Oct 2026, 02:281,728+6
12 Oct 2026, 20:561,722+219
6 Oct 2026, 01:361,503-255
28 Sept 2026, 20:181,758-5,533
18 Sept 2026, 19:207,291-344
14 Sept 2026, 04:017,635+791
10 Sept 2026, 07:566,844+383
4 Sept 2026, 15:416,461+486
1 Sept 2026, 06:145,975+4,716
28 Aug 2026, 22:541,259-3,964
25 Aug 2026, 19:135,223+21
23 Aug 2026, 02:485,202first reading

Engagement

32 posts held, back to 6 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 9 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.754%
avg views ÷ 6,577 subscribers
Avg views / post
49.6
5 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
5
of 32 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 9 November 2026
Posts held32 (6 August 2026 – 9 November 2026)
Views total248
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Nov 2026, 17:00 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

Photos
≈2,450
Videos
≈656
Links
≈5

Lifetime counters from Telegram’s own channel header, read 9 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
3m 24s
Average length
9s

Measured directly from 24 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.

Recent posts

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

9 Nov 2026, 16:02 UTC11 viewsread 9 November 2026
Video

🏆杭州中高端外围可上门-橙橙🏆 🎆 全杭覆盖💰(700-2500)🎆 ➡️茶馆讨论群:https://t.me/chenchenjiaoliuqun 🐴大圈/中圈/小圈/莞式 /🈚T/学妹/洋酒/ 处女/转运珠/3T/6T spa/空姐/萝莉 🉑上门 🉑课室🉑包夜 🉑包天 🐴全国一二线城市大圈外围🏆活动价 #2500p #一次一小时 🐴频道只做当日推荐, 具体需求可以咨询客服 ,靠谱推荐,满意为止!

Signed TGBot

9 Nov 2026, 05:43 UTC50 viewsread 9 November 2026
Forwarded from @chenchenyefuPhoto

#杭州上城区 #盈澜中心 #杭城超市 #马到成功 #转运珠 麻将输 没中奖 买球输 工作不顺 跟着蜜蜂找花朵 重重打下去 好运来 🥓客服:@su6355955 🥓双向:@su6355955bot 🥓水费:1600p 🈚+300

Signed 橙橙 杭州外围💎

8 Nov 2026, 07:45 UTC66 viewsread 9 November 2026
Forwarded from @chenchenguanshiPhoto

#杭州 #滨江区#极品莞服 #微信飞机 #白雨希 🥓安排 @su6357069 🥓私信限制联系 @su6357069bot 🥓水费顶级莞服两次 #2300pp

Signed 橙橙 杭州外围💎

8 Nov 2026, 07:43 UTC60 viewsread 9 November 2026
Forwarded from @chenchenfankuiPhoto

#杭州上城区 #玲珑山庄 #大圈下放 #洛丽塔 #欲萝圣体 #软软 🉑上门🉑夜🉑🐍吻🉑69🉑制服 #一如既往好评 【验证留名】:可留可匿 【验证日期】:2026.10.11 【妹妹花名】:软软 【妹妹类型】:萝莉 【妹子技能】:69、🐍、制服 【人照几成】:人照一致 【目测年纪】:07 【身高身材】:165 【胸围大小】: 【简评总结】:这个真不错,挺嫩的,人照一致,会聊天衣服多,给好评! 【最终评分】:10 💲水费:#1500p #2300pp 夜4800 🥐私信联系:@su6357069 🥐双向限制:@su6357069bot

Signed 橙橙 杭州外围💎

8 Nov 2026, 07:21 UTC61 viewsread 9 November 2026
Forwarded from @chenchenyefuPhoto

#杭州上城区 #悦玺 #马到成功转运珠 #转运神器5个月 🉑蛇纹🉑69裸吹🉑 夜 🉑转运!! 🥓安排 @su6357069 🥓双向 @su6357069bot 🥓水费 2000p

Signed 橙橙 杭州外围💎

12 Aug 2026, 04:29 UTC17 viewsread 12 August 2026
Forwarded from @chenchenfankuiPhoto

#杭州 #上城 #可蛇纹69 #可🈚套 #可拍视频不露脸可3p #可外出 #小爵爷 🥓安排 @su6357069 🥓私信限制联系 @su6357069bot 🥓水费800p 🈚+300

12 Aug 2026, 04:04 UTC44 viewsread 12 August 2026
Video

👑全国认证高端外围可上门-橙橙👑 💻【安排】 @su6357069 🤚【双向】 @su6357069bot 🗝【频道】 @chenchenchaguan1 📇【群组】 @chenchenjiaoliuqun 🧐 🎆 全国嫩茶 🎆 💵 全杭覆盖700-3000各种类型 🎉全国一二线城市大圈活动价2500p,定期抽奖活动! 🎉 频道只做部分分享 具体需求可以咨询客服 ,给你推荐让你满意的 😀全杭最全资源 最靠谱的中高端外围😀

11 Aug 2026, 10:49 UTC332 viewsread 12 August 2026
Photo

🎰 中大圈橙橙传媒 @su6357069 福利抽奖 📮 抽奖条件: 🎫 加入-杭州💎橙橙茶馆 🎫 加入-杭州💎橙橙茶馆群 🎫 加入-杭州Alex的大奶认证榜单 🎫 加入-杭州Alex教你123 🎫 加入-杭州Alex的小视频 🎫 加入-杭州Alex的大奶新人榜单 🎫 加入-Alex的小视频群2.0 🎁 奖品内容: 大圈优惠劵200 × 3 中圈优惠劵100 × 3 💡 活动说明: 5天内兑奖,炸号超时名额作废 📅 开奖日期:(UTC+8) 2026年08月16日 18时48分12秒

11 Aug 2026, 10:36 UTC196 viewsread 12 August 2026
Photo

#杭州 #刚下水兼职 #上门 #SW #ZF #🉑🚗🐍 #🉑夜 #露露 🥐安排 @su6357069 🥐私信限制联系 @su6357069bot 🥐水费 #1800p夜#5000

11 Aug 2026, 09:35 UTC226 viewsread 12 August 2026
Photo

#杭州 #拱墅区#174大长腿#乐乐 #微信小楼 🥓安排 @su6357069 🥓私信限制联系 @su6357069bot 🥓水费:p1200

8 Aug 2026, 17:25 UTC46 viewsread 9 August 2026
Photo

#杭州 #刚下水兼职 #上门 #SW #ZF #🉑🚗🐍 #🉑夜 #露露 🥐安排 @su6357069 🥐私信限制联系 @su6357069bot 🥐水费 #1800p夜#5000

8 Aug 2026, 12:17 UTC130 viewsread 9 August 2026

杭州 Alex 杭州 狼友之家 杭州 星巴克 杭州 一哥 四群同时上榜担保 信誉保证 放心安排

Showing the 12 most recent of 32 posts we hold for @chenchenchaguan1. 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.

Forward network

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.

Mentions

Named by 10 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 9 November 2026 — this entry's latest reading, not the date you are reading this.

“杭州💎橙橙茶馆” (@chenchenchaguan1), 6,577 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/chenchenchaguan1.

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.