Telegram RegisterThe public register of Telegram
Telegram profile photo for 招聘现场岗位

Channel

招聘现场岗位

@xianchang266

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

2,891subscribers

+170 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003279032203
TypeChannel
Username@xianchang266
Created8 November 2025measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live12 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/xianchang266

Topic

Job listings — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 why it has no browse page of its own yet.

Growth

2,7212,8912,8067 August 2026 — 2,721 subscribers8 August 2026 — 2,721 subscribers11 August 2026 — 2,729 subscribers14 August 2026 — 2,743 subscribers18 August 2026 — 2,765 subscribers20 August 2026 — 2,787 subscribers24 August 2026 — 2,814 subscribers28 August 2026 — 2,818 subscribers30 August 2026 — 2,833 subscribers3 September 2026 — 2,851 subscribers8 September 2026 — 2,862 subscribers12 September 2026 — 2,891 subscribers7 August 202612 September 2026
12 measurements spanning 36 days, net +170. 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 2,696–2,917 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 17:572,891+29
8 Sept 2026, 18:562,862+11
3 Sept 2026, 15:392,851+18
30 Aug 2026, 22:362,833+15
28 Aug 2026, 02:452,818+4
24 Aug 2026, 16:162,814+27
20 Aug 2026, 15:262,787+22
18 Aug 2026, 00:512,765+22
14 Aug 2026, 21:282,743+14
11 Aug 2026, 07:152,729+8
8 Aug 2026, 12:332,721no change
7 Aug 2026, 18:332,721first reading

Engagement

9 posts held, back to 8 November 2025the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 9 posts for this entry, the most recent from 20 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

24 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 95.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2395.8%
🔥14.17%

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 8 of the 9 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 24 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

20 Jun 2026, 14:52 UTC≈2,770 views4 reactionsread 7 August 2026
Forwarded from @yuancheng266

招聘行政人员🌹🌹🌹 ✅岗 位:行政 2名 ✅办公地点:亚美尼亚,正规企业大楼、工签、交医社保 🇺🇳国 籍:马来西亚🇲🇾、印尼🇮🇩 、越南🇻🇳、缅甸🇲🇲、老挝🇱🇦、台湾🇹🇼 💼工作内容: ✅根据上级安排完成行政相关工作任务 💰薪资待遇 ✅试用期:2200美 ✅转正后:2800-3000美💥 ✅工作每满一年+130美 ✅公平公正晋升机会 ⏰工作时间 ✅长白班09:00-19:00(本地时间) ✅休息:月休2天 ✅假期:半年带薪15天 💁基本要求: ✅性别年龄:男女均可,20岁以上 ✅流利的中、英文表达能力,熟练的沟通技巧 ✅责任心强、执行力高 ✅熟练使用Excel、Word ✅工作经验:有无经验均可,有行政工作经验者优先 ⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️ 🥳福利🥳 ✅满勤奖 ✅生日津贴 ✅餐补、房补 ✅年终奖13薪 ✅半年带薪15天,不休可补贴 ✅春节、中秋节、 端午节 、元旦节红包

4

20 Jun 2026, 14:52 UTC≈2,800 views2 reactionsread 7 August 2026
Forwarded from @yuancheng266

📤 行政专员 男女不限 💻工作地点:菲律宾,索莱尔 💰薪资待遇 1500-1700 USD 起 具丰富经验者薪资可面议 能力优秀者待遇从优 工作时间 10休2 10-20点 北京时间 ✍️ 岗位要求 ✅ 中文、英文流利(听说读写) ✅ 具行政、人事或相关工作经验优先 ✅ 熟练使用 Office / WPS 办公软件 ✅ 责任心强,沟通协调能力佳 ✅ 能独立处理日常行政事务 🎁福利待遇 ✅ 提供住宿 ✅ 办理工作签证 ✅ 医疗补助 ✅ 带薪年假 ✅ 节日福利 ✅ 良好晋升发展空间 联系 @fengge90 看更多岗位在频道 yuancheng266 xianchang266

2

9 Jun 2026, 16:36 UTC≈2,750 views6 reactionsread 7 August 2026
Forwarded from @yuancheng266Photo

