Supergroup
御姐研习社|浦浦🚘
@pupu123pupu
On this record: Topic · Growth · Engagement · Citations · Cite this entry
1,605members
+294 since we began measuring on 6 August 2026
32 online right now
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1003842692969 |
|---|---|
| Type | Supergroup |
| Username | @pupu123pupu |
| Description | 1.频道浦浦一刻 https://t.me/cdcpupupupu 和本群为非公益组织，有恰饭行为，恰饭范围仅限于广告商。 2.本人所有出击均为原价，不会收取老师折扣。被包养就不要谈独立人格。如果任何人能拿出讨口证据，群和频道直接解散，绝不食言。本条群规一直保留不会修改。2026.7.2 3.本群谢绝老师、代聊入内 4.每个月定期脱水，清理潜水不发言成员，下次脱水9月1日。是的，你没看错，本群是一个不需要人越多越好的群。 5.本群聊天红线： 脏话、辱骂、无脑嘴炮 ，恶意带节奏，触犯者禁言处理。 |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 26 September 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 15 |
| On Telegram | t.me/pupu123pupu |
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 26 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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.
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 26 Sept 2026, 03:05 | 1,605 | no change |
| 18 Sept 2026, 22:37 | 1,605 | +31 |
| 14 Sept 2026, 15:58 | 1,574 | +38 |
| 10 Sept 2026, 18:38 | 1,536 | +72 |
| 6 Sept 2026, 00:18 | 1,464 | +60 |
| 2 Sept 2026, 02:34 | 1,404 | -230 |
| 30 Aug 2026, 01:03 | 1,634 | +20 |
| 27 Aug 2026, 09:28 | 1,614 | +32 |
| 24 Aug 2026, 11:44 | 1,582 | +28 |
| 20 Aug 2026, 21:15 | 1,554 | +43 |
| 17 Aug 2026, 10:32 | 1,511 | +62 |
| 13 Aug 2026, 11:13 | 1,449 | +63 |
| 10 Aug 2026, 01:16 | 1,386 | +74 |
| 6 Aug 2026, 21:36 | 1,312 | +1 |
| 6 Aug 2026, 20:06 | 1,311 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Mentions
Named by 5 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.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“御姐研习社|浦浦🚘” (@pupu123pupu), 1,605 members as measured 26 September 2026. Telegram Register, tgregister.com/channel/pupu123pupu.
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.