近期因为有人冒充潇湘阁修车 ⚠️⚠️⚠️ 下单请认准 😍 菲-泰-等..国 (助理) :@XXGE8 🥰 新-马-等..国(助理):@XXGE888 @lxl168 此号将慢慢不再接待 ❤️ 认 准 👆 ↑ 上方三个 ⚠️⚠️⚠️除此以外 都是假的 ↓ ↓ 频 道 导 航 ↓ ↓ 越南频道 @Bangkokxxg000 泰妹频道 @Bangkokxxg001 日韩大洋马 @Bangkokxxg003 外围高端中国 @Bangkokxxg004 潇湘阁 各国 在岗频道导航

Channel
曼谷泰妹💃芭提雅泰妹💃泰国泰妹💃曼谷泰国妹子
@Bangkokxxg001
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
4,462subscribers
+682 since we began measuring on 2 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001967265360 |
|---|---|
| Type | Channel |
| Username | @Bangkokxxg001 |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 September 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/Bangkokxxg001 |
Topic
Adult — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 16 September 2026 and assigned it the closest of 31 fixed categories, at 65% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 16:37 | 4,462 | +18 |
| 12 Sept 2026, 18:18 | 4,444 | +158 |
| 9 Sept 2026, 02:57 | 4,286 | +357 |
| 3 Sept 2026, 11:56 | 3,929 | +149 |
| 2 Sept 2026, 11:15 | 3,780 | first reading |
Engagement
6 posts held, back to 26 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 1.74%
- avg views ÷ 4,462 subscribers
- Avg views / post
- 77.8
- 6 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- 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.
| Window | Rolling 30 days · latest post in window 1 September 2026 |
|---|---|
| Posts held | 6 (26 August 2026 – 1 September 2026) |
| Views total | 467 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 11:15 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
- 13s
- Average length
- 7s
Measured directly from 2 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
🇹🇭泰国:#曼谷 ⚜️姓名: 星星 ⚜️年龄:19岁 ⚜️身高:157 ⚜️体重:53公斤 ⚜️三围:34/27/38 ⚜️牙套: 没 ⚜️胸部: 真胸 ⚜️包养: 接保养 ⚜️陪嗨: 可以 ⚜️职业: 兼职 ⚜️语言: 中英泰 ⚜️备注: 没整容 会中文沟通方便 1小时1次 8000 6小时2次 15000 上门+1000 偏远另算
🇹🇭泰国:#曼谷 ⚜️姓名: sprite ⚜️年龄:23岁 ⚜️身高:170厘米 ⚜️体重:50公斤 ⚜️三围:32/24/38 ⚜️牙套: 没 ⚜️胸部: 真胸 ⚜️包养: 接保养 ⚜️陪嗨: 可以 ⚜️职业: 兼职 ⚜️语言: 中英泰 ⚜️备注: 没整容 会中文沟通方便 1小时1次 8000 6小时2次 15000 上门+1000 偏远另算
https://t.me/dcvbniuyt
近期因为有人冒充潇湘阁修车 新老客户有上当 我们修改了联系方式 尽量避免再被模仿 和 减少新老客户上当 😍 菲-泰-等..国 (助理) :@XXGE8 🥰 新-马-等..国(助理):@XXGE888 @lxl168 此号将慢慢不再接待 ⚠️⚠️⚠️⚠️ 近期有冒仿着 下单请认准 此频道联系人 助理 ❤️ 认 准 👆 ↑ 上方三个 ⚠️⚠️⚠️除此以外 都是假的
新人极品 中国A牌 刚刚落地,可放心推,皮肤白, 身高165.,00年.48公斤,🐻C,真胸 陪酒4-5小时 15000 1小时1次 16000 6小时2次 45000 酒夜 55000 - 包天 70000
Showing the 6 most recent of 6 posts we hold for @Bangkokxxg001. 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 6 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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“曼谷泰妹💃芭提雅泰妹💃泰国泰妹💃曼谷泰国妹子” (@Bangkokxxg001), 4,462 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/Bangkokxxg001.
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.