Telegram RegisterThe public register of Telegram
Telegram profile photo for 🔥多个国家月休8天工作交流(每周更新)

Channel

🔥多个国家月休8天工作交流(每周更新)

@shuangxiugognzuo

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Telegram's recommendations · Cite this entry

7,049subscribers

+561 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-1001686889569
TypeChannel
Username@shuangxiugognzuo
Description香港--日本--迪拜--越南--格鲁吉亚--马来西亚--菲律宾—招募多个岗位,总有一个合适你的 Telegram:@sunny9488 @sunny52033 whatsapp:927 834 8469 蝙蝠:158493316 微信:sunny_2926feng QQ:2547462394 LLark/飞书/:[email protected] 🤖:@sunny9452089bot(双向请联系)
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live13 November 2026
Measurements held26
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/shuangxiugognzuo

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 67% 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 the other topics.

Growth

6,4887,0496,768.59 August 2026 — 6,488 subscribers9 August 2026 — 6,488 subscribers13 August 2026 — 6,513 subscribers16 August 2026 — 6,532 subscribers20 August 2026 — 6,566 subscribers24 August 2026 — 6,589 subscribers26 August 2026 — 6,610 subscribers29 August 2026 — 6,625 subscribers1 September 2026 — 6,631 subscribers4 September 2026 — 6,647 subscribers9 September 2026 — 6,642 subscribers13 September 2026 — 6,646 subscribers17 September 2026 — 6,687 subscribers27 September 2026 — 6,732 subscribers5 October 2026 — 6,791 subscribers12 October 2026 — 6,839 subscribers15 October 2026 — 6,871 subscribers18 October 2026 — 6,889 subscribers22 October 2026 — 6,924 subscribers24 October 2026 — 6,947 subscribers28 October 2026 — 6,950 subscribers31 October 2026 — 6,977 subscribers3 November 2026 — 6,994 subscribers6 November 2026 — 7,007 subscribers9 November 2026 — 7,029 subscribers13 November 2026 — 7,049 subscribers9 August 202613 November 2026
26 measurements spanning 96 days, net +561. 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 6,404–7,133 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
13 Nov 2026, 12:557,049+20
9 Nov 2026, 01:387,029+22
6 Nov 2026, 03:017,007+13
3 Nov 2026, 02:076,994+17
31 Oct 2026, 11:016,977+27
28 Oct 2026, 04:306,950+3
24 Oct 2026, 23:566,947+23
22 Oct 2026, 02:276,924+35
18 Oct 2026, 10:316,889+18
15 Oct 2026, 18:416,871+32
12 Oct 2026, 12:096,839+48
5 Oct 2026, 08:186,791+59
27 Sept 2026, 09:566,732+45
17 Sept 2026, 20:406,687+41
13 Sept 2026, 11:006,646+4
9 Sept 2026, 12:016,642-5
4 Sept 2026, 04:176,647+16
1 Sept 2026, 04:156,631+6
29 Aug 2026, 08:256,625+15
26 Aug 2026, 17:396,610first reading

Engagement

80 posts held, back to 29 July 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 29 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
15.6%
avg views ÷ 7,049 subscribers
Avg views / post
1,100
53 posts measured
Reaction rate
0.089%
reactions ÷ views · ER floor
Posts in window
53
of 80 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. It is computed over the 20 of 53 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 November 2026
Posts held80 (29 July 2026 – 16 November 2026)
Views total58,217
Reactions total20
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 02:55 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

Photos
7
Links
8

Lifetime counters from Telegram’s own channel header, read 18 November 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.

Reaction mix

46 reactions across 24 posts, in 4 distinct kinds. The most used accounts for 82.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3882.6%
🤣510.9%
🤬24.35%
🔥12.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 36 of the 80 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 46 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 80 most recent posts we hold, published 29 July 2026 to 16 November 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

