Telegram RegisterThe public register of Telegram
Telegram profile photo for 洗米国际官方频道

Channel

洗米国际官方频道

@xmpc28

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

443subscribers

-225 since we began measuring on 18 August 2026

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

Register entry

Telegram ID-1002386664375
TypeChannel
Username@xmpc28
Created13 September 2024measured — dated from the channel’s first post
First recorded18 August 2026
Last confirmed live9 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/xmpc28

Growth

443668555.518 August 2026 — 668 subscribers19 August 2026 — 666 subscribers25 August 2026 — 578 subscribers31 August 2026 — 511 subscribers9 September 2026 — 443 subscribers18 August 20269 September 2026
5 measurements spanning 22 days, net -225. 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 409–702 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 11:55443-68
31 Aug 2026, 20:14511-67
25 Aug 2026, 20:56578-88
19 Aug 2026, 05:54666-2
18 Aug 2026, 11:15668first reading

Engagement

15 posts held, back to 13 September 2024the 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
10.6%
avg views ÷ 443 subscribers
Avg views / post
47.0
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 15 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 17 August 2026
Posts held15 (13 September 202417 August 2026)
Views total47
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Aug 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
13s

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.

Reaction mix

1,907 reactions across 4 posts, in 5 distinct kinds. The most used accounts for 20.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥39620.8%
🎉39220.6%
👍38620.2%
38220.0%
😁35118.4%

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 5 of the 15 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 1,907 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 13 September 2024 to 17 August 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

17 Aug 2026, 09:19 UTC47 viewsread 18 August 2026
Photo

😀😀😀重要通知! 经董事会商议,今日起流水群限红调整为,大小单双6万,组合3万。 😯反向4.6财务:@vip1313 😯反向网盘财务:@xmwpcw 😯超满倍4.74财务:@vip705 😦反向5.0筹备中😯😯😯😯 😦反向2.8筹备中😯😯😯😯

7 Apr 2026, 04:04 UTC392 viewsread 18 August 2026
Photo

❤️反向4.6财务:@vip1313 😯投注机器人:@ximi46_bot ❤️反向网盘财务:@xmwpcw 😯投注机器人: @ximigjwp_bot

30 Dec 2025, 08:08 UTC≈2,490 views1,900 reactionsread 18 August 2026
Photo

全网最大信誉平台❤️❤️❤️❤️,已向😀😀😀😀 @shibo 《公群验证》上押🥰🥰🥰🥰🥰,大额秒下,千万无忧。 ✨我们勤劳耕耘,服务至上,获得业界一众好评与认可!💐💐 🪄应广大群友的要求,洗米国际推出一条龙服务!🍷🍷 🎈🎈在今后的日子里,我们真诚地希望各位代理、各位会员能与我们携手前行,共创辉煌🎆🎆。 洗米国际反向4.6 4.2 👀 洗米国际反向网盘 👀 💡💡💡💡💡💡💡💡💡💡💡 😉😉😉😉😉😉😉 ✈️洗米唯一管理:@vip1314 ✈️洗米4.6财务: @vip1313 ✈️洗米网盘财务:@xmwpcw ✈️洗米官方频道:@xmpc28

🔥396🎉392👍383378😁351

13 Jul 2025, 04:58 UTC≈2,390 viewsread 18 August 2026
Photo

全网最大信誉平台❤️❤️❤️❤️,已向😀😀😀😀 @shibo 《公群验证》上押🥰🥰🥰🥰🥰,大额秒下,千万无忧。 ✨我们勤劳耕耘,服务至上,获得业界一众好评与认可!💐💐 🪄应广大群友的要求,洗米国际推出一条龙服务!🍷🍷 🎈🎈在今后的日子里,我们真诚地希望各位代理、各位会员能与我们携手前行,共创辉煌🎆🎆。 洗米国际反向4.6 4.2 ❤️ 洗米国际反向网盘 ❤️ 💡💡💡💡💡💡💡💡💡💡💡💡 😉😉😉😉😉😉😉 ✈️❤️❤️❤️❤️唯一管理:@vip1314 ✈️❤️❤️❤️❤️4.6财务: @vip1313 ✈️❤️❤️❤️❤️网盘财务:@xmwpcw

18 Nov 2024, 09:46 UTC≈1,310 views5 reactionsread 18 August 2026
Photo

❤‍🔥 洗米😔😔 一打起飞❤‍🔥 ❤‍🔥今晚的风很大,大哥依旧没有倒下❤‍🔥 ❤‍🔥扭转乾坤,输赢就在你的一念之间❤‍🔥 ❤‍🔥乾坤未定,你我皆是黑马❤‍🔥 ❤‍🔥财运滚滚,大哥手气旺旺旺❤‍🔥 🫶欢迎各位老板前来洗米国际爆庄🫶 😉😉😉😉😉😉😉😉 😉😉😉😉😉😉😉😉 🫰洗米4.6唯一财务 :@vip1313 🫰洗米唯一唯一管理:@vip1314 🫰洗米唯一官方频道:@xmpc28 😳洗米反向4.6进群链接

3👍2

30 Sept 2024, 17:19 UTC≈1,220 views1 reactionsread 18 August 2026
Video

❤️❤️❤️❤️🥰🥰🥰🥰🥰🥰🥰🥰 🎆🀄🀄🀄🀄🎆 🥰国庆佳节,心连心,洗米集团向您致以最诚挚的祝福!愿您在这个特殊的日子里,收获满满的幸福与喜悦,事业蒸蒸日上,家庭和和美美。 🥰无论您身处何地,我们都愿与您一同庆祝这充满希望与美好的节日。感谢您一直以来的支持,愿未来的日子充满更多的合作与共赢! 🥰祝您国庆快乐,万事如意!

👍1

16 Sept 2024, 14:46 UTC≈1,200 views1 reactionsread 18 August 2026
Photo

全网最大信誉平台❤️❤️❤️❤️入驻飞机市场,已向😀😀😀😀 @shibo 《公群验证》上押🥰🥰🥰🥰🥰,大额秒下,千万无忧。 ✨我们勤劳耕耘,服务至上,获得业界一众好评与认可!💐💐 🪄应广大群友的要求,洗米国际推出一条龙服务!🍷🍷 🎈🎈在今后的日子里,我们真诚地希望各位代理、各位会员能与我们携手前行,共创辉煌🎆🎆。 洗米国际反向4.6 4.2 ❤️ 洗米国际更多实时玩法关注官方频道 ❤️ 💡💡💡💡💡💡💡💡💡💡💡💡 😉😉😉😉😉😉😉 ✈️❤️❤️❤️❤️唯一管理: @ximigl ❤️ ✈️❤️❤️❤️❤️唯一财务: @ximicw ❤️

1

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

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.

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

“洗米国际官方频道” (@xmpc28), 443 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/xmpc28.

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.