Channel
@kgjdddd
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
6,127subscribers
+1,594 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002454206868 |
|---|---|
| Type | Channel |
| Username | @kgjdddd |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/kgjdddd |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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 |
|---|---|---|
| 10 Nov 2026, 15:50 | 6,127 | -2 |
| 7 Nov 2026, 01:25 | 6,129 | +19 |
| 3 Nov 2026, 19:16 | 6,110 | +4 |
| 31 Oct 2026, 15:36 | 6,106 | +2 |
| 29 Oct 2026, 02:20 | 6,104 | +7 |
| 26 Oct 2026, 02:17 | 6,097 | +3 |
| 22 Oct 2026, 22:46 | 6,094 | +43 |
| 20 Oct 2026, 04:36 | 6,051 | +89 |
| 17 Oct 2026, 06:50 | 5,962 | +78 |
| 13 Oct 2026, 20:27 | 5,884 | +137 |
| 8 Oct 2026, 04:18 | 5,747 | +106 |
| 1 Oct 2026, 16:40 | 5,641 | -87 |
| 16 Sept 2026, 11:57 | 5,728 | +110 |
| 12 Sept 2026, 23:39 | 5,618 | +237 |
| 9 Sept 2026, 01:20 | 5,381 | +220 |
| 4 Sept 2026, 00:55 | 5,161 | +20 |
| 31 Aug 2026, 04:48 | 5,141 | +43 |
| 27 Aug 2026, 19:04 | 5,098 | +34 |
| 24 Aug 2026, 13:04 | 5,064 | +41 |
| 20 Aug 2026, 10:06 | 5,023 | first reading |
75 posts held, back to 6 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 11 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 9 of 26 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 5 November 2026 |
|---|---|
| Posts held | 75 (6 August 2026 – 5 November 2026) |
| Views total | 10,500 |
| Reactions total | 3 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 5 Nov 2026, 16:49 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
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.
5 reactions across 5 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5 | 100.0% |
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 16 of the 75 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 5 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 75 most recent posts we hold, published 6 August 2026 to 5 November 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.
Telegram’s own ‘edited’ marker: 11 of 26 posts held from the last 30 days (42.3%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
#空港基地斯巴达编队 @小六 #2026.11 #西湖 #美汁源 #漫漫 店铺: @mzynpqyj 颜值8 身材8 皮肤8 敏感度9.5 性格9.5 综合体验 9 优点：性格超好 缺点：会触发特殊机制 过程： 性格：超好，过于善良的好妹妹，很容易被骗。 体质：超敏体质，过度刺激容易过敏，亲柔很重要。后背敏感，可以抚摸。 状态：心态和皮肤都很嫩，三点粉，人工白虎。 受众：推荐素质流玩家（素质流玩家有保底）。 机制：有特殊机制，具体内容不公开。 情报：西湖掉落时长不确定，可能回萧山。 推荐等级：#L4 L1 踩雷别去 L2 平淡乏味 L3 可以一去 L4 较为推荐 L5 此身必驾
#空港基地斯巴达编队 @火鸡味锅巴 #2026.11 #上城 #翻斗花园 #妈妈 店铺: https://t.me/fandouhuayuan_jlq/27671?single 颜值8 身材8-9.5 皮肤7.8 敏感度9.5 性格8.5 综合体验 8.4 优点：敏感高潮怪，bbw，一米八，f奶 缺点：大体型受众有限 过程： 翻斗花园近期版本更新角色妈妈，一米八加圆润身材堪比八尺夫人。看模卡面如蛇蝎，带着一股邪恶的气息，而且还是s😲，我特么直接冲爆。 出门前下大雨还想要不要鸽了，还是二弟替我下了决心，冲！ 提前到等了几分钟妈妈随后赶到。本人对比模卡八分相似，黑色镂空蕾丝裙和灰色丝袜勾勒着身型，近看妆感较重，在当前版本已经是普遍现象。 坐下前我去洗了个手，让妈妈看见（重点）。两人躺在一起聊天侃大山，妈妈的谈吐带着自然且凌驾的感觉。捧着我的脸说我像一脸期待等主人回家的小狗😊。随后便吻了上来，唇齿想接，舌头交缠两人不停交替攻…
#空港基地斯巴达编队 @孤城 #2026.11 #拱墅 #不晚 #狐狸 店铺: https://t.me/buwanlianai2026/397825 颜值7.5 身材7.8 皮肤 8 敏感度 9 性格 8.5 综合体验 7.9 优点：敏感度高 缺点：颜值身材未到预期 过程： 到店看到狐狸，穿着长裤，有点欧美的感觉，尤其是眼睛特别的欧美，进房间后，妹妹细心的将漱口水递给我，然后笑盈盈的看着我，由于店里只是个沙发，两人刚开始先端坐这，然后搂腰靠在一起破冰，她发现我最近在健身，于是一起聊了一会健身的话题，破冰后，一个对视两人立马火热的吻在一起，双手也不闲着，先攻击双峰，慢慢往下探，隔着长裤感受到了一点湿润，于是让她脱掉长裤，等一脱完，两个人立马又抱在一起，轻轻的隔着内裤对小森林慢慢抚摸，感受到越来越湿润，再舔着奶头，一声声呻吟声在旁边响起，于是向最后一步发起攻击，没想到的是妹妹严防死守，后面尝试了很多次，就算内裤湿透也不肯卸…
#空港基地斯巴达编队 @低调低调 #2026.11 #上城 #翻斗花园 #毛毛 店铺：https://t.me/fandouhuayuan_jlq/27777 颜值7 身材8 皮肤 9 敏感度 8 性格 9 综合体验8 以前毛毛在kt的时候一直没约上，这次到翻斗上班我立马就约了。 进门就热情的打招呼，给我一下整得不知所措，没想到一个看着内向的妹子居然这么热情。 我们双双坐在床上挑了一个动漫看着， 婷婷很热情的和我攀谈着家常，也谈论这动漫内容。毛毛穿搭和之前的ootd没有任何区别，看着就想邻家妹妹一般，那可真是年轻时的心动。在气氛到了后我也是主动吻上了她的唇，没想到居然这么反差，妥妥的小蟒蛇来的，感受到那双唇的湿热，我那双不老实的手也是开始向下摸索 那双又长又直的双腿不突兀还带着肉感，在一整抚摸后，终究开始了神秘的探索，还没爱抚多久已经是水漫金山，真的好多。一边热吻一边爱抚中我也是燥热的不行，主动卸甲让我，在她的一阵…
#空港基地特战编队 @6699飞行员 #珊珊 #星茶荟 #上城 #2026.10 #1h 店铺：https://t.me/xingchahui888/125261?single 颜值 8.7 身材 8.7 皮肤 8.6 敏感度8.3 性格 8.6 综合体验 8.5 优点：腰臀比一绝、甜妹、身材好、广东小夹子 缺点：没赶上好时候 过程：珊珊作为星茶荟最近的满姐之一，前面一直时间不太合适没有约上，这次终于狠下心来错峰出行。广东小夹子一枚，声音比较好听，软软糯糯的有点儿像抖音那个小孩儿音的探店博主。当天穿着一身灰色包臀裙，参考前面的ootd视频，大胸 大屁股呼之欲出，刚进房间小弟弟就立马起立了，从中能看得出来硬件确实一流。软件上情绪价值给得很足，夸夸党，说有腹肌身材好声音还好听，关键是篮球尺寸确实异于常人，不过大多数妹妹的话术都这样，不知真假。舌吻技术上属于是中小蟒蛇，配合度没问题，但是舌头不长。既然是满姐其他方面也无需赘述…
#空港基地特战编队 @6699飞行员 #涵涵 #梦之瑶 #上城 #2026.11 #1h 店铺：https://t.me/mzy461615/7352?single 颜值 8.3 身材 8.4 皮肤 8.4 敏感度8.5 性格 8.7 综合体验 8.5 优点：大蟒蛇、御姐、一线天、主动狂野 缺点：略有小肚子 过程：最近上城附近开了不少新店，cj变得更方便了，对钱包的压力也很大了。看到新人涵涵挺符合自己的御姐审美，果断冒雨出击。整体风格上妹妹确实御姐范儿十足，听说这还是因为今天打扮更加温和，平时的打扮会更加狂野，高跟鞋都是豹纹的。钟上内容来说也是狂野小豹类型，今天也是化身成为了一名小受，被动享受了一会儿。吻技上属于大蟒蛇，有30分钟的时间没有松嘴，略有烟味，但是相对能接受。卸甲主动顺畅，没多一会儿就完成了卸全甲的任务，皮肤相对顺滑，锁骨处有纹身，但面积不大。胸的大小在B-C之间，水滴型，较为柔软，敏感度上相对一般，水量不…
#空港基地斯巴达编队 @1024飞行员 #甜甜 #库洛 #西湖 #2026.11#1h 店铺：https://t.me/kuluokeke/373871?single 颜值8.2 身材 8.5 皮肤 8.3 敏感度 9 性格 8.8 综合体验8.7 优点：活泼开朗，敏感跳虾 缺点：没化妆 过程：（100 字以上） 听说库洛来了一位王冰冰，虽然不是王冰冰的粉丝，但还是很喜欢她给人的那种感觉，我到要去看看这位甜甜妹妹有几成似她～ 到了楼下听从指挥安稳上楼，听说来了个美女客服，叮咚之后我竟一时分不清我面前的是客服还是妹妹，在大厅稍等片刻之后，甜甜穿着一身运动服风尘仆仆的从外面回来了，说实话第一眼我差点以为是哪来来串门的妹妹，得知我早就等候多时时热情又腼腆的和我说了声抱歉，我的心中顿时一阵暖暖的，这时甜甜呆萌的忽然记起来要换下衣服，然后又拿着包进了卫生间，出来时已然换了一身小白T+JK裙，还系着一条小领带，这才对…
🎰 斯巴达&养只猫联谊活动 📮 抽奖条件: 🎫 加入-杭州养只小猫女仆交流群 🎫 加入-浮光跃金 🎫 加入-武林女仆集注 🎫 加入-武林女仆杂货店 🎫 加入-空港基地（杭州女仆） 🎫 加入-空港基地杭州女仆编队 🎫 加入-战斗暴龙兽的女仆进化之旅 🎫 加入-那些年去过的女仆 🎁 奖品内容: 150优惠券 × 3 100优惠券 × 5 💡 活动说明: 🥷优惠券与别的优惠不叠加 🥷开奖后，有效期7天 👹最终解释权归商家所有 📅 开奖日期:(UTC+8) 2026年11月06日 21时19分53秒
#空港基地斯巴达编队 @FD #涵涵 #梦之瑶 #上城 #2026.11#1h 店铺：https://t.me/mzy461615/7146?single 颜值8 身材8.9 皮肤 8.6 敏感度 9 性格 9 综合体验8.79 优点：女友感、敏感、水润 缺点：没有 过程： 梦之瑶是新店，一直关注，只是迫于没有合适的。偶然群里看到涵涵ot，很喜欢，正好今天得空，就问了涵涵，正好客服说有空，遂直接预约前往。 店在小区，安全性不错，跟着客服一步步到店。因为来的早，照例先冲个澡。 房间有一次性床单，进屋一会，妹妹进来了，紧身体恤+包臀裙，凸显婀娜身姿，妆容精致，五官柔美，确认是ot视频中19岁小美女一枚。主动递漱口水，还端着垃圾桶等你，好评！ 涵涵湖南妹子，比较健谈，破冰一会就让她坐上来，抱着屁屁，又软又滑。涵涵吻技一流，湿滑软糯，光亲亲就能哼唧个不停，全程缠斗。卸甲流畅，独留一甲，上手的那一刻惊了，怎么能又软又挺。向蓓蕾进攻…
#空港基地斯巴达编队 @89757 #vv #梦之瑶 #上城 #2026.11#1h 店铺：https://t.me/mzy461615/7115 颜值7.5身材8皮肤 9 敏感度 9 性格 8 综合体验8..88 优点：皮肤光滑白皙，腿细，腰臀比很绝。 缺点：胸没有很大 过程：关注这家店蛮久了。今天帅逼相邀一起去打新，看了一下模卡就约了。 位置在九堡这边，离很近。虽然下雨，但是出击的路上空气都是香甜的。 到店妹妹已经等候许久了，因为约的比较临时，客服提前告知说只有一个没有投影的房间还空着。但是也无所谓，又不是冲投影去的。进了房间刚躺床上，妹妹就躺进了怀里。开始了有一搭没一搭的闲聊，思绪已飞，手在光滑的背上轻抚了起来。妹妹的手也不自觉的伸进了衣服里面，全自动流派，很省心。边摸还会问这样子是否会舒服点，后面自己就女上跨坐着摇，此时甲还没卸，我就说有点硌，脱了吧。很爽快的开始了卸甲，片刻后俩人就一丝不挂。让女上摇了会我就让…
#空港基地斯巴达编队 秦先生 #kiki #美年达 #上城 #2026.11#1h 店铺：https://t.me/hznplaq/110677 颜值8身材7 皮肤 8 敏感度 8性格 8 综合体验7.8 优点：主动热情，情绪价值不错 缺点：身材中规中矩 过程：周一看到排班有kiki，放购物车很久了遂决定cj，本人还是很好看的，下班直冲美年达，妹妹领进房间主动拿来漱口水，躺床上打开了前一个顾客看的音乐类节目，躺在舒服的大床上，kiki主动靠过来，躺在我怀里，0帧起手直接亲了过来，妹妹是条中蟒蛇，可以一直亲，你不停她不停，小舌头小巧特别灵活，当然如果你不经意的吸到她的小舌头你会发现惊喜，说话很温柔，情绪价值真的拉满，抚摸妹妹的胸，两颗小葡萄绽放起来，听着妹妹声声娇喘，热血沸腾，妹妹说甲衣有点束缚，独留一甲，隔着裤子摸了几下，已经能感觉到一汪春水了，讨论起了哪里能让他登顶的生理课，穿越茂密的丛林，奔向水帘洞，伸出我的加藤鹰之…
#空港基地斯巴达编队 @小小 #毛毛 #翻斗花园 #上城 #2026.11#1h 店铺：https://t.me/fandouhuayuan_jlq/26863 颜值8.2 身材8.4 皮肤 8.6 敏感度 8.5 性格 8 综合体验8.2 优点：皮肤滑嫩 配合度较好 缺点：似乎有点疲？话不多 过程：本来萝莉不在我的出击范围内，不过明总说甜妹感居多加上之前约的妹妹正好鸽子了于是便约好时间出击了。进房间后稍微聊了聊换店的事就靠到一起开始亲亲，亲亲很配合反馈也比较强，中蟒以上，卸甲也很顺利，爽快的卸干净了，不过钟上比较沉默，没什么互动感觉，情绪价值比较缺乏吧，超大范围内的内容倒是都很配合了。 总结：可能没对上妹妹电波，整体上钟除了配合很好之外话很少，过程中靠在怀里沉默居多居多，平平淡淡吧。。。 推荐等级：#L3 L1 踩雷别去 L2 平淡乏味 L3 可以一去 L4 较为推荐 L5 此身必驾
Showing the 12 most recent of 75 posts we hold for @kgjdddd. 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.
@kgjdddd edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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 4 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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“空港基地（杭州女仆）” (@kgjdddd), 6,127 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/kgjdddd.
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.