Telegram RegisterThe public register of Telegram

Channel

大洋-车评报告

@cddy028

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

549subscribers

-2 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1003064618318
TypeChannel
Username@cddy028
CreatedBetween 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live13 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/cddy028

Growth

54955155012 Aug 2026, 23:17 — 551 subscribers13 Aug 2026, 05:23 — 549 subscribers12 Aug 2026, 23:1713 Aug 2026, 05:23
2 measurements taken within a single day, net -2. 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 549–551 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 05:23549-2
12 Aug 2026, 23:17551first reading

Engagement

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

ERR · 30 days
12.3%
avg views ÷ 549 subscribers
Avg views / post
67.3
6 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
6
of 6 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. It is computed over the 2 of 6 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 August 2026
Posts held6 (5 August 202611 August 2026)
Views total404
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 23:17 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
26s
Average length
4s

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

11 Aug 2026, 12:10 UTC29 viewsread 12 August 2026
Photo

大洋外围🌸会员反馈 因为专注|所以专业 【花名】: #成都媚媚 好评+1 【反馈】:除了不🐍,其他无短板 查看详情 感谢推荐,转介绍有礼 成都娱乐认准大洋包不坑 🥺永久ID联系 @dayang028 频道均为大洋会员反馈|或部分大洋亲自见面&以防踩雷

10 Aug 2026, 09:20 UTC41 viewsread 12 August 2026
Photo

大洋外围🌸会员反馈 因为专注|所以专业 【花名】: #成都大密 好评+1 【反馈】:会玩,服务好 查看详情 感谢推荐,转介绍有礼 成都娱乐认准大洋包不坑 🥺永久ID联系 @dayang028 频道均为大洋会员反馈|或部分大洋亲自见面&以防踩雷

7 Aug 2026, 16:15 UTC74 viewsread 12 August 2026
Photo

大洋外围🌸会员反馈 因为专注|所以专业 【花名】: #成都宣宣 好评+1 【反馈】:年轻漂亮,娇小可人,下面也很紧 查看详情 感谢推荐,转介绍有礼 成都娱乐认准大洋包不坑 🥺永久ID联系 @dayang028 频道均为大洋会员反馈|或部分大洋亲自见面&以防踩雷

6 Aug 2026, 14:09 UTC86 viewsread 12 August 2026
Photo

大洋外围🌸会员反馈 因为专注|所以专业 【花名】: #成都乐盈 好评+2 【反馈】:服务好,态度好,五星好评,十分满意 查看详情 感谢推荐,转介绍有礼 成都娱乐认准大洋包不坑 🥺永久ID联系 @dayang028 频道均为大洋会员反馈|或部分大洋亲自见面&以防踩雷

5 Aug 2026, 12:41 UTC92 views0 reactionsread 12 August 2026
Photo

大洋外围🌸会员反馈 因为专注|所以专业 【花名】: #成都小梨 好评+1 【反馈】: 情绪价值高,完事儿还一直按摩,好评不错 查看详情 感谢推荐,转介绍有礼 成都娱乐认准大洋包不坑 🥺永久ID联系 @dayang028 频道均为大洋会员反馈|或部分大洋亲自见面&以防踩雷

5 Aug 2026, 12:29 UTC82 views0 reactionsread 12 August 2026
Photo

大洋外围🌸会员反馈 因为专注|所以专业 【花名】: #上海兰兮 好评+1 【反馈】: 质量高,非常满意,强烈推荐 查看详情 感谢推荐,转介绍有礼 成都娱乐认准大洋包不坑 🥺永久ID联系 @dayang028 频道均为大洋会员反馈|或部分大洋亲自见面&以防踩雷

Showing the 6 most recent of 6 posts we hold for @cddy028. 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 — 395,896 of 1,478,351entries 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 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 August 2026 — this entry's latest reading, not the date you are reading this.

“大洋-车评报告” (@cddy028), 549 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/cddy028.

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.