Channel
@pan12521
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
842subscribers
+746 since we began measuring on 28 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004307717996 |
|---|---|
| Type | Channel |
| Username | @pan12521 |
| Created | 25 September 2026 — measured — dated from the channel’s first post |
| First recorded | 28 September 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/pan12521 |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 14 October 2026 and assigned it the closest of 31 fixed categories, at 38% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Nov 2026, 09:56 | 842 | -21 |
| 2 Nov 2026, 01:49 | 863 | -167 |
| 30 Oct 2026, 07:46 | 1,030 | -169 |
| 27 Oct 2026, 02:10 | 1,199 | +435 |
| 20 Oct 2026, 19:28 | 764 | -126 |
| 14 Oct 2026, 00:39 | 890 | +233 |
| 4 Oct 2026, 23:15 | 657 | +561 |
| 28 Sept 2026, 18:22 | 96 | no change |
| 28 Sept 2026, 17:47 | 96 | first reading |
7 posts held, back to 25 September 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 28 September 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.
🎰 91·暖暖福利放送🧧 📮 参与条件： 🪪 必须设置用户名 🎫 加入-暖暖的朋友圈 🎫 加入-暖暖女神 └ 🔑 发送口令﹝极品炮架，奇迹暖暖﹞ 🎫 加入-成都91修车学院 └ 🔑 发送口令﹝极品炮架，奇迹暖暖﹞ 🎫 加入-成都91修车学院报告收录 🎫 加入-成都91修车学院已验车库 ❗ 口令提示： 请先参与抽奖，再发送口令激活 🎁 奖品内容： 💰️ 口令红包88元 × 3 💰️ 暖暖100元优惠券 × 10 💰️ 暖暖单P半价券 × 1 ⚠️ 抽奖说明： 1.中奖半价券/红包请在48小时内联系 @pan20123 兑奖 2.中奖半价券，兑换使用后须出具体验报告 3.本次奖品半价券不可折现、不可转让、不可买卖；因炸号，退群，注销账号等原因，超时未兑换等原因的，不予兑奖！ 🔋 人品加成：⚡️× 5 规则 📅 开奖日期：(北京时间) 2026年10月02日 21时00分00秒
暖暖的朋友圈 pinned a photo
新人暖暖～首次下海 🉑口爆 年龄20 裸高166 体重102 🐻C 服务：鸳鸯浴 无T口 亲咪咪 舔 69 制服丝袜诱惑 新人成都首开，初次下海，昨天晚上连夜空降到成都，以前从来没做过。本人很乖，颜值高，身材好，皮肤白，真人真照，态度好听话乖巧，但是第一次下海从来没做过，需要老表些指点一二，调教调教😄 🈲️：无T 拔T 磕药 喝酒 扣B SM 低素质 7P（50分钟）12PP（90分钟） 默认P，PP提前说，PP做一次不退。
📊 0条车评 写报告 好评 0% | 人照 | 服务 中评 0% | 颜值 | 态度 差评 0% | 身材 | 环境 ✅成都91修车学院认证 艺名: #暖暖 地址: #高新区 #交子大道站 价格: #700P/50分钟 #1200PP/90分钟 类型: #御姐车 #身材车 #态度车 #敏感车 #7P #代聊 #女友感 #交子大道 联系: @pan20123 锐评：该老师年龄21岁，身高165cm，体重100斤左右，无纹身，肤色正常色偏白，全身摸着光滑，整体身材细腰大屁股，无赘肉，炮架子身材；人照相似度9分，去美白跟视频差不多，真人颜值中上，脸型偏圆润有肉肉这种，妆容御姐；胸为B，掌中宝，乳头乳晕小巧粉嫩，手感软；下面户型为小蝴蝶，浅褐内粉，特别紧，进入有顿挫感，水量正常，毛量正常；服务为 三件套 69 优点: 细腰大…
Channel name was changed to «暖暖的朋友圈»
新人暖暖 紧的批爆 细枝硕果 爽的一批
Channel created
Showing the 7 most recent of 7 posts we hold for @pan12521. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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 6 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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“乔乔” (@pan12521), 842 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/pan12521.
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.