Telegram RegisterThe public register of Telegram
Telegram profile photo for 体育直招

Channel

体育直招

@wanmeiitiyu

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

82subscribers

-4 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003940354669
TypeChannel
Username@wanmeiitiyu
CreatedBetween 1 April 2026 and 27 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live29 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/wanmeiitiyu

Growth

8286847 August 2026 — 86 subscribers9 August 2026 — 86 subscribers15 August 2026 — 83 subscribers29 August 2026 — 82 subscribers7 August 202629 August 2026
4 measurements spanning 22 days, net -4. 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 81–87 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 08:4282-1
15 Aug 2026, 00:4683-3
9 Aug 2026, 16:3386no change
7 Aug 2026, 09:0186first reading

Engagement

20 posts held, back to 27 June 2026the 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
22.0%
avg views ÷ 82 subscribers
Avg views / post
18.0
2 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
3
of 20 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 9 August 2026
Posts held20 (27 June 20269 August 2026)
Views total36
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 16:33 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
39s
Average length
10s

Measured directly from 4 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

3 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3100.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 20 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 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 27 June 2026 to 9 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

9 Aug 2026, 14:58 UTC9 viewsread 9 August 2026

柬埔寨要一维护需要有经验,男女不限底薪12k,32岁以内,不要外籍,福建籍

9 Aug 2026, 04:15 UTC27 viewsread 9 August 2026

FKZJB GW: 风控质检专员 10名 GZDD:SLK XZDY:10-12+绩效 GZSJ:9小时(月休4) 9-18 14-23 XB:不限 NL:35岁以下 XL:不限 GJ:不限,缅甸,福建/山东/河南敏感地区不要 YYXQ:中文流利 *不要小白 GWXQ: 1.福建/山东/河南敏感地区不要 2.熟悉办公软件,会基本函数 3.思维逻辑清晰,抗压能力强 4.只要有FK/ZJ经验,不要小白 GWZZ: 1.对fk作业进行抽检,查错纠错 2.通过大数据分析,及时发现问题并预警 3.较强的学习执行能力,能举一反三

4 Aug 2026, 09:55 UTC114 viewsread 9 August 2026

薪资(人民币):底薪12-13k + kpi 0-2k 10小时,月休4 ,无夜班 工作地点:西港 国籍:中国 性别:男 年龄:28岁以下 人数:3人 岗位要求: 接受无经验小白,但要对计算机编程代码感兴趣,愿意学习钻研,(学历必须要大专以上,需要学信网查看毕业证书) 岗位职责: 1、利用python,sql等数据工具拉取和处理数据,处理日常和临时数据需求 2、参与团队图表可视化开发,设计可视化图表模板 3、完成上级领导交代的其他工作任务 数据专员 官资要的

30 Jul 2026, 10:05 UTC228 viewsread 9 August 2026

格鲁需求: 家庭保姆,要求菲律宾或者越南籍,英语熟练,主要工作就是打扫家里卫生,整理家庭环境,偶尔帮忙照顾下小孩子。要求女性,最好是有带做过家庭保姆的经验。汉语没有要求,只要求英语和家庭保姆工作经验。 @ww6125

28 Jul 2026, 12:42 UTC272 viewsread 9 August 2026

内账专员招聘 一、岗位职责 负责审核各项请款及报销,重点核查需求合理性、采购真实性、物品一致性、报销合规性、票据完整性及款项可追溯性; 负责公司日常收支账、应收账及核销账的登记与管理; 根据资产台账,每月组织资产盘点,确保账实一致; 月末编制柬埔寨财务月报,以及部门、科目汇总报表; 定期核对账面明细及账户余额,包括U钱包、现金等。 二、任职要求 国籍:中国籍 性别:女性 具备内账相关工作经验; 熟练使用Excel及常用函数; 工作细致严谨,责任心强,具备良好的数据核对能力。 三、薪资待遇 工作班次:每日10小时,12:00—22:00。 试用期: 薪资:12000+全勤奖; 休假:月休2天。 转正后: 薪资:15000+全勤奖+KPI绩效奖金; KPI绩效奖金:0—2000; 休假:月休4天。 四、员工福利 团建补贴、医疗补贴、节日礼金及过节红包。

27 Jul 2026, 06:30 UTC245 views1 reactionsread 9 August 2026

2026.7.27 西港 招聘岗位 : 😞😞😞😞😞😞😞😞 🇷🇪人资专员 🇷🇪薪酬专员 🇷🇪审计专员 🇷🇪财务专员 🇷🇪后勤专员 🇷🇪网管专员 🇷🇪红利组长 🇷🇪运营专员 TG4 🇷🇪推广专员 🇷🇪维护专员 TG6 🇷🇪推广专员 🇷🇪主播专员 🇷🇪SEO专员 🇷🇪维护专员 YXTG 🇷🇪维护专员 🇷🇪推广助理 HOME 🇷🇪推广专员 YBTG 🇷🇪推广专员 🇷🇪维护专员 WMTG13B 🇷🇪推广专员 🇷🇪维护专员 WMTG11B 🇷🇪推广专员 ZS2B 🇷🇪代理发展专员 🇷🇪代理发展组长

1

27 Jul 2026, 06:09 UTC229 viewsread 9 August 2026

要2个维护 薪资固定10k 要中国籍 8小时 三班倒 职责:类似于客服 送送彩金,回复一下会员消息 要求:懂电子 备注:不忙可以休息,商量着来 @ww6125

23 Jul 2026, 12:23 UTC287 views2 reactionsread 9 August 2026

7月份西港招聘需求 客服 风控 推广 推广维护 电销 主播 人资 越南国籍 第三方专员 seo专员 运营专员 招商专员 招商组长 审计 财务专员 外籍 🔜🔜🔜🔜🔜🔜🔜🔜🔜🔜🔜🔜🔜 柬埔寨西港 随时欢迎上门谈 🤥7年资质 终秉承无隐形赔付无负面新闻,不坑不骗,赔付透明,欢迎咨询了解, 😘招聘频道:@ww6125 ✅招聘联系人:招聘频道:https://t.me/wanmeiitiyu

2

23 Jul 2026, 10:33 UTC247 viewsread 9 August 2026
Photo

西港的后勤,还要一个 中国籍 可以投男生,30以下有经验优先

14 Jul 2026, 05:50 UTC390 viewsread 9 August 2026
Photo

资部招聘2位人资专员,做薪酬账目,签证信息管理等 这边缺人,尽快招聘,最好是越南人,会中文

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

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

“体育直招” (@wanmeiitiyu), 82 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/wanmeiitiyu.

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.