Channel
@gumingpb
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1,890subscribers
+97 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003295738050 |
|---|---|
| Type | Channel |
| Username | @gumingpb |
| Created | Between 1 October 2025 and 28 February 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 27 September 2026 |
| On Telegram | t.me/gumingpb |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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 |
|---|---|---|
| 27 Sept 2026, 02:17 | 1,890 | +120 |
| 15 Sept 2026, 22:18 | 1,770 | +8 |
| 12 Sept 2026, 07:58 | 1,762 | -2 |
| 8 Sept 2026, 11:57 | 1,764 | -1 |
| 3 Sept 2026, 10:46 | 1,765 | -4 |
| 31 Aug 2026, 06:44 | 1,769 | -5 |
| 28 Aug 2026, 17:13 | 1,774 | +6 |
| 25 Aug 2026, 10:55 | 1,768 | -7 |
| 22 Aug 2026, 13:26 | 1,775 | -5 |
| 19 Aug 2026, 11:53 | 1,780 | -3 |
| 16 Aug 2026, 16:04 | 1,783 | -5 |
| 13 Aug 2026, 03:14 | 1,788 | -1 |
| 10 Aug 2026, 10:23 | 1,789 | -4 |
| 7 Aug 2026, 20:48 | 1,793 | no change |
| 7 Aug 2026, 17:49 | 1,793 | first reading |
7 posts held, back to 5 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 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
杭州古茗女仆排班 📍门店地址： ⏺上城区婺江路附近 💸收费价格 ： ⏺标大/超大 600/h，1100/2h，续钟 550/h；外勤1200/2h，另加来回路费 🗓8月8日（周六）出勤排班： 🟠小嘟 16-23 测评合集 🟠小茹 15-24 测评合集 🟠汉堡 18-21 测评合集 🔗店铺导航： 联系客服 @guming_kf 微信客服 Toixc771 聊天交流 @guming66888 排班频道 @gumingpb 测评反馈 @gumingcp
Signed 古茗客服 美团小发
#ootd 🉑外勤 #小嘟 仅空21.30-22.30 🈳 测评合集 #世一 仅空21.00-22.00 🈳 测评合集 联系客服 @guming_kf
Signed 古茗客服 美团小发
#ootd 🉑外勤 #小嘟 仅空21.30-22.30 🈳 测评合集 #世一 仅空21.00-22.00 🈳 测评合集 联系客服 @guming_kf
Signed 古茗客服 美团小发
杭州古茗女仆排班 📍门店地址： ⏺上城区婺江路附近 💸收费价格 ： ⏺标大/超大 600/h，1100/2h，续钟 550/h；外勤1200/2h，另加来回路费 🗓8月7日（周五）出勤排班： 🟠小嘟 15-23 测评合集 🟠世一 16-24 测评合集 🟠糯糯 15-24 测评合集 🗓8月8日（周六）提前预约： 🟠小茹 15-23 测评合集 🟠汉堡 周六🈵 周日仅🈳18-21标大 测评合集 🔗店铺导航： TG客服 @guming_kf 微信客服 Toixc771 聊天交流 @guming66888 排班频道 @gumingpb 测评反馈 @gumingcp
Signed 古茗客服 美团小发
#ootd 🉑外勤 #小茹 21-22 🈳 测评合集 #世一 18.30-24.00 🈳 测评合集 #小嘟 18.30-22.00 🈳 测评合集 联系客服 @guming_kf
Signed 古茗客服 美团小发
杭州古茗女仆排班 📍门店地址： ⏺上城区婺江路附近 💸收费价格 ： ⏺标大/超大 600/h，1100/2h，续钟 550/h；外勤1200/2h，另加来回路费 🗓8月6日（周四）出勤排班： 🟠小茹 15-23 测评合集 🟠世一 16-24 测评合集 🟠糯糯 15-24 测评合集 🟠小嘟 15-22 测评合集 🔗店铺导航： TG客服 @guming_kf 微信客服 Toixc771 聊天交流 @guming66888 排班频道 @gumingpb 测评反馈 @gumingcp
Signed 古茗客服 美团小发
#ootd 🉑外勤 #小茹 15-23 🈳 测评合集 #世一 16-24 🈳 测评合集 #小嘟 16-23 🈳 测评合集 联系客服 @guming_kf
Signed 古茗客服 美团小发
Showing the 7 most recent of 7 posts we hold for @gumingpb. 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.
Named by 8 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.
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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“古茗女仆排班频道” (@gumingpb), 1,890 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/gumingpb.
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.