14 Aug 2026, 13:03 UTC259 viewsread 28 August 2026
开课🎯
Channel
🐟池池
@tungtti76
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
350subscribers
-53 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002790268022 |
|---|---|
| Type | Channel |
| Username | @tungtti76 |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/tungtti76 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 04:59 | 350 | -30 |
| 6 Sept 2026, 05:37 | 380 | -18 |
| 29 Aug 2026, 09:43 | 398 | -5 |
| 28 Aug 2026, 20:30 | 403 | no change |
| 28 Aug 2026, 20:15 | 403 | first reading |
Engagement
11 posts held, back to 11 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 11 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
- 45s
- Average length
- 6s
Measured directly from 7 videos 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.
Recent posts
13 Aug 2026, 09:13 UTC298 viewsread 28 August 2026
Video
猜猜我弹的啥🫣
10 Aug 2026, 08:30 UTC384 viewsread 28 August 2026
Video
说～你喜欢上谁了📞
4 Aug 2026, 11:37 UTC425 viewsread 28 August 2026
Photo
【艺名】： #冒泡小鱼 【地址】： #上城区 【联系】： @GUOMEME 【频道】： https://t.me/tungtti76 👇下面评论区留言👇
4 Aug 2026, 11:31 UTC451 viewsread 28 August 2026
https://t.me/kuaile88yijifa
3 Aug 2026, 12:27 UTC435 viewsread 28 August 2026
Video
开课
30 Jul 2026, 11:46 UTC463 viewsread 28 August 2026
Forwarded from @hangzhourzzy
【老师花名】: 冒泡小鱼🫧 【联系方式】: @GUOMEME 【位置坐标】: 拱墅区 课室 【验证留名】: k good 【出击时间】: 7/28 【凶器罩杯】: D➕ 【上课花费】: 1600/p 【修车细节】: 颜值很高的一位御姐 像极了我高中时候的校花，丰满的身材很让人喜欢，内心充满了激动，快速完成洗漱，老师帮我擦干，看着老师的精致的面容，忍不住亲了上去，到了床上当然还是从最喜欢的舌吻环节开始，和老师舌头疯狂的纠缠在一起，接下来老师开始服务，不得不说老师的口技还是不错的，看着老师口的那么认真，精神得到了极大的满足，实在忍不住戴上套套先是女上起手，边🐍边顶了一阵，切换传教士，大长腿架在我的身上，下面开始疯狂的进出，忍不住又和老师继续🐍接…
25 Jul 2026, 07:41 UTC575 viewsread 28 August 2026
Photo
冒个泡🫧
20 Jul 2026, 10:30 UTC611 viewsread 28 August 2026
Forwarded from @hxhzbgb
【老师花名】: 冒泡小鱼🫧 【联系方式】: @GUOMEME 【位置坐标】: 拱墅区 课室 【验证留名】: 顾 【出击时间】: 7/18 【凶器罩杯】: D➕ 【上课花费】: 1600/p 【修车细节】: 今天再次约了这个甜美妹子，她准备了超多惊喜！一进门就看到她穿着黑色超薄丝袜，配上性感吊带情趣内衣，D杯被紧紧包裹，蕾丝边缘若隐若现，那双修长腿在丝袜包裹下显得又滑又嫩，简直是行走的丝袜诱惑。 她娇羞地问哥哥今天想玩什么角色，我说想看学生妹，她立刻换上白衬衫+短裙+黑丝袜，乖乖叫我“老师”，跪坐在床边用丝袜美腿轻轻摩擦我，丝袜的触感顺滑又带着微微的摩擦力，简直要命！随后她主动骑上来，情趣内衣半解，D杯在面前晃动，一边扭腰一边用甜甜的声音说“老…
20 Jul 2026, 08:17 UTC506 viewsread 28 August 2026
Video
⚽️赛看完了，也该想起我了吧……
11 Jul 2026, 17:46 UTC532 viewsread 28 August 2026
Forwarded from @hangz_laosj_002Photo
花名：#小鱼 位置：#拱墅区 联系：@GUOMEME 费用：16p28PP #16/28 标签：#嫩妹（舌吻.69）
Showing the 11 most recent of 11 posts we hold for @tungtti76. 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 1 registered channel — 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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“🐟池池” (@tungtti76), 350 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/tungtti76.
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.