【财务专员】 Financial Specialist 待遇: • 工作时段 - 依照排班 - 12 H • 地点 - 菲律宾 • 月休- 2 日 • 试用期- 30 日 • 底薪 - 10000-16000 RMB 小白 • 底薪 - 12000-17000 RMB 有经验 • 生活补助 - 400 RMB / 月 • 生日补贴:260 RMB • 绩效奖金 - 0~3000 RMB • 满 6 个月未回国奖金 - 3000~6000 RMB • 公司包吃住 有13薪 工作要求: ⚡️国籍不限,中文听、说、读、写 熟练 ⚡️熟练使用 Word / Excel ⚡️学习能力强,理解能力好 ⚡️对数字敏感、逻辑思维能力强者 优先 工作职责: ✨监控支付通道 ✨下发、审核款项 ✨支付相关费用 ✨制作及维护财务报表 ✨跨部门沟通与协调 联系

5🔥1

8 Jun 2026, 01:48 UTC≈2,930 views5 reactionsread 7 August 2026
Photo

招聘 行政 需要会中英 会开车 工资 第一年 15.000RMB 到 21.000RMB 工作地点: 亚美尼亚 工作时间:11:00-23:00北京时间(特殊情况该加班要服从安排) 联系 @fengge90 看更多岗位在频道 yuancheng266 xianchang266

5

19 May 2026, 02:55 UTC≈3,900 views5 reactionsread 7 August 2026

🌍 海外招聘|后台专员(数位) 📍 办公地点 🇦🇲 Yerevan(亚美尼亚首都 · 埃里温) 🇱🇰 Colombo(斯里兰卡首都 · 科伦坡) 💼 岗位职责 ⚡️负责查看通道及订单数据 ⚡️切换第三方通道 ⚡️审核客户提现订单 ⚡️跟进出款订单回调情况 ⚡️查询处理中及未回调订单状态 ⚡️协助客服处理客户存取款反馈问题 ⚡️制作及整理数据报表 💰 薪资待遇 (中文听说读写流利) 💦试用期:1700U(1–3个月) 💦转正后:每月递增 +70U 💦第一年度最高可达:2100U封顶 ✨ 若英文听说读写流利,面试后可根据能力议定更高薪资 (英文听说读写 — 有限水平 / 雅思4分) 💦试用期:1800U(1–3个月) 💦转正后:每月固定递增 70U 💦第一年度薪资封顶:2200U 入职满第二年:可根据个人绩效表现向部门申请调薪评估 🕒 工作时间 12小时制 月休 2 天 两班倒 🏠 生活保障 🍽 食堂 埃里温:一天五餐

5

22 Apr 2026, 12:06 UTC≈3,500 views0 reactionsread 7 August 2026
Forwarded from @yuancheng266

行政 在日本工作 不要中国/台湾-越南藉优先 • 工作时段 -12pm-10pm • 地点 - 日本/大阪 • 上班时间 - 10小時 月休6-8天 • 试用期 - 30天 • 薪资 -15000-2000RMB(具体面议) • 转正+绩效 • 生活补贴 - 宿舍/機票補貼 工作要求: ✨良好的中日文写作、口语、阅读能力 ✨熟练使用办公软件及办公自动化设备 ✨熟练Excel软件 ✨做事细心 耐心 有责任 有耐心 有韧劲 ✨1年以上行政工作经验尤佳 ✨内能认真执行上级指示 ✨目标清晰,抗压能力强,具备较强的执行力和沟通协调能力 联系 @fengge90

15 Mar 2026, 14:30 UTC≈6,350 views0 reactionsread 7 August 2026
Photo

招聘 行政 需要会中英 会开车 工资 第一年 15.000RMB 到 21.000RMB 工作地点: 亚美尼亚 ,菲律宾 工作时间:11:00-23:00北京时间(特殊情况该加班要服从安排) 联系 @fengge90 看更多岗位在频道 yuancheng266 xianchang266

10 Mar 2026, 04:13 UTC≈2,210 views2 reactionsread 7 August 2026
Forwarded from @yuancheng266

🙁😨 助理专员【1位女性】 🥳薪资待遇: 试用期:12000元~18000元+补贴 🥳工作时间: 10休2 🥳工作地点: 菲律宾🇵🇭 🚽岗位要求: 性别:女性 年龄:18-29岁以内 国籍:越南🇻🇳 语言要求:中-英文流利 1, 具备基础办公软件使用能力, 熟练使用excel; 2, 对数字敏感, 助理工作经验者为佳; 3, 态度亲和, 有耐心, 思维缜密, 保密意识强。 🚽岗位职责: 1, 负责各项先进的登记, 核对; 2, 日记账处理, 报表及科目明细表; 3, 完成领导交办的其他工作。 联系 @fengge90 看更多岗位在频道 yuancheng266 xianchang266 anna

2

Showing the 9 most recent of 9 posts we hold for @xianchang266. 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“招聘现场岗位” (@xianchang266), 2,891 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/xianchang266.

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.