Telegram 中文圈搜索引擎,积木 JIMU 帮你查询任何您想要的群组、频道(不论公开与私密) 🧩 积木:@jimu · @jimux · @jimuxx 👉 所有入口都能助力提升排名🚀

Channel
湖畔™工作室
@cqhupangzs
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry
8,221subscribers
+234 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001869440709 |
|---|---|
| Type | Channel |
| Username | @cqhupangzs |
| Description | 诚意优选,服务至上! |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/cqhupangzs |
Topic
Other / unclassifiable — 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 65% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Nov 2026, 23:01 | 8,221 | +9 |
| 6 Nov 2026, 13:01 | 8,212 | +11 |
| 31 Oct 2026, 02:11 | 8,201 | +3 |
| 28 Oct 2026, 11:50 | 8,198 | +3 |
| 25 Oct 2026, 11:18 | 8,195 | -4 |
| 22 Oct 2026, 00:40 | 8,199 | -11 |
| 15 Oct 2026, 16:28 | 8,210 | -3 |
| 12 Oct 2026, 12:31 | 8,213 | -13 |
| 5 Oct 2026, 19:00 | 8,226 | +30 |
| 28 Sept 2026, 07:39 | 8,196 | +50 |
| 18 Sept 2026, 20:19 | 8,146 | +44 |
| 14 Sept 2026, 03:00 | 8,102 | +7 |
| 10 Sept 2026, 09:38 | 8,095 | +24 |
| 5 Sept 2026, 04:58 | 8,071 | +28 |
| 1 Sept 2026, 08:54 | 8,043 | +44 |
| 29 Aug 2026, 02:34 | 7,999 | +28 |
| 25 Aug 2026, 21:14 | 7,971 | -12 |
| 23 Aug 2026, 02:46 | 7,983 | +8 |
| 20 Aug 2026, 00:57 | 7,975 | -1 |
| 16 Aug 2026, 20:26 | 7,976 | first reading |
Engagement
39 posts held, back to 28 July 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 36 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 8.78%
- avg views ÷ 8,221 subscribers
- Avg views / post
- 722
- 9 posts measured
- Reaction rate
- 0.119%
- reactions ÷ views · ER floor
- Posts in window
- 12
- of 39 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 6 of 9 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 November 2026 |
|---|---|
| Posts held | 39 (28 July 2026 – 6 November 2026) |
| Views total | 6,497 |
| Reactions total | 7 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Nov 2026, 13:54 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
- 212
- Videos
- 51
- Links
- 36
Lifetime counters from Telegram’s own channel header, read 10 November 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.
- Video runtime
- 1m 30s
- Average length
- 11s
Measured directly from 8 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
13 reactions across 11 posts, in 2 distinct kinds. The most used accounts for 84.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 11 | 84.6% | |
| 🥰 | 2 | 15.4% |
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 14 of the 39 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 13 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 39 most recent posts we hold, published 28 July 2026 to 6 November 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
Telegram’s own ‘edited’ marker: 4 of 12 posts held from the last 30 days (33.3%) 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).
Photo, posted without a caption
湖畔™工作室 pinned «😘😘渝北唐家院子😔😔🈷️😔 头牌嫩妹【紫爱你】7/13🈳🔥 体育学妹【抿抿甜】7/13🈳🔥 人气嫩妹【妖布岛台】8🈳🔥 服务之星【针不戳】8🈳🔥 良家下海【初夏】7/13🈳新人 巨乳护士【咪咪咪】8/15🈳🔥 御萝双修【啾咪】6/11🈳 小嘴抿甜【李郝】6/11🈳 良家少妇【小马叉虫】6/11🈳 170长腿【橙到日】6/11🈳 😤😒🙁😣客服: 澜澜 双向私信:@CQhupanlanlan3_bot 🛍️聊天群:https://t.me/cclm288 欢迎大家进入…»
😘😘渝北唐家院子11🈷️8⃣ 服务之星【针不戳】8🈳🔥 良家下海【初夏】7/13🈳 巨乳护士【咪咪咪】8/15🈳🔥 御萝双修【啾咪】6/11🈳 小嘴抿甜【李郝】6/11🈳 美妇巨乳【笑嘻嘻】7/13🈳 😤😒🙁😣客服: 澜澜 双向私信:@CQhupanlanlan3_bot 🛍️聊天群:https://t.me/cclm288 欢迎大家进入❤️QQ群:1063818716 备用联系方式 防止失联
❤2
推开门,我愣了一下。 屋里没开大灯,只沙发旁的顶部灯晕着暖黄的光。 她原本蜷在沙发里,听见门响,便慢慢站起来——先是微微前倾,手往上轻轻一撑,像只刚睡醒的猫,不慌不忙地舒展开身子。她轻哼着:“你来了!“ 月白的棉布衫子随着动作垂下来,腰身处那道弧线还是活的,温温润润地收进去,又柔柔和和地放出来。她站稳了,我才注意到她脚上那双哈基米毛绒鞋。雪白缎面,绣着浅浅暖色调的花纹,憨头憨脑的。穿在她脚上,配着那身素净的衫子,竟说不出的俏皮,像一幅工笔画里忽然跳进一只高挑哈基米,让人忍不住想笑。 她见我盯着她的鞋看,脚趾在鞋里微微蜷了一下,像个被发现了小秘密的姑娘,抿着嘴笑了笑:“喜欢吗,穿着舒服。” 就这一笑,时光“哗”地倒流了。我感觉似故人归来,倒流回十几年前那个九月,大学礼堂里闹哄哄的,平行时空的她坐在前排,也是这样抿着嘴笑,干干净净的一张脸,像春天的第一场雨,夏天的第一口瓜。那时候她是男生卧谈会上的“她”,名字只敢轻轻地说,说重了都怕…
🌸花名:绵绵羊 🗺️地址:渝北区 🉑69 🉑浅💋,详情服务,看菜单 🧾面试反馈:胸型好看,皮肤白恁 三点粉,身材好紧致水多 🉑艳舞 同行借调 💰7P(50分钟内) 13pp ❌喝🍺 嗑💊拔🎈 预约联系👉👍客服: 澜澜 双向私信:@CQhupanlanlan3_bot 🛍️聊天群:https://t.me/cclm288 欢迎大家进入🐥QQ群:1063818716 备用联系方式 防止失联
❤1
🌸花名:绵绵兔 🗺️地址:渝北区 🉑69 详情服务,看菜单 🍟面试反馈 皮肤白胸大温柔身材好紧致水多 🉑艳舞 同行借调 💰7P(50分钟内) 13pp ❌喝🍺 嗑💊拔🎈 预约联系👉👍客服: 澜澜 双向私信:@CQhupanlanlan3_bot 🛍️聊天群:https://t.me/cclm288 欢迎大家进入🐥QQ群:1063818716 备用联系方式 防止失联
⛺️渝北唐家院子11🈷5⃣ 御萝双修【啾咪】6/11🈳 小嘴抿甜【李郝】6/11🈳 巨乳护士【咪咪咪】8/15🈳 良家少妇【小马叉虫】6/11🈳 艳舞诱惑【绵绵兔】7/13🈳 170长腿【橙到日】6/11 艳舞公主【绵绵羊】7/13🈳 人气嫩妹【妖布岛台】8🈳🔥 服务之星【针不戳】8🈳 🍟预约联系客服: 澜澜 双向私信:@CQhupanlanlan3_bot 🛍️聊天群:https://t.me/cclm288 欢迎大家进入❤️QQ群:1063818716 备用联系方式 防止失联
❤2
湖畔™工作室 pinned Deleted message
🌸花名:咪咪咪 🗺️地址:冉家坝 🉑69 🉑🐍💋,详情服务,看菜单 🧾面试反馈:人照对版,一线天,波澜壮阔,伟大无需多言! 💰8P(50分钟内) 15pp ❌喝🍺 嗑💊拔🎈 预约联系👉👍客服: 澜澜 双向私信:@CQhupanlanlan3_bot 🛍️聊天群:https://t.me/cclm288 欢迎大家进入🐥QQ群:1063818716 备用联系方式 防止失联
🥰1
湖畔™工作室 pinned a photo
🌸花名:霍得转 🗺️地址:渝北区 唐家院子 🉑69 🉑🐍💋,详情服务,看菜单 🧾面试反馈:人照对版,面容精致,颜值耐看,性格好情商高,代课如初恋,腿长,屁股大,很紧,摸一下就出水 💰8P(50分钟内) 15pp ❌喝🍺 嗑💊拔🎈 预约联系👉👍客服: 澜澜 双向私信:@CQhupanlanlan3_bot 🛍️聊天群:https://t.me/cclm288 欢迎大家进入🐥QQ群:1063818716 备用联系方式 防止失联
❤1
Showing the 12 most recent of 39 posts we hold for @cqhupangzs. 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.
Posts edited after publishing
@cqhupangzs edited 7 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 8 August 2026
- Most recent edit
- 8 November 2026
Posts recorded as deleted after publishing
We recorded 5 posts on @cqhupangzs as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
- First seen missing
- 10 August 2026
- Most recent seen missing
- 5 November 2026
- Median time before seen missing
- 44 hours
- Seen missing in the last 30 days
- 3
Mentions
Named by 2 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@cqhupangzs named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 9 posts, 8 August 2026 – 23 August 2026
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.
“湖畔™工作室” (@cqhupangzs), 8,221 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/cqhupangzs.
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.