#同安区 #沐朵 #5米 #服务系 #BBW #69 #毒龙 服务内容:见照片课表 已过群友验证,是本人自聊 联系方式: @muduo95 双向联系: @muduozhushou_bot 个人频道: t.me/muduo98
❤1👍1

Channel
@xmzygxpd
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
8,385subscribers
-16 since we began measuring on 6 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003458219313 |
|---|---|
| Type | Channel |
| Username | @xmzygxpd |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/xmzygxpd |
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 25 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Nov 2026, 10:05 | 8,385 | +12 |
| 5 Nov 2026, 10:16 | 8,373 | +23 |
| 2 Nov 2026, 07:34 | 8,350 | +8 |
| 30 Oct 2026, 04:08 | 8,342 | +7 |
| 27 Oct 2026, 02:36 | 8,335 | +2 |
| 23 Oct 2026, 22:46 | 8,333 | +13 |
| 20 Oct 2026, 20:49 | 8,320 | +19 |
| 17 Oct 2026, 15:05 | 8,301 | +3 |
| 14 Oct 2026, 09:39 | 8,298 | +33 |
| 10 Oct 2026, 12:41 | 8,265 | -77 |
| 4 Oct 2026, 19:19 | 8,342 | +24 |
| 25 Sept 2026, 03:57 | 8,318 | -111 |
| 17 Sept 2026, 04:18 | 8,429 | +9 |
| 13 Sept 2026, 15:18 | 8,420 | -9 |
| 9 Sept 2026, 15:41 | 8,429 | +28 |
| 6 Sept 2026, 15:22 | 8,401 | no change |
| 6 Sept 2026, 14:47 | 8,401 | first reading |
17 posts held, back to 4 September 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 11 pages of Telegram’s post history, 20 posts per page.
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 7 November 2026 |
|---|---|
| Posts held | 17 (4 September 2026 – 7 November 2026) |
| Views total | 15,945 |
| Reactions total | 64 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Nov 2026, 00:28 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.
Measured directly from 7 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.
87 reactions across 17 posts, in 4 distinct kinds. The most used accounts for 52.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 46 | 52.9% | |
| 🤮 | 27 | 31.0% | |
| 👍 | 13 | 14.9% | |
| 🔥 | 1 | 1.15% |
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 17 of the 17 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 87 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 4 September 2026 to 7 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.
Telegram’s own ‘edited’ marker: 0 of 11 posts held from the last 30 days (0%) 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).
#同安区 #沐朵 #5米 #服务系 #BBW #69 #毒龙 服务内容:见照片课表 已过群友验证,是本人自聊 联系方式: @muduo95 双向联系: @muduozhushou_bot 个人频道: t.me/muduo98
❤1👍1
#湖里 #林豆豆 #五米 #舌吻 #嫩妹 #包时 之前上榜过,湖里02年嫩妹林豆豆,有5米和6米两个课表,边上班边下海兼职,女友感爆棚,🉑🐍🉑69🉑上门 电报: @Ldd131288 频道:https://t.me/XMGRLdd131288 双向联系: @DoudouLinbot
❤1
新群聊 @xmzygxpdhcq 群满3000人抽老师免单券优惠券
❤2
#顾梓萱 #湖里 #7米 #69 #舌吻 #御姐 之前上榜过,身材服务各方面评价都很高,模特身材人照一致,纯天然无整情绪价值高,服务内容:🉑陪浴🉑69🉑🐍吻,花式吹箫亲胸舔蛋制服丝袜激情爱爱 联系方式: @gzx05 个人频道:https://t.me/gzx997 双向联系: @gzxxzs_bot 资源备用频道: https://t.me/XMzsgzypd
❤3👍3🔥1
厦门最有性价比的保养频道,靠谱放心,有售后。 联系方式 @xiaow880 频道 https://t.me/txdtll000 聊天群 https://t.me/xiaow99909 双向 @guqingw999_bot
🤮4👍2❤1
#小樱 #翔安 #5米 #🉑亲 #兼职下海 翔安兼职刚下海的老师,会的服务不多,但是相当听话配合,🉑亲,有任何不足可以提出,会慢慢改进 联系: @VA772667570 频道: https://t.me/a772667570 双向: @VA772667570bot V: A772667570
❤7🤮3👍1
#湖里枋湖 #安琪 #4米 #包时 #姐妹花 #双飞 25岁御姐安琪,天然34B罩杯,有点御姐风,服务态度蛮好,🉑69,1p400,包时800一小时,可以和姐姐小米一起双飞🤔,已过群友们验证 报告1 报告2 电报: @anqi8886 个人频道:https://t.me/anqi520666888 双向联系: @anqi520bot 上榜联系: @xmzqz118
🤮6❤2👍1
#可可 #湖里围里 #3米 #4米 湖里区新来的快餐老师可可,快餐300,全套400,详情见照片课表,已过视频验证 联系方式: @TTianzi88 个人频道: https://t.me/httpsRe0ItU3GcQJmN2Ux 双向联系: @ttianzi88_bot
❤5🤮4👍1
#安然 #湖里万达附近 #69 #5米 之前上榜过,性价比非常高❤️服务态度很好,🉑69,御姐风配合程度高,在岛内性价比高,🉑包时一小时内不限次数包配合 联系方式 @Anr88800 个人频道 https://t.me/XMAnr000 双向联系 @Arn888000bot
❤3👍1🤮1
祝清枝的号炸了,重新联系新号 @xmzqz118 后续继续挖掘新资源
❤2🤮1
#小泪 #思明何厝 #5米 #69 #🐍吻 #包时 之前上榜过,童颜巨乳很有女人味,服务内容:鸳鸯浴 69 无套口 🐍吻 激情爱爱 配合程度高 用户名 @dhdhddbh 双向 @sjsjbotqjsjbot 频道 https://t.me/xiaoleidehdhhs
❤5👍1🤮1
海沧新垵的快餐影子,去海沧必吃的一个性价比老师,快餐200,全套还有待开发,已过广大群友验证,有种小女友的感觉。 报告1 联系方式: @yingzi1213 个人频道: https://t.me/yingzi2233
❤4🤮2👍1
Showing the 12 most recent of 17 posts we hold for @xmzygxpd. 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.
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.
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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“厦门资源共享频道” (@xmzygxpd), 8,385 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/xmzygxpd.
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.