Telegram RegisterThe public register of Telegram
Telegram profile photo for 08可可

Channel

08可可

@putuo08keke0

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

153subscribers

+136 since we began measuring on 18 August 2026

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

Register entry

Telegram ID-1004361380098
TypeChannel
Username@putuo08keke0
Created26 July 2026measured — dated from the channel’s first post
First recorded18 August 2026
Last confirmed live25 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/putuo08keke0

Growth

171538518 August 2026 — 17 subscribers18 August 2026 — 29 subscribers25 August 2026 — 153 subscribers18 August 202625 August 2026
3 measurements spanning 7 days, net +136. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 21:02153+124
18 Aug 2026, 13:2329+12
18 Aug 2026, 11:3017first reading

Engagement

10 posts held, back to 26 July 2026the 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 · 30 days
34.2%
avg views ÷ 153 subscribers
Avg views / post
52.3
7 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
9
of 10 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 18 August 2026
Posts held10 (26 July 202618 August 2026)
Views total366
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Aug 2026, 11:30 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
7s
Average length
7s

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.

Recent posts

18 Aug 2026, 08:57 UTC56 viewsread 18 August 2026
Photo

🎉 萝莉岛(@shlldq) 萝莉岛 普陀 08可可老师半价券抽奖 🎁 奖品清单 • 1p半价劵 × 1 🛡️ 参与条件 • 加入 上海萝莉岛 • 加入 08可可 • 加入 上海萝莉岛榜单 • 加入 上海萝莉岛报告 • 加入 上海萝莉岛甄选 • 必须设置用户名 🔮 祝福加持 • 祝福消耗:10积分 • 祝福上限:5次 • 祝福一次增加一个抽奖号,提高中奖率 • 幸运值祝福:支持 幸运值说明 ⌛ 抽选时刻 • 2026-08-21 13:30:00 📜 抽奖说明 1️⃣本次抽奖由 08可可 老师赞助 @putuo08keke 2️⃣开奖后七天有效,请再七天内使用 3️⃣遇到问题请找唯一客服 @shlldbot ✨ 愿命运之剑指引你们前行,直至胜利之光照耀每一个人。

18 Aug 2026, 08:09 UTC56 viewsread 18 August 2026

‼️‼️展览会福利群: 免费拿5折6折7折优惠 和抽奖 白嫖 现金红包 本群专属手势认证高质量老师 上海艺术展览会福利群: https://t.me/+nFnE0wANtSRkMjEx 点击进去备用群 上海艺术展览会总榜单:https://t.me/+2i_egsiBxNFlNmJh 上海艺术展览会人气推荐榜 https://t.me/+vOj1VuT48NE3MDc1 上海艺术展览会中转平台 https://t.me/+-sIwH2NalFw2MzEy 展览会老师广告群 @shanghaiyishu 个人推荐频道88🧧 📡 上榜管理:@yishuja_bot 📡 管理秘书:@Yishujia798_bot

18 Aug 2026, 08:09 UTC54 viewsread 18 August 2026

上海奶茶妹高质量福利群: 主打嫩妹福利,抽奖竞拍半价6折。 现金红包🧧 上榜管理: @Naichacbot 上海奶茶妹交流群 https://t.me/+iSwJ-vAcG902N2E1 上海奶茶妹备用群 https://t.me/+38a0Y7pTMccyZjUx 上海奶茶妹高质量榜单 https://t.me/+PHc3J4BHv4pmMzg1 上海奶茶妹老师广告群 https://t.me/+VZrekuT90f5mN2Zl

18 Aug 2026, 07:52 UTC50 viewsread 18 August 2026

普陀:0️⃣8️⃣🉑🉑 身高:164cm。 体重:46kg 🐻 :c罩杯 课时:7p/40分。14pp/90分 fw:🐍💋 鸳鸯浴、阴推、 胸推、制服丝袜👠 自带gzs🉑外🉑✌️ 女友感十足,萝莉系嫩妹 真实08年,支持身份证验证

Showing the 10 most recent of 10 posts we hold for @putuo08keke0. 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

Citation-graph rank — 794,191 of 1,620,455entries 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.

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

“08可可” (@putuo08keke0), 153 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/putuo08keke0.

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.