Telegram RegisterThe public register of Telegram
Telegram profile photo for 厦门桃花岛(公开认证榜)

Channel

厦门桃花岛(公开认证榜)

@xmthdb

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry

34,704subscribers

+11,023 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002231571935
TypeChannel
Username@xmthdb
Description厦门公开聊天群: https://t.me/xmthdxmthdxmthd1 上榜联系: @csysxjqr123bot 老师报告:https://t.me/THDTHDTHDTHD
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 November 2026
Measurements held63
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/xmthdb

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 9 September 2026 and assigned it the closest of 31 fixed categories, at 64% 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 the other topics.

Growth

23,58934,70429,146.57 August 202612 November 2026
63 measurements spanning 96 days, net +11,023. 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 21,922–36,371 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)SubscribersChange
12 Nov 2026, 07:5834,704+72
10 Nov 2026, 08:3934,632+16
8 Nov 2026, 20:3134,616+77
7 Nov 2026, 12:4634,539+13
6 Nov 2026, 11:4034,526+73
5 Nov 2026, 14:5134,453+54
4 Nov 2026, 15:0634,399+78
3 Nov 2026, 15:4634,321+130
2 Nov 2026, 17:3934,191+124
1 Nov 2026, 15:1934,067-27
31 Oct 2026, 16:2934,094+46
30 Oct 2026, 18:5734,048+14
29 Oct 2026, 20:5734,034+89
28 Oct 2026, 23:3133,945-38
27 Oct 2026, 21:1833,983+76
26 Oct 2026, 18:2733,907+3
25 Oct 2026, 20:2933,904+55
24 Oct 2026, 19:2633,849+36
23 Oct 2026, 22:2033,813+43
22 Oct 2026, 22:0733,770first reading

Engagement

166 posts held, back to 3 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 174 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.80%
avg views ÷ 34,704 subscribers
Avg views / post
2,010
71 posts measured
Reaction rate
0.082%
reactions ÷ views · ER floor
Posts in window
71
of 166 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 57 of 71 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 14 November 2026
Posts held166 (3 August 2026 – 14 November 2026)
Views total142,790
Reactions total95
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Nov 2026, 19:40 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,810
Videos
≈459
Links
≈241

Lifetime counters from Telegram’s own channel header, read 14 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
16m 09s
Average length
10s

Measured directly from 93 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.

Reaction mix

394 reactions across 123 posts, in 12 distinct kinds. The most used accounts for 84.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤33284.3%
👍174.31%
👎153.81%
🔥133.30%
👀51.27%
🍓30.761%
👏30.761%
🥰20.508%
💋10.254%
😘10.254%
🤔10.254%
🤩10.254%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 143 of the 166 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 394 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 166 most recent posts we hold, published 3 August 2026 to 14 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

