Channel
@kkjut64641
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
1,180subscribers
-16 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1004362945946 |
|---|---|
| Type | Channel |
| Username | @kkjut64641 |
| Created | Between 1 June 2026 and 20 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/kkjut64641 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 01:46 | 1,180 | -10 |
| 10 Aug 2026, 20:52 | 1,190 | -6 |
| 10 Aug 2026, 12:15 | 1,196 | no change |
| 10 Aug 2026, 12:01 | 1,196 | first reading |
11 posts held, back to 20 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 pageof 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.
| Window | Rolling 30 days · latest post in window 10 August 2026 |
|---|---|
| Posts held | 11 (20 July 2026 – 10 August 2026) |
| Views total | 112 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 12:15 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.
川普大流量引流互推【频道A9】 最爱反差婊🌹爸爸你不要这样，小穴要裂开了，你都让女儿怀孕了！ 1. 女神要亲亲😘 2. 你的草莓妹妹🍓 3. 爱笑的女人都会坏！ 4. 气质女神 5. 长春外卖上门频道 6. 福利姬学生宿舍酒店自拍偷拍 7. 温柔可人的大姐姐 8. 性感甜妹妹 9. 付费资源免费看的福利搜索引擎✅ 10. 妖媚的小姨子 11. 女神姐姐的凝视 12. 老婆和小姨子的合拍 13. 海角禁忌录|强奸迷奸 14. 黑丝欲望 15. 精神小妹福利社 16. 这就是女神范儿 每日大赛🍑妈妈的屁股太大了，尤其是在练瑜伽的时候，爸爸太幸福了，可以天天👅我妈的大屁股🌹
免费互推【频道A5】 黄色交流群 1. 福州外围品茶 2. 无锡非常不错的妹子真实靠谱喝茶 3. 黄色交流群 4. 纯色怀旧猫片（陆港台3-4级） 5. 裸贷泄密资源 6. 💋日本超清无码AV|熟女反差少妇💋 7. 大理上门约 8. 福利姬轮奸海角社区 9. 电报低成本引流｜高质量增粉 10. 大学生宿舍和男的一起自拍泄露 黄色交流群
原味互推【频道B2】 神马搜索 1. 露脸曝光26岁混血极品美女 2. 长春高端外围真实服务妹子 3. ⁰免费白嫖 ai脱衣机器人 满足你的一切幻想 4. 语音萝莉裸聊一对一服务包满意👅👅 5. 肤白貌美大长腿气质佳在线裸聊👄👄 6. 高颜值反差萝莉 7. 原味 8. 韩国舞蹈频道 9. 爽翻天妹妹在线视频裸聊👄等你来哟 10. ❤️[telegram]免费机器人[telegram]机器人定制🌹 11. 电报零粉起步轻松涨粉 12. Growth Engine 13. 柏林引流｜Telegram引流增粉｜Telegram频道运营｜Telegram涨粉技巧｜推广方法 极搜搜索
一个很邪恶的频道 未满十八岁禁止入内 🚀来自百度互推【 E9 】组🚀 1. 优链科技-哈希游戏赌博结果修改外挂程序 2. 重庆 集美会私密兼职约炮 3. 酒店监控探花偷窥癖 4. 老衲吃瓜 5. 少萝少御御姐在线裸聊一对一 6. 👨✈️【查一切】聊天记录➏开房记录➏通话记录➏开盒➏查档👨✈️ 7. 镇江外围全区上门空降服务 8. 贵阳外围品茶 9. 武汉外围上门喝茶 10.🟢绿帽淫妻少妇3P调教🟢 11.济南海选上门服务 12.清纯萝莉少女🍒 😍一个很牛逼的频道 限时免费开放 👙失足少女求调教（人妻被逼出轨😍） 💋性瘾少女嫩穴想被插入😍
⭐️⭐️⭐️星链互推 - B04车⭐️⭐️⭐️ AD：十万全国楼凤资源🔥每日更新 AD：海量资源免费搜片群 1. 中南楼凤大全 2. 异性SPA/富婆男技师推油💋 3. 粉馒头Cosplay预览群 4. ㊙️☘️老船长树洞㊙️ 5. 全国上门【高质量外围】 6. 酒店偷拍|摄像头直播|泄露曝光 7. 成都嫩妹上门服务 8. 足交反差网红母狗 AD：引流神器自动发片机 AD：👉全网破解资源免费搜索👈
大流量互推首选【频道B3】 最爱反差婊🌹爸爸你不要这样，小穴要裂开了，你都让女儿怀孕了！ 1. 性感露脸F杯巨乳OL美女醉酒自愿求操 2. 菲菲裸聊馆在线接性感裸聊一对一🤞🤞🤞 3. 电报低成本引流｜高质量增粉 4. 抖音反差网红福利姬㊙️ 5. 韩国美女跳舞 6. 石家庄上门约 7. 日本欧美 8. 泰安性欲超敏感的御姐兼职外出品茶 9. 嫩鲍大学生精品私拍 10. 日本好片无码AV高颜值FC2 11. 韩国小姐姐舞蹈合集 12. 日本爽片(高清无码) 13. 异性SPA/夫妻SPA男技师🔞 14. Social Growth Lab 15. 热播短剧㊙️擦边短剧 16. 徐州极品嫩妹上门服务 17. 三亚外出一手嫩妹资源 18. 柏林引流｜Telegram引流增粉｜Telegram频道运营｜Telegram涨粉技巧｜推广方法 19. 👨✈️【查一切】聊天记录➏开房记录➏通话记录➏开盒➏查档👨✈️ 20. 湖州极品外围多…
马云互推【频道A9】 最爱反差婊🌹爸爸你不要这样，小穴要裂开了，你都让女儿怀孕了！ 1. 绿茶女孩 2. 黑丝小太妹 3. 姐姐28岁还是单身！ 4. 我可是你的妈妈呀！ 5. 站街女的另一面 6. 🔞小红书深度擦边🔞 7. 调皮的大姐姐 8. 女神的回头一笑 9. 寸止村长🫶 10. 广州外围(精选资源) 11. 付费资源免费看的福利搜索引擎✅ 12. 📣 通知下去：我要操逼了 13. 短发女神是S 14. 温泉里面的尤物 15. 各场所扫街验牌迷玩 16. 花儿一样的姑娘 17. 柏林引流｜Telegram引流增粉｜Telegram频道运营｜Telegram涨粉技巧｜推广方法 18. 酒吧女郎 19. 一个发泄工具罢了！ 20. 和田地区极品外围品茶学妹兼职赚学费 21. 电报高效引流一键爆粉 22. 我是你的小公主 23. 气质女神 好看的公众号🍑妈妈的屁股太大了，尤其是在练瑜伽的时候，爸爸太幸福了，可以天天👅我妈的大
1️⃣【凶器罩杯】：B+ 2️⃣【身高身材】：166 3️⃣【大概年纪】：30 4️⃣【 体重 】：105 5️⃣【服务内容】： #一条龙💋#洗澡💦#调情 💦#舌吻💦#制服💦💦#口爆💦#深喉💦#69互动💦#胸推💦#臀推💦#独龙🐲💦#舔蛋💦#做爱💦#无套💦 狼友精选好评：姐姐人很好 好聊 不冷场，我们一起看电影吃东西像情侣一样 情绪价值拉满，服务也很周到 ，美好的一晚 下次还会找姐姐的
1️⃣【凶器罩杯】：B 2️⃣【身高身材】：160 3️⃣【大概年纪】：20 4️⃣【 体重 】：93 5️⃣【服务内容】： #一条龙💋#洗澡💦#调情 💦#舌吻💦#制服💦💦#口爆💦#深喉💦#69互动💦#胸推💦#臀推💦#独龙🐲💦#舔蛋💦#做爱💦#无套💦 狼友精选好评：一直在找优秀的环保ls，今天找到西西，真的是来对了，所有细节拉满，老师的身材长相也是我喜欢的类型，皮肤很白，胸抓起来也很舒服，老师舌头口活超级顶，毒龙做的很到位，服务时间做满，真的很用心，必须反食
1️⃣【凶器罩杯】：A+ 2️⃣【身高身材】：165 3️⃣【大概年纪】：25 4️⃣【 体重 】：98 5️⃣【服务内容】： #一条龙💋#洗澡💦#调情 💦#舌吻💦#制服💦💦#口爆💦#深喉💦#69互动💦#胸推💦#臀推💦#独龙🐲💦#舔蛋💦#做爱💦#无套💦 狼友精选好评：今天起得很早，在群里刷到妹子，一看还可以就私了老师，刚问老师是早上，老师说刚醒还没起床，她说她还没化妆问我介意不。我就过去了，没想到老师真的纯素颜，颜值太抗打了，长得太可爱了，太可爱呀，老师是自聊验证过，放心冲狼友们。
1️⃣【凶器罩杯】：B 2️⃣【身高身材】：167 3️⃣【大概年纪】：21 4️⃣【 体重 】：95 5️⃣【服务内容】： #一条龙💋#洗澡💦#调情 💦#舌吻💦#制服💦💦#口爆💦#深喉💦#69互动💦#胸推💦#臀推💦#独龙🐲💦#舔蛋💦#做爱💦#无套💦 狼友精选好评：妹子真人确实比图好看，身材瘦瘦的，但有料，我喜欢的类型，进门引诱我洗澡，一边口一边抚摸，舌头非常柔软，对着床边镜子那个画面感确实棒！可能是我太久没有做了，加上妹子太骚了，下面太紧了，水又多，换了几个姿势 我就射了，完事妹子也很耐心的陪我聊天，让我感觉挺放松的
Showing the 11 most recent of 11 posts we hold for @kkjut64641. 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.
Citation-graph rank — 329,533 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 10 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.
@kkjut64641 named 5 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“武汉外围上门喝茶” (@kkjut64641), 1,180 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/kkjut64641.
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.