Telegram’s own ‘edited’ marker: 16 of 53 posts held from the last 30 days (30.2%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

16 Nov 2026, 03:53 UTC≈1,020 views1 reactionsread 18 November 2026

产品经理 工作地点:居家远程—需要人在海外,不可以在中国大陆 工作时间 9小时每周休一天 薪资范围 20-25K / 月,根据能力与经验面议 行业类型:Igaming 职位介绍 我们正在寻找一位兼具产品思维与客户成功意识的产品经理,负责 iGaming SaaS 平台从产品交付、需求管理到持续迭代优化的全生命周期。 你将深入理解客户业务场景,推动产品落地,与研发、运营、客服等团队协作,不断提升平台能力与客户体验。 岗位职责 产品规划与需求管理 • 收集客户反馈、业务需求及市场信息,输出产品需求文档(PRD)。 • 梳理业务流程,分析痛点,持续推动产品优化与功能迭代。 • 将业务需求拆解为可执行方案,与研发团队沟通并推进落地。 • 跟踪产品版本开发进度,协调测试、验收及上线。 产品交付与客户成功 • 负责 SaaS 平台客户开站、配置、上线及交付流程。 • 协助客户快速完成产品接入,提高产品使用效率。 • 持续跟踪客户使用…

❤1

16 Nov 2026, 03:52 UTC822 views1 reactionsread 18 November 2026

Cocos 游戏工程师 工作地点:居家远程—需要人在海外,不可以在中国大陆 工作时间 9小时每周休一天 薪资范围 25K – 45K / 月,根据能力与经验面议 行业类型:Igaming 工作内容 • 开发与维护游戏:使用 Cocos Creator 制作 H5 游戏,确保程序稳定、易于维护且具备扩展性。 • 设计 UI 与游戏机制:负责游戏流程、操作逻辑与界面实现,提升玩家体验。 • 对接后端数据:通过 API 与 WebSocket 与服务器交互,处理数据交换与逻辑控制。 • 优化游戏架构:熟悉现有框架,持续优化架构与性能,提升开发效率。 • 产品运维:维护已上线的游戏,处理稳定性与性能优化问题。 应聘条件 • 目前人在海外(可远程工作); • 熟练 JavaScript(ES6)与 TypeScript,具备良好的程序架构能力; • 具备 Cocos Creator 游戏开发经验,且至少有一款已上线的游戏作品; …

❤1

16 Nov 2026, 03:51 UTC756 viewsread 18 November 2026

Go 后端开发工程师 工作地点:居家远程—需要人在海外,不可以在中国大陆 工作时间 9小时每周休一天 薪资范围 25K – 45K / 月,根据能力与经验面议 行业类型:Igaming 岗位职责 • 负责后端系统的架构设计、业务功能开发和优化,确保系统的高性能和稳定性; • 参与业务需求讨论,设计合理的技术方案,高质量开发,确保功能按时上线; • 负责数据存储、缓存系统(如 MySQL / PostgreSQL、Redis 等)的设计与优化; • 解决高并发、高吞吐下的性能瓶颈,优化 API 调用、数据库查询和缓存策略; • 撰写技术文档,完善代码测试,提高代码可读性和稳定性。 任职要求 1. 编程经验 • 熟练使用 Go,熟悉 Linux,熟悉 Gin、gRPC、go-zero 或其他主流框架; • 具备良好的代码规范和高并发编程经验,掌握 Goroutine、Channel 及性能优化方法; • 熟悉微服务架构,具…

16 Nov 2026, 01:01 UTC801 viewsread 18 November 2026

❤️🇵🇭菲律宾职位:维护开发、高阶渗透工程师、黑帽SEO渗透、市场总监、体育直播流量负责人、财务分析师、彩票平台负责人、财务经理、网络安全与流量优化工程师、体育直播项目负责人、直播运营组长、 UI设计师、项目管理、首席营销官、平台运营专家、用户增长负责人、前端产品经理、游戏产品经理、策略运营总监-PDD专项、平台运营算法负责人、行政运营协调、厂商合作运营、首席运营业务助理、整合营销负责人、内容运营专员/专家、活动运营、策略运营、用户运营、资深游戏商务、用户体验专家/专员、PMO项目管理、游戏平台测试工程师、应用开发工程师、 IT服务台工程师、K8S运维工程师、CRM客户关系管理、赌具工程师、 高级产品运营、业财分析师、SEO专员、Tiktok小游戏运营、FlutterAPP开发工程师、资深渗透测试专家、资深云安全专家、 ------------------------------------------------------…

16 Nov 2026, 01:01 UTC879 viewsread 18 November 2026

❗️❗️日本--越南--斯里兰卡—香港--马来西亚--菲律宾---迪拜—知名集团月休6-8天 (周末双休),总有一个合适你的 ❤️⭕️远程职位:推广(团队)、招商专员、SEO专员、电销专员、短视频编导/内容策划、体育主播、体育天推、引流专员、高阶渗透工程师、拍摄达人、Golang开发、cocos工程师、产品经理、 ❤️🇬🇪格鲁吉亚:财务经理 ❤️🇸🇬新加坡:运维工程师、 ❤️🇻🇳越南职位:业务组长、运营主管、风控主管 ❤️🇨🇦香港:数据产品经理、数值策划、平台前端产品、活动运营、用户运、策略分析师、策略运营、UX专家/专员、产品经理、平台运营算法负责人、算法工程师、战略与经营分析师、资深平台运营算法、资深数值、资深slots产品、平台运营经理、平台策略运营、运营总监、首席合规官、 ❤️🇯🇵日本职位:财务专员、客服专员、网络链路与分发安全运维工程师、视频直播运维工程师、财务专员、Rust 工程师、golang开发、运营…

13 Nov 2026, 07:37 UTC≈1,210 viewsread 18 November 2026

K8S运维 工作地点:日本大阪 行业类型:IM即时通讯 薪资范围:30-40K 学历要求:统招本科 职责描述: 1、负责公司生产系统和测试系统搭建、更新、升级等; 2、负责公司技术基础组件搭建、更新、升级等; 3、负责公司办公环境日常维护; 4、为业务、行政等相关部门提供IT技术支撑。 5、为业务系统提供漏洞扫描、基线检查、弱口令检查、渗透测试等服务 职位要求: 1、本科及以上学历,3年以上运维工作经验; 2、学习能力强,具备较好的沟通和协作能力;思维逻辑清晰,语言书面表达能力强; 3、工作积极主动,具有较强的敬业精神与工作责任心。 4、熟悉K8S环境搭建,管理及优化,协助开发人员定位问题,至少1年以上生产K8S维护经验,有100+以上大型系统维护经验者优先; 5、熟悉jenkins、maven、gitlab、nacos、kong等devops工具; 6、熟悉k8s环境下promethues、grafana、elk、zabbi…

13 Nov 2026, 04:55 UTC≈1,150 viewsread 18 November 2026

资深会计专员—马来籍 薪资范围:RM6,000-RM12,000(特优另议) 工作地点:马来西亚吉隆坡 工作时间:周一至周五 9:30-18:30(双休) 应聘要求: 1.持有ACCA或CPA资格,至少4年相关工作经验 2.熟练MS Office及会计软件(最好熟悉SAP或Yonyou) 3.具备处理大量数据的能力 4.具备经验的簿记和会计原则、实务、标准、法律及法规知识 5.高度注重细节及准确性 6.能读听写中文、英文、马来文 7.具备沟通及演讲能力 工作职责: 1.管理每月财务结账流程,包括确保所有发生的成本均得到正确记录,审核会计分录、账户余额 对账及报告编制。 2.参与持续制定及建立会计政策、程序和运营策略,包括审核及实施流程与系统变更。 3.持续专注于提高系统效率和业务实践,积极审核财务及会计流程并提供建议。 4.与各级人员、预算负责人(部门主管或董事)及其他利益相关者进行沟通与合作,确保及时、 高效、准确地完成月末…

12 Nov 2026, 08:59 UTC≈1,120 viewsread 18 November 2026

职位名称:资深云安全专家 工作地点:菲律宾BGC 行业类型:菲律宾本土游戏 工作时间:9小时月休8天加菲假 薪资范围:面议 岗位定位 负责公司多云及混合云环境(华为云、AWS、阿里云、菲律宾 IDC)的整体安全架构与治理,建立可持续运行的云安全基线、权限治理与检测能力。 岗位职责 规划并落地多云统一的安全架构,涵盖账号体系、网络隔离、访问控制、加密与密钥管理、日志审计等。 制定各云平台的安全基线与配置标准,建立持续性的配置合规检测(CSPM),推动风险项整改闭环。 主导云上 IAM 治理,包括最小权限设计、权限梳理与回收、特权账号管理、跨账号/跨云访问控制,并与内部权限平台、审批流程打通,实现自动化开通与审计。 对云环境开展安全评估与攻击模拟,识别存储暴露、元数据服务利用、过度授权、密钥泄露等风险。 负责容器与 Kubernetes 安全,包括镜像安全、运行时防护、集群配置与 RBAC。 推动云原生日志(如 CloudTrai…

12 Nov 2026, 08:59 UTC861 views0 reactionsread 18 November 2026

职位名称:资深渗透专家 工作地点:菲律宾BGC 行业类型:菲律宾本土游戏 工作时间:9小时月休8天加菲假 薪资范围:面议 岗位定位 负责公司在线娱乐平台的攻击面安全评估,以攻击者视角发现高风险漏洞,尤其是涉及资金和账户的业务逻辑问题,并推动攻击能力的沉淀与自动化。 岗位职责 主导公司 Web、移动 App(Android/iOS)、API、后台管理系统及零信任接入体系的渗透测试,独立完成从信息收集、漏洞挖掘、利用到报告的全流程。 深入核心业务链路(充值、提现、活动奖励、账户体系、游戏交互)开展业务逻辑漏洞挖掘,识别越权、竞态条件、风控绕过、奖励滥用等高价值风险。 主导红队演练,模拟外部攻击及内部账号/终端失陷场景,评估横向移动与权限提升路径,输出攻击链复盘。 参与新业务、新版本上线前的安全评审与测试,制定测试标准,推动研发修复并复测闭环。 与安全开发团队协作,将测试方法、Payload 与检测思路沉淀为自动化渗透平台的规则和…

12 Nov 2026, 08:56 UTC774 views0 reactionsread 18 November 2026

职位名称:APP开发工程师 工作地点:菲律宾BGC 行业类型:菲律宾本土游戏 工作时间:9小时月休8天加菲假 薪资范围:面议 工作职责 负责游戏平台 App 的开发,独立完成从需求分析、框架设计到项目落地的全流程交付。 负责核心业务系统的架构设计,解决高并发、高复杂度 UI 前端工程的极致性能与稳定性问题。 负责 App 性能体系建设,围绕启动速度、渲染流畅度、内存占用、功耗发热和包体积做持续的专项优化,保证中低端机型的使用体验。 负责线上稳定性治理与疑难问题攻坚,对崩溃、ANR、卡顿等问题做根因定位,从源头修复。 负责 App 工程化体系构建,持续迭代 CI/CD、自动化测试、监控告警、性能诊断系统等工程化设施,建立性能防劣化机制,提升开发效能。 负责技术攻坚,如插件化架构、跨端融合、H5 容器加速、图形与动画渲染等解决方案,保持技术先进性。 负责用户体验优化,能设计合理的指标体系,持续观测和优化用户体验。 推动 AI 工具…

12 Nov 2026, 08:55 UTC787 viewsread 18 November 2026

职位名称:CRM客户管理管理 工作地点:菲律宾BGC 行业类型:菲律宾本土游戏 工作时间:9小时月休8天加菲假 薪资范围:面议 用户生命周期管理 -负责平台用户从注册、首存、复存、活跃、沉默到流失的全生命周期 CRM 运营 -根据用户行为、投注频率、充值金额、用户价值等维度进行精细化分层策略CRM 自动化营销 -负责 CRM 系统(Solitics)的日常操作、营销旅程配置及自动化策略 -通过 SMS、Email、Push、站内消息等渠道开展精准营销 协同与执行-与产品、数据及技术团队合作,推动 CRM 事件追踪、数据回传及功能优化 -与运营团队协作,达成KPI目标与业绩增长目标 数据分析与绩效优化 -每日及每周监控 CRM 核心指标,包括转化率、复存率、留存率、召回率及活动 ROI -关注营销成本与奖励投入效率,提升 CRM 增量贡献 跨部门协作与合规 与客服、VIP 团队协调用户沟通及会员服务…

12 Nov 2026, 07:39 UTC839 viewsread 18 November 2026

upay高级前端工程师 · 基建方向 工作地点: 迪拜(现场办公) 薪资: 面议 拟招聘人数:1-2人 岗位职责 1. 参与新一代前端(Web + App)核心模块开发,保证 PC、H5、App 多端的质量和性能。 2. 负责基础设施的开发和维护:脚手架、组件库、公共 SDK、构建体系。 3. 负责工程化能力的开发落地:CI/CD、自动化测试、灰度发布、热更新、前端监控。 4. 全程按团队的 AI 研发工作流开发,对自己提交的代码负责(含 AI 生成部分),并向 AI 效能工程师反馈问题和改进建议。 5. 参与技术规范制定和代码评审,解决性能、兼容性和疑难问题。 6. 沉淀可复用的组件、工具和文档,为业务团队提供基建支持与答疑。 任职要求 1. 5 年以上前端经验,TypeScript 熟练,精通 Vue3 生态,熟悉 Vite 等构建工具,理解前端工程化和性能优化。 2. 【必须】基建经验:亲手建设过脚手架、组件库、构建体系或…

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

Posts edited after publishing

@shuangxiugognzuo edited 13 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
10 August 2026
Most recent edit
14 November 2026

Posts recorded as deleted after publishing

We recorded 8 posts on @shuangxiugognzuo as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
10 August 2026
Most recent seen missing
14 November 2026
Median time before seen missing
7 days
Seen missing in the last 30 days
5

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.

找工作|招聘|人事【博牛招聘】
@bnzhaopingmnl · 106,536
Telegram ranks this channel #3 of 84 here — alongside 83 others — read 15 August 2026
TG招聘|求职|人才聚集地✳️
@XCRLZP · 104,460
Telegram ranks this channel #21 of 82 here — alongside 81 others — read 13 August 2026
远程工作者
@remote_cn · 25,976
Telegram ranks this channel #22 of 85 here — alongside 84 others — read 15 September 2026
abetterpath 招聘求职
@abetterpathxyz · 32,778
Telegram ranks this channel #28 of 90 here — alongside 89 others — read 4 September 2026
DeJob—Web3招聘求职频道📮
@DeJob_official · 48,023
Telegram ranks this channel #37 of 94 here — alongside 93 others — read 27 August 2026
🚗《招聘求职-柬埔寨东南亚吃瓜》
@zii33 · 104,625
Telegram ranks this channel #52 of 78 here — alongside 77 others — read 16 August 2026
求职招聘
@qzzpfabu888 · 610,185
Telegram ranks this channel #63 of 72 here — alongside 71 others — read 9 August 2026
TG招聘|东南亚新闻大事件‼️
@XMZPK · 59,711
Telegram ranks this channel #67 of 76 here — alongside 75 others — read 16 August 2026

This channel appears in 8 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 13 November 2026 — this entry's latest reading, not the date you are reading this.

“🔥多个国家月休8天工作交流(每周更新)” (@shuangxiugognzuo), 7,049 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/shuangxiugognzuo.

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.