Channel
@wanmei6899
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
413subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002218918235 |
|---|---|
| Type | Channel |
| Username | @wanmei6899 |
| Description | WM集团直招 -要大量推广 招商 客服 -西港🇰🇭格鲁吉亚🇬🇪 -非园区 -不禁足-靠谱的人事@xiaoshu0109 |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/wanmei6899 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 05:34 | 413 | no change |
| 7 Aug 2026, 10:32 | 413 | first reading |
19 posts held, back to 13 June 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 pageof 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. It is computed over the 1 of 6 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 4 August 2026 |
|---|---|
| Posts held | 19 (13 June 2026 – 4 August 2026) |
| Views total | 1,555 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 05:34 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.
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 3 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
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 3 of the 19 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 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 13 June 2026 to 4 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.
岗位：数据专员 薪资(人民币)：底薪12-13k + kpi 0-2k 10小时，月休4 ，无夜班 工作地点：西港 年龄：28岁以下 国籍：中国 人数：3人 岗位要求： 愿意学习一些简单的编程，有学习能力，以及愿意钻研的小白，需要大专以上，需要学信网查看毕业证书 岗位职责： 1、利用python，sql等数据工具拉取和处理数据，处理日常和临时数据需求 2、参与团队图表可视化开发，设计可视化图表模板 3、完成上级领导交代的其他工作任务
🇲🇱🇲🇱🇲🇱内账专员 一、岗位职责 负责审核各项请款及报销，重点核查需求合理性、采购真实性、物品一致性、报销合规性、票据完整性及款项可追溯性； 负责公司日常收支账、应收账及核销账的登记与管理； 根据资产台账，每月组织资产盘点，确保账实一致； 月末编制柬埔寨财务月报，以及部门、科目汇总报表； 定期核对账面明细及账户余额，包括U钱包、现金等。 二、任职要求 国籍：中国籍 性别：女性 具备内账相关工作经验； 熟练使用Excel及常用函数； 工作细致严谨，责任心强，具备良好的数据核对能力。 三、薪资待遇 工作班次：每日10小时，12:00—22:00。 试用期： 薪资：12000＋全勤奖； 休假：月休2天。 转正后： 薪资：15000＋全勤奖＋KPI绩效奖金； KPI绩效奖金：0—2000； 休假：月休4天。 四、员工福利 团建补贴、医疗补贴、节日礼金及过节红包。 🙂西港-非园区-不禁足 @xiaoshu0109
❤1
🇲🇱🇲🇱🇲🇱部要2个维护，职责类似于客服 送送彩金，回复一下会员消息 8小时 两班倒，要求懂电子，中国籍 薪资固定10k 🗺西港-非园区-不禁足
🇲🇱人资专员 国籍：越南🇻🇳 性别：不限 年龄 ：32岁以下 地址：西港🇰🇭 工资💰：10k转12k +绩效 工作时间 ：9小时，试用期2个月 试用期月休2 转正月休4 1 、熟练电脑的文档操作 2 、中文流利， 工作积极细心 有上进心 愿意学习 3 、备主动服务理念， 服从安排 4、优选有相关工作经历者 🙂西港🇰🇭-非园区-不禁足 离海边很近天天能看到海🌊🌊🌊
IT 主任 国籍：非中國籍 地址：菲律宾🇵🇭-馬尼拉 工资💰：2500起 工作时间：9小時 6-7天(大小月) +菲假 😂IT策略與規劃 🔥制定並執行公司IT中長期策略與年度計畫。 🔥評估新技術（如雲端、資安、數據分析、AI）導入可行性。 😂系統與基礎架構管理 🔥負責公司內部系統（ERP、CRM、HR、Email、Network等）之建置、維運與優化。 🔥管理伺服器、網路、雲端環境與備援機制。 😂資訊安全與風險管理 🔥建立並落實資訊安全政策、資安事件應變流程。 🔥確保資料備份、權限控管與法規遵循（如ISO 27001、個資法）。 😂專案管理 🔥規劃與執行IT相關專案，控管進度、成本與品質。 🔥跨部門溝通協調，確保專案符合業務需求。 😂團隊管理 🔥領導與培育IT團隊（工程師、系統管理員、外包廠商）。 🔥人力規劃、績效管理與技術培訓。 😂供應商與預算管理 🔥評估與管理IT供應商、外包與合約。 🔥編列與控管IT預算，提升投資效益。 …
🇲🇱🇯🇵🇬🇺 岗位 🇲🇪：第三方 出入款 😁要大量 性别🇲🇪 ：不限 国籍 🇲🇪： 越南🇻🇳 +中国🇨🇳 语言🇲🇪：中文流利 薪资🇲🇪 ： 中国 10k-12k +kpi ： 越南 9k-11k+kpi 工作时间😇 ：9小时休息4 试用期 休2 三班倒 工作🙂 ：西港🇰🇭/非园区/不禁足 😜😜😜😜😜😜😜😜😜😜😜 ✅@xiaoshu0109
要一个运营专员 10-12k+绩效 9小时休4 需要有这行业经验 🎯入职西港
HR SHUSHU-体育盘-西港直招-不禁足 pinned «🔠🔠🧐😋2️⃣0️⃣2️⃣6️⃣ 😟🤓😊😊😊 🥰年底13薪，半年假（可带薪休15天不休息奖励5000RMB） 节日礼金：生日礼金及礼品👑 🥰吃：免费提供营养美味的餐食（10菜2汤+水果）👑 🥰住：酒店式房间 2人间，提供情侣房，免费保姆打扫卫生，入职免费发放生活用品 👑 🥰行：24小时定点班车接送上下班，保证员工的出行安全👑 🥰免费福利：定期部门团建，年度员工旅游，晋升机制，培训考核👑 🥰其他福利：部门奖金、贡献奖，全勤奖👑 🥰合法保障：公司带有合法正规牌照，员工依法缴纳当地税金👑»
🇲🇱格鲁需要发语音的女生，只要台湾的，中国敢发语音的也可以女生 12000加kpi 1000-5000 12小时月休4 🙂格鲁吉亚🇬🇪
要推广小组维护、推广开发 小组日活2000 资源好 维护平均工资每月也可以拿四五万 世界杯想赚钱的来 🙂西港
🇲🇱SEO专员 国籍：不限 性别：不限 地址：西港🇰🇭 薪资2万起步+点位，可面议 有bc经验，懂单站或者泛站运营，工作经验2年以上
男生 年轻点会表格或者有助理经验也行
Showing the 12 most recent of 19 posts we hold for @wanmei6899. 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 — 899,116 of 1,478,351entries 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.
Named by 2 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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“HR SHUSHU-体育盘-西港直招-不禁足” (@wanmei6899), 413 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/wanmei6899.
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.