Telegram RegisterThe public register of Telegram
Telegram profile photo for 桃桃酱

Channel

桃桃酱

@ttkk68680

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

487subscribers

+231 since we began measuring on 4 November 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003855173799
TypeChannel
Username@ttkk68680
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 November 2026
Last confirmed live5 November 2026
Measurements held2
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/ttkk68680

Growth

256487371.54 Nov 2026, 17:22 — 256 subscribers5 Nov 2026, 12:19 — 487 subscribers4 Nov 2026, 17:225 Nov 2026, 12:19
2 measurements taken within a single day, net +231. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 221–522 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Nov 2026, 12:19487+231
4 Nov 2026, 17:22256first reading

Engagement

20 posts held, back to 2 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 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
40.7%
avg views ÷ 487 subscribers
Avg views / post
198
3 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
3
of 20 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 4 November 2026
Posts held20 (2 August 2026 – 4 November 2026)
Views total595
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken4 Nov 2026, 17:22 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.

What this channel posts

Video runtime
1s
Average length
1s

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

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.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 1 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 1 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 2 August 2026 to 4 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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 3 posts held from the last 30 days (0%) 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).

4 Nov 2026, 14:07 UTC130 viewsread 4 November 2026
Video

🎰 俱乐部 联合 娜优&桃桃酱 发福利啦 📮 参与条件: 🎫 加入-桃桃酱 🎫 加入-娜优 🎫 加入-✨小天涯·日记✨ 🎫 加入-༺ཌༀ成都修车俱乐部•车库ༀད༻ 🎫 加入-༺ཌༀ成都修车俱乐部ༀད༻ └ 🔑 发送口令﹝娜优与桃桃酱 祝俱乐部的哥哥们天天开心﹞ ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ 48元口令红包🧧 × 1 💰️ 50元口令红包🧧 × 2 💰️ 68元口令红包🧧 × 1 💰️ 88元口令红包🧧 × 1 💰️ 俱乐部666积分 × 3 💰️ 桃桃酱200元通用优惠券 × 5 ⚠️ 抽奖说明: ✨俱乐部白嫖口令不间断✨ 1.口令红包兑换有效期为开奖后48小时内,逾期作废! 2.本次优惠券不可折现,优惠券兑奖有效期为开奖后7天内,逾期作废! 3.因没有用户名,炸号,退群,注销账号等原因,超时未兑换等原因的,不予兑奖! 4.中途退群退频道,乱水群都会取消中奖资格! 5.口…

1 Oct 2026, 17:47 UTC598 views1 reactionsread 4 November 2026

四川🔎情报局📊专用工兵报告 [大群]:https://t.me/ojboo [留名]:#进击的小居居 [时间]:2026.09.25 [花名]:#桃桃酱 [年龄]:26 [胸器]:胸A+ [车费]:700p 1100pp [车牌]:@dmkk68680 [人照]:8.5分,本人,和视频几乎一样 [模式]:#代聊 [地址]:理工大学附近 [环境]:干净卫生,在小区里面 [服务]:按摩,指滑,毒龙,口,胸推 [态度]:9分 [优点]:颜值不错,良家感十足,身材也很好,课表有的服务基本上都做了一遍,床上比较配合,做服务也很认真,而且有什么要求都会尽量满足,能让妹子一直口,态度还是非常不错,好评 [缺点]:没有🐍,良家兼职,不是随时都有空 [简评]:妹儿颜值很高,长相没得说,挺好看,而且身材好,服务态度也不错。下面真的超级紧,服务也非常耐心和配合,尤其是后入非常爽,日感相当好。颜值控,还有喜欢有良家感的狼友,一定不要错过,但是请轻点…

❤1

22 Sept 2026, 08:50 UTC633 viewsread 4 November 2026

👙【花名】:桃桃酱 📊综合评分: 8.25 人照评分: 8 颜值评分: 8.5 身材评分: 8 服务评分: 8.5 环境评分: 8 态度评分: 8.5 👍【车牌】:@dmkk68680 👍【收费】:#7P,#11PP 【时间】:2026-09-22 👍【评价人】:乌鸦 👍【坐标】:成华区,东郊记忆 👍【类型】:御姐,服务车,态度车,御姐车 🏷【标签】:#情趣,#御姐,#鸳鸯戏水,#无套口,#态度车 👍【总结】:✍️总结:今日秋高气爽 ,浅算一卦,今日宜出击。果不其然,在群里看见了桃桃,非常符合我乌鸦哥的口味,果断拿下。 进门就看见妹妹俏生生的站在门后,北方有佳人,绝世而独立,说的就是桃桃了。168的身高搭配上前凸后翘的身材,很完美。 洗完躺在床上,佳人为我按摩、指滑、毒龙,感受着柔软在我背后,心跳逐渐加速。翻过身来,桃桃对我上下其手,口技略显生疏,但是持久,会贴心的问我要不要口的久一点。 桃桃偏小,磨蹭了几下才进去,女上技术…

22 Sept 2026, 03:36 UTC519 viewsread 4 November 2026

🌸【成都海花集修车群】🌸 专用报告 🌸基础信息🌸 【妹子花名】:#桃桃酱 【妹子车牌】:@dmkk68680 【验证留名】:@tianyalang123 【验证时间】:2026.09.21 【所在位置】:理工大学 【修车水费】:7P 11PP 【是否代聊】:代聊 🌸硬件评价🌸 【身高体重】:身高165,体重45 ,基本无纹身,锁骨处只有一小行英文字母,可以忽略。皮肤手感好,光滑细腻。 【妹子年龄】:26 【湿度紧度昆感】:老师的户型相当粉嫩,下面很湿,而且特别紧,不愧是良家兼职,周围毛量正常 【颜值相似】:人照8.5分,是本人,跟那个视频9分像,颜值好看,有气质,御姐风 【凶器罩杯】:胸型A+,胸部手感好,乳头红黑色,奶子揉着爽,很软很滑 🌸软件评价🌸 【环境卫生】:交通方便,靠近理工大学地铁口,房间整洁干净,出入方便,小区里面 【服务内容】:按摩,指滑,胸推,毒龙(用果冻),口 【机车行为】:无 …

Showing the 12 most recent of 20 posts we hold for @ttkk68680. 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.

Mentions

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.

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 5 November 2026 — this entry's latest reading, not the date you are reading this.

“桃桃酱” (@ttkk68680), 487 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/ttkk68680.

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.