Telegram RegisterThe public register of Telegram
Telegram profile photo for 曼谷修车 中国 农夫修车

Channel

曼谷修车 中国 农夫修车

@mangugirl888

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

14subscribers

+1 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002261974514
TypeChannel
Username@mangugirl888
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live28 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/mangugirl888

Growth

131413.58 August 2026 — 13 subscribers12 August 2026 — 13 subscribers28 August 2026 — 14 subscribers8 August 202628 August 2026
3 measurements spanning 21 days, net +1. 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 13–14 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 23:5214+1
12 Aug 2026, 03:0213no change
8 Aug 2026, 04:3213first reading

Engagement

3 posts held, back to 21 May 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
64.3%
avg views ÷ 14 subscribers
Avg views / post
9.0
2 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
2
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 5 August 2026
Posts held3 (21 May 20265 August 2026)
Views total18
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 03:02 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
8s
Average length
8s

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

5 Aug 2026, 02:28 UTC9 viewsread 12 August 2026
Photo

🇨🇳曼谷外围 · 06年纯天然在校女大学生首秀🇨🇳 👑 艺名: #小诺 中国🇨🇳 · S级 ✨硬件数据 📐 身高:170cm / 50kg 🍒 胸围:天然 B Cup 🎂 年龄:20岁(06年已成年) 🗣 语言:中文丝滑沟通 🌟 独家魅力 🎀 纯天然少女脸,满分邻家小妹既视感🥰 首次出国兼职,活泼有趣,毫无商业油腻感💯 真实在校学生,可查学信网/班级群,保真含苞待放🛁 第一次下水体验,服务配合度极高,听话乖巧 🇹🇭高端越南 🇹🇭高端日韩 🇹🇭高端中国 🇹🇭高端欧美 🇹🇭私聊客服详解甜蜜的爱 👈 🇹🇭备用客服👈 #泰国修车 #泰国选妃 #泰国外围 #泰国会所 #泰国上门

5 Aug 2026, 02:25 UTC9 viewsread 12 August 2026
Photo

🇹🇭曼谷外围 · 纯欲天花板首度惊艳亮相 🇹🇭 👑 艺名: #小雨(中国🇨🇳 · S级 ✨硬件数据 📐 身高:163cm / 40kg 🍒 胸围:34C 天然真胸 🎂 年龄:19岁 🗣 语言:中文丝滑沟通 🌟 独家魅力 💎杭州极品囡囡,初恋感十足的纯欲天花板 🎀甜美温柔,互动黏人且极具恋爱氛围 💯冰肌玉肤,全身粉嫩动人,状态极佳 🛁细节控天花板,配合度满分,节奏温柔缠绵 🇹🇭高端越南 🇹🇭高端日韩 🇹🇭高端中国 🇹🇭高端欧美 🇹🇭私聊客服详解甜蜜的爱 👈 🇹🇭备用客服👈 #泰国修车 #泰国选妃 #泰国外围 #泰国会所 #泰国上门

21 May 2026, 09:05 UTC84 viewsread 12 August 2026
Photo

angkok•中国🇨🇳•(新人•漫漫) 𝐇𝐞𝐢𝐠𝐡𝐭/168 🐻𝐁𝐮𝐬𝐭/c+ 01年 * 风趣幽默 小淘气会撩人 * 床上功夫绝 * 内里疯狂 偷心小猎 懂分寸 知情趣 * 有耐心 初恋的感觉 天生敏感体质 💦多 会夹 床上让你欲罢不能 爽到极致 全能高手 接触后就会懂 *可纯可欲 情绪价值极高 —————————————— 🇹🇭高端越南 🇹🇭高端日韩 🇹🇭高端中国 🇹🇭高端欧美 🇹🇭私聊客服详解甜蜜的爱 👈 🇹🇭备用客服👈 #泰国修车 #泰国选妃 #泰国外围 #泰国会所 #泰国上门

Showing the 3 most recent of 3 posts we hold for @mangugirl888. 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 — 98,291 of 1,627,068entries 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 28 August 2026 — this entry's latest reading, not the date you are reading this.

“曼谷修车 中国 农夫修车” (@mangugirl888), 14 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/mangugirl888.

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.