Channel
@gushi1024
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,096subscribers
+23 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003735446821 |
|---|---|
| Type | Channel |
| Username | @gushi1024 |
| Created | 28 February 2026 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/gushi1024 |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 51% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 06:38 | 1,096 | -5 |
| 12 Sept 2026, 15:58 | 1,101 | -8 |
| 8 Sept 2026, 10:42 | 1,109 | +9 |
| 2 Sept 2026, 22:09 | 1,100 | -7 |
| 30 Aug 2026, 18:11 | 1,107 | -7 |
| 28 Aug 2026, 01:34 | 1,114 | +1 |
| 25 Aug 2026, 10:48 | 1,113 | +1 |
| 22 Aug 2026, 12:58 | 1,112 | -10 |
| 19 Aug 2026, 04:34 | 1,122 | +13 |
| 16 Aug 2026, 07:26 | 1,109 | +45 |
| 12 Aug 2026, 08:32 | 1,064 | -9 |
| 12 Aug 2026, 03:31 | 1,073 | first reading |
7 posts held, back to 28 February 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 7 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
喵女士的二三事（上） 喵女士，胸器惊人，御姐风骨，性价比不差，服务褒贬不一。 某日，友人兴奋地告诉小灰机：喵女士要回来了，机票已订，头课PP也约好了。他是她的沉船常客，往来几十次，对“头课”有着近乎处女情结的执念。 这本无可厚非，可小灰机是何许人？TG恶霸、二沙岛岛主，多重身份集于一身。见友人那副得意模样，他悄悄开了个小号，和喵女士商量好约了头课四小时包时。 于是喵女士对友人说：“飞机晚点了，改到明天吧。”友人略显沮丧，半小时后，小灰机却又借故取消。 喵女士又转而对友人说：“飞机又准点。” 友人失而复得，喜滋滋再来炫耀。 小灰机把约课与取消的记录一并发给他，没有再说多余的话。 友人沉默无语，心如刀割，自此对喵女士彻底失望，失而复得的头课也没去了。听说他现在沉溺于另一位大胸御姐，日日流连...... 我本不知喵女士是谁，因为小灰机说的时候，并没指名道姓。 直到小灰机某日说：“树洞现在天天刷她“ 我才恍然——原来是…
57天的“爱情” 一面倾心 六月中旬，命运随手掷下一枚半价的签。她出现时，冷白皮衬着清瘦的身形，曲线不偏不倚，眉眼也生得恰到好处——几乎精准地落在我的审美里。见过之后，我竟有些失态，仿佛真的撞见了所谓的真爱。彼时频道初起，电报也玩不久，那时几乎天天都在出击。从前遇到中意的人，总会忍不住在水群时泄露半分；这一次，却只在频道里淡淡落下一句“很好，像是遇到了真爱”。最亲近的几位再三追问，我都硬生生咽了回去。 一周三见 因为同时还在其他榜上抽奖，手里又握着些积分，我便故意放出风声，说要抽当时颇为热门的佳妮，暗地里却用几个号把她的充能悄然填满，终又得一张半价+一张优惠券。于是初见后第三日再见，再隔三日又见。每一次都像有说不尽的话，电报上断断续续地续着，有一搭没一搭，却并不觉得寡淡。 多嘴之祸 初见时，她曾提起有位L先生想拍她。她看着朋友被拍后心疼的要哭了。我多嘴劝了一句：既然不喜欢，便不必勉强。此后几次见面，都会不自觉地再问起这件事…
广州故事汇 · 创刊词 没有真名，没有身份，只有那些真正沉过、痛过、醒过的故事。 我们只收“老师”与“学生”之间真正有分量的爱恨情仇—— 那些短暂的陪伴与漫长的余韵， 那些明码标价却渐渐失控的情绪， 那些不该沉却还是沉了的船， 那些以为只是交易、却在某一刻动了真情的瞬间， 以及沉船后的反水、消失、重逢、报复与救赎。 鸡毛蒜皮的琐事，这里不管。 只欢迎那些真正能让后来者心惊、警醒、反思的经历。所有投稿都会做严格匿名化处理， 并在保留核心真实的基础上，适当进行深度文学加工， 让故事更有力量，也更值得被反复阅读。我们力求每周有所更新。 创立这个故事汇的目的很简单—— 警醒后来者，不要重蹈覆辙。 广州很大，夜很长。 真正能听完这些故事、并让后来人少走弯路的地方，却很少。 欢迎来到《广州故事汇》，把那些沉过的船、踩过的坑、醒过来的夜，翻给我们看吧。 投稿请私信，或按频道规则发送。 我们会认真、匿名、克制地处理每一段故事。 ——广州…
Channel name was changed to «广州故事汇»
Channel photo updated
广州故事汇 pinned Deleted message
Channel created
Showing the 7 most recent of 7 posts we hold for @gushi1024. 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.
Named by 1 registered channel — 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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“广州故事汇” (@gushi1024), 1,096 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/gushi1024.
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.