Telegram RegisterThe public register of Telegram
Telegram profile photo for 重庆大圈每天更新 部分展示

Channel

重庆大圈每天更新 部分展示

@lo08003

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

3,999subscribers

-35 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001600589554
TypeChannel
Username@lo08003
CreatedBetween 1 November 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live21 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 21 August 2026
On Telegramt.me/lo08003

Growth

3,9954,0374,0167 August 2026 — 4,034 subscribers8 August 2026 — 4,030 subscribers11 August 2026 — 4,037 subscribers14 August 2026 — 4,000 subscribers17 August 2026 — 3,995 subscribers21 August 2026 — 3,999 subscribers3,9997 August 202621 August 2026
6 measurements spanning 13 days, net -35. 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 3,989–4,043 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Aug 2026, 02:563,999+4
17 Aug 2026, 16:353,995-5
14 Aug 2026, 18:194,000-37
11 Aug 2026, 11:044,037+7
8 Aug 2026, 08:314,030-4
7 Aug 2026, 16:024,034first reading

Engagement

5 posts held, back to 6 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
1.48%
avg views ÷ 3,999 subscribers
Avg views / post
59.0
5 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
5
of 5 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 7 August 2026
Posts held5 (6 August 20267 August 2026)
Views total295
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 05:42 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
19s
Average length
6s

Measured directly from 3 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

7 Aug 2026, 10:42 UTC50 viewsread 8 August 2026
Photo

⚠️ 请勿给妹妹现场展示本频道 🌟🌟 查看重庆大圈资源 🌟🌟 查看重庆中圈资源 🌟🌟 高端外围导航入口 🌟🌟 包养包月导航入口 🌟🌟 客户评价反馈频道 🌟🌟 客服大蜜蜜:@CY9818 🌟🌟 双向客服:@cy918_bot

7 Aug 2026, 10:42 UTC42 viewsread 8 August 2026
Photo

车展御用模特 瑜伽爱好者健身达人 04可以年173D 性感 会吸 会夹 超级主动 单单好评 通体雪白 细腻光滑 完美腰臀比例 御姐范** 温柔如初恋 提供情绪价值,风骚性感🔥好不事

7 Aug 2026, 10:42 UTC48 viewsread 8 August 2026
Photo

5⬆️质量 🉑️纯🉑️御身高173体重/50kg 胸围/d 纯天然真🐻 🔷:颜值天花板 精致气质款 🔷:纯欲甜美 穿着高级 🔷:谈吐优雅 综合素质极高 🔷: 皮肤白嫩细腻 蜜桃臀 可Jk 丝袜 👙 🔷:照片和视频都是本人 所见即所🉐️ 只接正常🥚🈲不做安全措施 每天限量治挑

6 Aug 2026, 09:50 UTC78 viewsread 8 August 2026
Photo

⚠️ 请勿给妹妹现场展示本频道 🌟🌟 查看重庆大圈资源 🌟🌟 查看重庆中圈资源 🌟🌟 高端外围导航入口 🌟🌟 包养包月导航入口 🌟🌟 客户评价反馈频道 🌟🌟 客服大蜜蜜:@CY9818 🌟🌟 双向客服:@cy918_bot

6 Aug 2026, 09:50 UTC77 viewsread 8 August 2026
Photo

#重庆水原希子 海航空姐 短开兼职 𝐇𝐞𝐢𝐠𝐡𝐭. 171 𝐖𝐞𝐢𝐠𝐡𝐭. 98 𝐁𝐮𝐬𝐭. D 幽默风趣性格开朗 只接待素质课 温文儒雅 谈吐优雅

Showing the 5 most recent of 5 posts we hold for @lo08003. 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 — 450,906 of 1,584,733entries 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 2 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 21 August 2026 — this entry's latest reading, not the date you are reading this.

“重庆大圈每天更新 部分展示” (@lo08003), 3,999 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/lo08003.

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.