Telegram RegisterThe public register of Telegram

Channel

dongnanya

@du185

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

10,233subscribers

-2 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002010285676
TypeChannel
Username@du185
Description本频道为失联导航 东南亚大事件永久ID: @cc199
Created9 May 2024measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/du185

Growth

10,23310,23510,2346 August 2026 — 10,235 subscribers6 August 2026 — 10,235 subscribers9 August 2026 — 10,234 subscribers13 August 2026 — 10,233 subscribers6 August 202613 August 2026
4 measurements spanning 6 days, 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 10,233–10,235 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 01:0310,233-1
9 Aug 2026, 00:5110,234-1
6 Aug 2026, 22:1510,235no change
6 Aug 2026, 22:0610,235first reading

Engagement

3 posts held, back to 9 May 2024the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 16 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
no view readings in window
Avg views / post
no view readings
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 3 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 August 2026
Posts held3 (9 May 20244 August 2026)
Views total
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 05:19 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

Photos
1

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

11 Jun 2025, 08:56 UTC≈3,860 viewsread 13 August 2026
Photo

避免官方封禁频道请关注: 东南亚大事件官方旗下媒体 👇👇👇 东南亚大事件: @cc199 热搜搞笑吃瓜: @cx681 海外人设素材: @TGQQSC 东南亚上头DJ:@LIKE_DJ 文案馆头像: @du153 网红私密曝光:@cx1670 表情包贴纸GIF: @bqbq199 二手交易频道: @du139 求职招聘甩人: @du163 动漫国漫频道: @tzdm18oo 电影电视剧频道: @du160 足球联赛预测: @cx164 TG万能搜索群: @wnss456 查U地址监控: @USDTYEJK_bot ⭐️投稿商务爆料: @cx167 ✅

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

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.

“dongnanya” (@du185), 10,233 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/du185.

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.