📢8月最新远程岗位来咯!🎁 岗位越来越少了!!!速速投递咯~ 🤍商务主管 🤍游戏客户端开发工程师 🤍高级项目经理 🤍产品经理 🤍运营主管 🤍运营组长 🤍德州风控组长 🤍德州风控专员 🤍德州运营专员 🤍平台运营专员 🤍活动运营专员 🤍数据专员 🤍真人风控 🎁日本岗位 🤍日本行政 🤚其他岗位 🤍总监助理 投递简历联系 ✈️ @hrjobfind
❤6🎉1👍1🙏1

Channel
@itremote88
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,232subscribers
+8 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002412984045 |
|---|---|
| Type | Channel |
| Username | @itremote88 |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/itremote88 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 19:16 | 2,232 | +7 |
| 7 Aug 2026, 15:56 | 2,225 | +1 |
| 7 Aug 2026, 09:46 | 2,224 | first reading |
20 posts held, back to 26 May 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 2 pagesof 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.
| Window | Rolling 30 days · latest post in window 4 August 2026 |
|---|---|
| Posts held | 20 (26 May 2026 – 4 August 2026) |
| Views total | 6,420 |
| Reactions total | 60 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 16:49 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.
197 reactions across 18 posts, in 13 distinct kinds. The most used accounts for 53.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 105 | 53.3% | |
| 👍 | 43 | 21.8% | |
| 🔥 | 14 | 7.11% | |
| 👌 | 11 | 5.58% | |
| 👏 | 7 | 3.55% | |
| 💯 | 6 | 3.05% | |
| 😱 | 3 | 1.52% | |
| 🎉 | 2 | 1.02% | |
| 👀 | 2 | 1.02% | |
| 🏆 | 1 | 0.508% | |
| 👨💻 | 1 | 0.508% | |
| 🙏 | 1 | 0.508% | |
| 🥰 | 1 | 0.508% |
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 18 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 197reactions 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 26 May 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.
📢8月最新远程岗位来咯!🎁 岗位越来越少了!!!速速投递咯~ 🤍商务主管 🤍游戏客户端开发工程师 🤍高级项目经理 🤍产品经理 🤍运营主管 🤍运营组长 🤍德州风控组长 🤍德州风控专员 🤍德州运营专员 🤍平台运营专员 🤍活动运营专员 🤍数据专员 🤍真人风控 🎁日本岗位 🤍日本行政 🤚其他岗位 🤍总监助理 投递简历联系 ✈️ @hrjobfind
❤6🎉1👍1🙏1
📢远程 真人资深风控专员 招聘人数: 2人 薪酬范围 :面谈 办公模式 :远程 上班时间 :9小时含一小时休息(三班倒) 休息天数 :月休4 国藉要求 :不限 特别要求 :真人风控专项经验2年以上 岗位职责: 1、日常风控项巡检、处理、汇报,包括套利、盈利率异常、机打等,并识别新的潜在风控风险项 2、熟悉审核原则,对提案、优惠、佣金以及其他各类财务项进行审核 3、根据客服、代理或会员等反馈的异常问题,核查特定风控问题并记录与分析 4、风控业务审核流程的优化与完善 职位要求: 1、从事BC风控岗2年以上,了解BC行业常态化存在的风险漏洞,对体育风控与德州扑克最起码精通一种。 2、对数据敏感,对接入的各类游戏的玩法、赔率以及潜在风险等有了解,且善于分析总结。 3、对代理行为,游戏用户行为有独到的见解,可以判断各类行为是否合理,是否存在风险 4、熟悉综合风控审核流程,有风控业务规划能力者优先 5、勤奋严谨,思路清晰,数据敏感,善于…
❤9👍2🔥1
📢新增岗位 菲律宾🇵🇭居家 出入款专员(限外籍) 简历投递 ✈️ @hrjobfind
❤6🔥3👏2
📢最新远程岗位来咯!🎁 岗位越来越少了!!!速速投递咯~ 🤍商务主管 🤍游戏客户端开发工程师 🤍高级项目经理 🤍产品经理 🤍运营主管 🤍运营组长 🤍德州风控组长 🤍德州风控专员 🤍德州运营专员 🤍平台运营专员 🤍活动运营专员 🤍数据专员 🤍真人风控 ❤️菲律宾现场如下 🤍出入款专员 🤍会计专员 🎁日本岗位 🤍日本行政 🤚其他岗位 🤍总监助理 投递简历联系 ✈️ @sushi618
❤11👍3👌2
有人冒充我的身份‼️ 使用类似的用户名而且还挂了我的频道😅 求职认准这个号哦 ✈️ @sushi618
👌5😱3👀2❤1💯1
📢远程 AI工程师 ⭐岗位职责: 1. 负责 AI 应用、智能体、自动化工具或大模型相关系统的设计、开发和优化。 2. 参与大模型 API、开源模型、RAG、Agent、工作流自动化等能力的接入与落地。 3. 根据业务需求完成 AI 功能模块开发,包括提示词工程、模型调用、数据处理、接口封装等。 4. 负责 AI 项目的工程化实现,包括后端服务、任务调度、模型推理、数据存储与系统监控。 5. 参与模型效果评估、性能优化、成本优化和稳定性改进。 6. 跟进 AI 领域新技术,并结合业务场景提出可落地的产品或技术方案。 7. 编写技术文档,沉淀开发规范、接口说明和项目经验。 ⭐岗位要求: 1. 本科及以上学历,计算机、人工智能、软件工程、自动化、数学等相关专业优先。 2. 熟悉 Python,具备扎实的后端开发能力,能独立完成服务端功能开发。 3. 熟悉至少一种主流后端框架,如 FastAPI、Django、Flask、Node…
❤10👍4👌3👏2🔥1
📢远程岗位 岗位:HR会计 国籍:外籍 需求:1位 岗位职责 1. 负责各部门费用的核对、审核及统计,确保数据准确无误。 2. 跟进费用报销、付款及相关单据的整理、归档。 3. 对费用数据进行分析,发现异常并及时反馈、跟进处理。 4. 与HR、财务及各业务部门保持沟通,确保费用核算流程顺畅。 5. 协助完成月度、季度及年度费用报表及相关财务支持工作。 6. 完成上级交办的其他财务相关工作。 任职要求 1. 本科及以上学历,会计、财务管理、审计等相关专业优先。 2.具有会计或财务相关工作经验,有费用审核、费用核对经验者优先。 3. 对数字敏感,逻辑清晰,具备较强的数据分析和核对能力。 4.工作认真细致,责任心强,能够独立完成费用核对工作。 5.熟练使用Excel等办公软件,能够进行常用函数、数据透视等操作者优先。 6.具备良好的沟通协调能力和团队合作意识。 简历投递 ✈️ @sushi618
❤11🔥4👍3
远程技术招聘频道 pinned a photo
📢远程 商务主管 工作地点:不限(偶尔出差海外) 岗位名称: 2B 商务主管 / B 端商务拓展主管 B2B Business Development Manager 🤚岗位职责: 1. 负责公司 B 端业务的商务拓展工作,围绕企业客户、渠道伙伴、行业资源等建立合作关系,推动业务增长。 2. 根据公司产品和业务方向,制定 B 端客户拓展策略,挖掘潜在客户,建立并维护客户资源池。 3. 独立完成客户开发、需求沟通、方案推进、商务谈判、合同签署及项目落地等完整商务闭环。 4. 深入理解客户业务场景和痛点,协同产品、运营、技术等团队,为客户提供有针对性的解决方案。 5. 负责重点客户关系维护,提升客户满意度、合作深度和复购机会,持续挖掘客户增长空间。 6. 拓展并维护行业合作伙伴、渠道资源及生态资源,推动联合推广、资源互换、项目合作等落地。 7. 关注行业动态、竞品情况和客户需求变化,定期输出市场反馈、客户洞察和业务建议。 8.…
❤6👍4🔥3👏1
📢最新远程岗位来咯!🎁 🤍AI工程师 🤍商务主管 🤍游戏客户端开发工程师 🤍高级项目经理 🤍产品经理 🤍运营主管 🤍运营组长 🤍德州风控组长 🤍德州风控专员 🤍德州运营专员 🤍平台运营专员 🤍活动运营专员 🤍数据专员 🤍HR会计专员 ❤️菲律宾现场如下 🤍出入款专员 🤍会计专员 🎁日本岗位 🤍日本行政 🤚其他岗位 🤍总监助理 🤍家庭助理 投递简历联系 ✈️ @sushi618
❤7👍3👏2🔥2🏆1💯1
📢招 家庭助理 基本要求: 1.会中文+英文,可以无障碍交流。 2.性格稳定,诚实可靠,有责任心 3.可长期工作,能住家 4.服从上级领导的安排 5.只考虑中籍以外的人选。 工作内容: 1.日常家庭事务管理; 2.安排、管理好保姆工作; 3.采购管理生活用品 4.协助接待客人/外卖/快递 5.以及其他家庭相关辅助工作 工作地点:菲律宾 工作待遇: 住家(提供房间) 包住+每月生活补贴 薪资面议(根据经验) 每月休息2天 男女不限 投递简历 ✈️ @sushi618
👍4
紧急‼️招聘 项目经理 ✈️ @sushi618
❤2
Showing the 12 most recent of 20 posts we hold for @itremote88. 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 — 11,011 of 1,151,006entries 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 6 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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“远程技术招聘频道” (@itremote88), 2,232 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/itremote88.
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.