主营项目: 包网 地点:马来西亚(需要到岗马来) 4-5位 岗位:运维工程师 福利待遇: 薪资: 40K 团建餐补 4200 马币 /月 13薪 每周工作6天,休息1天 公寓住2室一厅 2人一间 @javion_1

Channel
远程技术办公岗位
@yuanchengbangong
On this record: Topic · Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
8,135subscribers
+349 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001312553962 |
|---|---|
| Type | Channel |
| Username | @yuanchengbangong |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/yuanchengbangong |
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 12 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 01:01 | 8,135 | +43 |
| 12 Sept 2026, 15:59 | 8,092 | +27 |
| 9 Sept 2026, 01:02 | 8,065 | +57 |
| 3 Sept 2026, 07:38 | 8,008 | +53 |
| 31 Aug 2026, 00:36 | 7,955 | +24 |
| 27 Aug 2026, 15:39 | 7,931 | +14 |
| 25 Aug 2026, 01:08 | 7,917 | +28 |
| 21 Aug 2026, 13:36 | 7,889 | +22 |
| 18 Aug 2026, 19:37 | 7,867 | +26 |
| 16 Aug 2026, 04:24 | 7,841 | +23 |
| 12 Aug 2026, 06:12 | 7,818 | +27 |
| 9 Aug 2026, 11:32 | 7,791 | +5 |
| 9 Aug 2026, 03:45 | 7,786 | first reading |
Engagement
23 posts held, back to 23 April 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 12 pages 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 23 posts for this entry, the most recent from 21 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
马来西亚入职岗位:(优先马来籍) 黑帽seo Marketing Manager(市场营销经理,懂seo) 商务经理 @Scott001122
曼谷居家办公岗位:高级Java/go开发工程师 要求:能够熟练使用 Java 和 Go 两种语言进行项目开发; 有交易所,区块链,钱包,IM项目优先 @javion_1
长期远程 产品经理:不限国籍,无需买设备 熟悉游戏类平台或包网系统的整体架构与业务流程,具备完整项目经验; 具备游戏产品、支付系统或后台管理系统经验,对用户端与运营端需求均有理解;
马来檳城入职岗位:薪资面议(马来籍人选) 市场营销经理 这个职位将主要关注SEO、社交媒体增长、数字营销活动、潜在客户获取和营销绩效优化。
运营负责人( 停招) 📍 工作地点:远程(优先考虑可到马来西亚工作) 💰 薪资范围:3,000–5,000 USD/月 🕒 工作强度:前期每天10小时,月休4 👥 团队规模:管理1名运营专员,协作8人团队 🚀 入职时间:越快越好 项目方向: 负责 AI 成人内容平台的整体运营,涵盖 AI 文字、图片、视频等内容产品,推动平台用户增长、创作者生态建设及商业化发展。 @javion_1
日本东京入职岗位: 要求:本科统招学历(优先在日本有签证) 大小周,年龄要求38以下 公司提供住宿 岗位: 前端开发工程师(薪资 : 30-50k) 岗位: GO开发工程师(薪资 : 30-50k)
📍远程岗位:高级 Java/Go 开发工程师 📌要求: 1. 掌握 Java 与 Go 语言。 2. 具备以下任二项目经验:交易所、区块链钱包、IM、直播视频平台、成人内容。(停招) 短期远程岗位:(今年下半年远程,明年需国外现场办公) Java 架构师 设计主管(中英文能力强) 资深动态设计师(中英文能力强) @javion_1
长期远程岗位:单休,不限制地点(不限国籍) UE开发工程师(无须买设备) • 计算机科学、软件工程、游戏开发、数字媒体或相关专业学历。 • 具备 1–3 年以上 Unreal Engine 开发经验。 • 熟悉 Unreal Engine 4 / Unreal Engine 5 开发流程。 • 具备良好的代码规范及软件开发能力。 • 具备独立分析问题及解决问题能力。 • 良好的团队合作及沟通能力。 UE美术 Unreal Engine 美术技术支持 材质与 Shader 开发 UE 工具开发与流程自动化 @Scott001122
日本入职 高级前端 高级go开发 薪资30 -50 包吃住
马来岗槟城入职岗位: 商务经理(Business Development / Commercial Manager) 工作时间 : 周一到周五, 9am-6pm 能读写中文 年龄不要超过 35 男、女都可以考虑 Igaming 行业优先
胡志明入职岗位: 运营总监 产品运营 渠道与投放管理(有投放经验的优先) 高级运营(活动策划+数据分析方向) 运营经理(需有巴西老虎机运营经验) 项目管理PMO
Showing the 12 most recent of 23 posts we hold for @yuanchengbangong. 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@remote_cn · 25,111
Telegram ranks this channel #4 of 85 here — alongside 84 others — read 15 September 2026
@abetterpathxyz · 33,176
Telegram ranks this channel #20 of 90 here — alongside 89 others — read 4 September 2026
@DeJob_official · 46,726
Telegram ranks this channel #34 of 94 here — alongside 93 others — read 27 August 2026
@bnzhaopingmnl · 142,493
Telegram ranks this channel #44 of 84 here — alongside 83 others — read 15 August 2026
@qzzpfabu888 · 636,574
Telegram ranks this channel #59 of 72 here — alongside 71 others — read 9 August 2026
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“远程技术办公岗位” (@yuanchengbangong), 8,135 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/yuanchengbangong.
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.