Telegram’s own ‘edited’ marker: 5 of 71 posts held from the last 30 days (7.04%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

14 Nov 2026, 04:10 UTC≈1,200 viewsread 14 November 2026
Photo

#已验 #湖里区 #电报老师 #5张 #雨欣 #服务 性价比高服务好可双飞可半套,老师会所出身,表哥们可以体验下,🉑蛇可6🉑毒放得开,三件套玩哆了可以试一试这服务体验 已通过视频验证 个人电报: @xmyx168 个人频道: https://t.me/xmyx1688

14 Nov 2026, 01:02 UTC≈1,440 views2 reactionsread 14 November 2026
Photo

#已验 #湖里区 #电报老师 #4张 #小米 #服务系 #会所 #莞式服务 性价比极高,且服务态度特别好的老师喜欢服务的可以体验一下服务,真的没得说,简直是123的天堂,性价比双飞 已通过视频验证 个人电报: @xiaomi8880 个人频道: https://t.me/xiaomi520666888

❤1👍1

13 Nov 2026, 05:39 UTC≈2,020 views4 reactionsread 14 November 2026
Photo

#已验 #6张 #电报老师 #水多耐桩 #服务好 #嫩妹 #兰兰 #湖里区 165体重94🌟🉑🐍🉑六九口活一流回吸会夹,可角色扮演,还有制服丝袜等等 已通过视频验证本人 电报联系方式: @hhjjyao 电报个人频道: https://t.me/yaoyaoaabb

❤4

13 Nov 2026, 04:24 UTC≈2,040 views1 reactionsread 14 November 2026
Photo

#已验 #6张 #奶豆 #电报老师 #水多耐桩 #服务好 #湖里区 164体重90🌟人美生甜,服务好,本人比视频照片更甜情绪很好天然大c可亲可69口活很好 已通过视频验证本人 电报联系方式: @ndkj666 个人频道: https://t.me/naidou678

❤1

12 Nov 2026, 15:25 UTC≈1,800 views1 reactionsread 13 November 2026
Photo

#已验 #思明区 #电报老师 #5张 #清予 #服务好 服务型老师表哥们嫩妹吃多了可以来享受一下服务老师也做95服务没得说,主打一个情绪价值主打,不会让你拘束每时每刻老师都在挑逗你的情绪 体验感特别好会让你感觉特别值得,毕竟服务多基本上都能待个40分钟起步 已通过视频验证 个人电报: @qingyuaini 个人频道: https://t.me/qingyu1998

❤1

12 Nov 2026, 05:11 UTC≈2,160 views0 reactionsread 13 November 2026
Photo

集美精品工作室 【92】 💯安全私密,独立房间,一对一个人服务 ⏰时间:14:00-01:00 🚩主打厦门最高端工作室,房间氛围直接拉🈵 情趣变装 制服 丝袜 ✅基础项目:高山流水,猴子偷逃,蚂蚁上树 胸推 手推 足交 丝袜诱惑,性感胸滑 日式调情 三角区护理 制服诱惑 情趣换装 冰🔥 🔷基础项目价格:468(60分钟,不限次数) 📺加钱656项目:抓龙筋 热舞 情趣变装 预约体验优惠价 📢预约请联系:@jiuqo,获取实时空闲技师。(个人工作室须提前预约技师,防止跑空) 📍地址导航:集美区嘉庚

12 Nov 2026, 03:15 UTC≈1,520 viewsread 12 November 2026
Photo

#已验 #湖里区 #电报老师 #6张 #软糖 #服务系 #可蛇 #可69 老师之前的号被盗了小心被骗这个是新号 已通过视频验证 个人电报: @ruantang2212 个人频道: https://t.me/ruantang16888

11 Nov 2026, 09:36 UTC≈1,840 viewsread 12 November 2026
Photo

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_5565405281

11 Nov 2026, 06:02 UTC≈1,950 views2 reactionsread 12 November 2026
Photo

#已验 #湖里区 #电报老师 #6张 #玫瑰好 #服务 #可🐍 #可69 服务型老师口活很好特别是深厚123根本抵不住服务👌应该之前有在会所做过95 奶子狠软摸可以2奶一吃 已通过视频验证 个人电报: @Aa1891203 个人频道: https://t.me/rosemary20252

❤2

11 Nov 2026, 04:10 UTC≈1,550 views1 reactionsread 12 November 2026
Photo

#已验 #湖里区 #电报老师 #5张 #萱萱 #服务 #可🐍 #可69 已通过视频验证 个人电报: @Xuan25888 个人频道:https://t.me/XMYY111000

❤1

10 Nov 2026, 11:21 UTC≈1,910 views0 reactionsread 11 November 2026
Photo

#已验 #湖里区 #电报老师 #6张 #沫沫 #服务好 #可kiss 老师今天刚刚到的下高铁就上班表哥们可以提前预约老师的下海第一课先到先得,主打一个活泼主动可能刚刚到厦门会有点腼腆不过没关系表哥们教一教就熟练了,可亲老师还是36d看着就有感觉,老师偶尔还健身 已通过视频验证 个人电报: @mx2266 个人频道: https://t.me/tm996677

10 Nov 2026, 09:51 UTC≈1,730 viewsread 11 November 2026
Photo

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_5565405281

Showing the 12 most recent of 166 posts we hold for @xmthdb. 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.

Posts edited after publishing

@xmthdb edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
23 October 2026
Most recent edit
27 October 2026

Posts recorded as deleted after publishing

We recorded 3 posts on @xmthdb as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
8 August 2026
Most recent seen missing
11 November 2026
Median time before seen missing
32 hours
Seen missing in the last 30 days
2

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.

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 12 November 2026 — this entry's latest reading, not the date you are reading this.

“厦门桃花岛(公开认证榜)” (@xmthdb), 34,704 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/xmthdb.

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.