科室停水了只能上门哦哥哥们

Channel
琪琪的🏘️🧸
@qiqi73745
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,988subscribers
+1,642 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1003996480466 |
|---|---|
| Type | Channel |
| Username | @qiqi73745 |
| Created | Between 1 April 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/qiqi73745 |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 06:16 | 1,988 | +196 |
| 16 Sept 2026, 19:40 | 1,792 | +13 |
| 12 Sept 2026, 23:20 | 1,779 | +42 |
| 3 Sept 2026, 10:58 | 1,737 | +18 |
| 30 Aug 2026, 22:05 | 1,719 | +1,270 |
| 24 Aug 2026, 15:25 | 449 | +76 |
| 16 Aug 2026, 21:12 | 373 | +27 |
| 15 Aug 2026, 17:00 | 346 | first reading |
Engagement
20 posts held, back to 31 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 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 20 posts for this entry, the most recent from 14 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 29s
- Average length
- 29s
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.
Reaction mix
14 reactions across 7 posts, in 2 distinct kinds. The most used accounts for 92.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 13 | 92.9% | |
| 💘 | 1 | 7.14% |
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 9 of the 20 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 14 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 31 July 2026 to 14 August 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
开课了宝宝们
探花楼(杭州最真实的出击交流群) 【探花时间】:2026-08-12 【老师艺名】:琪琪 【探花留名】:ClowRead 【人照打分】:9 【身材打分】:10 【服务打分】:8.5 【态度打分】:10 【环境打分】:9 【综合评分】:9.3 【体验详细】:女孩,明眸皓齿的女孩,单纯可爱明眸皓齿的女孩,让你重新体验一次青春的女孩。这就是我对琪琪的初印象,浑身上下都散发着女大的单纯清澈与青春活力,窈窕的身影逐渐与大学时候的那个她渐渐融合,初见有点小羞涩,熟络之后就像个百灵鸟跟你聊天聊地。对于流程也显得不那么娴熟,在浴室甚至换成我给她上上下下仔细清洗,过程中会用大眼睛偷偷瞄你,眼神碰上了又会慌乱的躲开。床上的服务也是标准的嫩妹三件套,但是口活的技术不错,极致敏感的身体,轻轻调情就湿的一塌糊涂,甚至感觉用水多多的套套都多余,过程中都很配合,一双无辜而又清澈的大眼睛,在高潮的时候会略显空洞的望着你,仿佛灵魂短暂的脱窍了,由于是舞蹈生出身…
杭州狼友出击协会模板 https://t.me/+yI0wXTr_cK8wMTA1 【综合评价】:#超级好评 【验证留名】:CR 【验证时间】:8月10日 【妹子花名】:琪琪 【联系方式】:@qiqi737455 【所在位置】:余杭未科 【修车水费】:500p 【包含服务】:有的打✅ ① 舌吻 有浅吻 ② 69舔逼 没要,可以谈 ③ 情绪价值 ✅ ④ 毒龙 【身高身材】:身高大概165多,比例很好,腿很长腰很细,无纹身 【颜值相似】:人照相似9分,颜值很好看,很符合我的审美 【凶器罩杯】:熊大概是b,乳头粉色偏小,自然熊,手感极佳 【服务总结】:嫩妹三件套 【个人卫生】:没闻到烟味,有漱口水浴巾,事前有陪洗 【时间管理】:开课准时,排课宽松 【推荐程度】:10分,因为外形长相都比较符合我的审美,再加上日感契合度很高,所以我很推荐 【流程小文】: “还记得多年前跟你手牵手,你却害羞的不敢抬…
Alex的大奶食谱: https://t.me/alexteamreport 【老师花名】:#琪琪 【上课费用】:工兵p 【上课区域】:#余杭未科 【出击评价】:#超级好评 【出击狼友】: ClowRead 【老师特点】: # 个高腿长细腰 # 面容姣好 # 敏感体质 # 柔韧性好 【老师车牌】: @qiqi737455 #硬件配置 个高大概165~170的样子,不胖不瘦正正好是那种充满青春的窈窕身材,年龄绝对不超过20,面容姣好,尤其是一双大眼睛,清澈而又充满挑逗,胸大概b,天然胸,手感极佳,腰部无赘肉,腿型是那种稍微有点肉的长腿,手感极佳!! #服务内容 有陪浴,舔胸,口交,浅吻,态度很好,都很配合 #情绪价值 女友感拉满,会躺在你怀里跟你聊天,刷到好看的视频会跟你一起看,完全无流程化的操作,一切都很自然 #态度意识 态度很好,说出来只要能接受都会配合,说要拿个东西,蹦蹦跳跳就帮你去拿了 #日感反馈 是我出击…
今天开课喽宝宝们
❤1
Posted without readable text
Posted without readable text
❤1
明天开课欢迎包天大折扣 目前只外出
❤2
休息几天
开喽宝宝们
还是不舒服休息一天不好意思宝宝们
❤2💘1
Showing the 12 most recent of 20 posts we hold for @qiqi73745. 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.
Forward network
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.
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.
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“琪琪的🏘️🧸” (@qiqi73745), 1,988 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/qiqi73745.
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.