Telegram RegisterThe public register of Telegram

Channel

🔖人事直聘|职缺列表|Rivi

@Winnieachr

On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

3,282subscribers

+18 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001711861875
TypeChannel
Username@Winnieachr
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/Winnieachr

Growth

3,2643,2823,2737 August 2026 — 3,264 subscribers7 August 2026 — 3,264 subscribers11 August 2026 — 3,272 subscribers14 August 2026 — 3,282 subscribers7 August 202614 August 2026
4 measurements spanning 7 days, net +18. 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 3,261–3,285 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 15:073,282+10
11 Aug 2026, 01:183,272+8
7 Aug 2026, 17:323,264no change
7 Aug 2026, 17:223,264first reading

Engagement

20 posts held, back to 13 April 2026the 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 · 30 days
43.1%
avg views ÷ 3,282 subscribers
Avg views / post
1,410
5 posts measured
Reaction rate
0.071%
reactions ÷ views · ER floor
Posts in window
5
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 1 August 2026
Posts held20 (13 April 20261 August 2026)
Views total7,073
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 23:38 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.

Reaction mix

27 reactions across 14 posts, in 3 distinct kinds. The most used accounts for 92.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2592.6%
🆒13.70%
👍13.70%

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 17 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 27reactions 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 13 April 2026 to 1 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

1 Aug 2026, 08:09 UTC923 views1 reactionsread 7 August 2026

📍吉隆坡-单休 Java 开发主管(Java Team Lead) ❤️‍🩹 10 年以上 Java 开发经验 ❤️‍🩹 有团队管理经验,带过研发团队 ❤️‍🩹 熟悉 Java 主流技术栈、微服务架构 ❤️‍🩹 能独立负责项目并带领团队交付 🐌Telegram:@vinnie_bb

1

Signed Rivi🌙

29 Jul 2026, 08:47 UTC≈1,390 views1 reactionsread 7 August 2026

📍日本东京 (优先在日本有签证) 大小周休息 ❤️‍🩹前端开发 ❤️‍🩹Go开发 🐌Telegram:@vinnie_bb

1

Signed Rivi🌙

28 Jul 2026, 01:31 UTC≈1,440 views3 reactionsread 7 August 2026

📍Playtime 📍日本东京 -游戏研发负责人(真人及电子) #岗位职责 1. 技术战略与研发体系建设 根据集团业务战略,制定真人游戏及电子游戏板块的中长期技术战略和产品研发规划。 负责游戏技术平台、产品架构及研发体系的整体设计与持续升级。 建立适用于多业务线、多品牌及多国家市场的统一技术架构。 推动研发流程、技术标准、代码规范、质量标准及技术治理体系建设。 评估行业技术趋势,并推动新技术在游戏研发及运营场景中的应用。 为集团全球市场拓展提供稳定、快速及可复制的技术能力。 2. 真人游戏平台研发 全面负责真人游戏产品及相关系统的规划、研发和技术管理,包括但不限于: 真人荷官游戏平台 视频直播及互动系统 游戏桌台管理系统 荷官管理系统 摄像头及视频采集系统 直播推流及视频编码系统 玩家互动及游戏控制系统 游戏逻辑及结算系统 玩家会话管理系统 钱包及支付接口 风控及异常行为监控系统 工作室运营支持系统 真人游戏后台管理系统 AI

3

Signed Rivi🌙

23 Jul 2026, 08:15 UTC≈1,670 views0 reactionsread 7 August 2026

📍Playtime BGC到岗 双休菲假 ❤️‍🩹平台运营 ❤️‍🩹平面设计 🐌Telegram:@vinnie_bb

Signed Rivi🌙

23 Jul 2026, 06:22 UTC≈1,650 views0 reactionsread 7 August 2026

📍迪拜-双休 高级Golang服务器开发 薪资范围 40,000-50,000RMB 🐌Telegram:@vinnie_bb

Signed Rivi🌙

16 Jul 2026, 02:47 UTC≈2,530 viewsread 7 August 2026

📍Playtime 棋牌数值策划 BGC到岗 双休菲假 #岗位职责 1.数值设计与平衡 o负责棋牌类游戏的核心数值体系设计,包括经济系统、成长系统、概率模型、胜负规则等。 o设计游戏内货币、道具、奖励的产出与消耗循环,确保长期可玩性和付费合理性。 o平衡玩家胜率、赔率、抽水比例等关键数值,优化游戏公平性与竞技性。 2.数学模型搭建 o建立游戏行为的数学模型(如牌型概率、随机算法、AI行为逻辑等),并通过模拟验证合理性。 o针对不同玩法模式设计差异化的数值策略。 3.数据分析与调优 o监控游戏上线后的数据表现(如付费率、留存率、对局时长等),提出数值优化方案。 o结合玩家反馈和测试结果,持续迭代调整数值参数。 4.协作与文档 o与系统策划、程序、美术团队协作,确保数值设计的可实现性。 o撰写详细的数值配置文档,输出公式、表格及逻辑说明。 #任职要求 1.必备条件 o2年以上棋牌类游戏数值策划经验,熟悉至少一种海外主流棋牌玩法(

Signed Rivi🌙

15 Jul 2026, 05:51 UTC≈2,040 views2 reactionsread 7 August 2026

Playtime-还要一位平面设计师 🐌Telegram:@vinnie_bb

1👍1

Signed Rivi🌙

2 Jul 2026, 07:25 UTC≈2,540 views2 reactionsread 7 August 2026

📍吉隆坡入职 #待招岗位 Vue/H5游戏前端开发 #上班时间 8小时 周末双休 #薪资范围 35,000-45,000RMB #岗位职责 -负责公司棋牌游戏 Web 前端开发,提供高效、稳定的前端开发工作。 -基于 Vue、HTML5、JavaScript / TypeScript 进行前端页面开发,实现游戏界面、交互逻辑、动画效果和业务流程开发。 -负责棋牌游戏、视频游戏等核心玩法的前端开发,包括牌桌界面、座位管理、下注操作、筹码动画、发牌动画、结算展示、倒计时、聊天互动等。 -负责与游戏服务端进行 WebSocket / HTTP 通信对接,实现实时消息推送、状态同步、断线重连、异常恢复等功能。 -负责 H5 游戏在 PC、移动端、不同浏览器和不同分辨率下的适配与性能优化。 参与游戏前端架构设计,优化项目结构、组件封装、资源加载机制和动画渲染性能。 -配合 UI、产品、后端、测试团队完成需求开发、联调测试、上线发布和版本

2

Signed Rivi🌙

2 Jul 2026, 07:21 UTC≈2,030 views1 reactionsread 7 August 2026

📍吉隆坡入职,后期胡志明 #待招岗位 Go棋牌服务器架构开发 #上班时间 8小时 周末双休 #薪资范围 40,000-50,000RMB #岗位职责 1.负责棋牌类游戏服务器架构设计与开发 2.负责高并发、高可用系统设计 3.负责 TCP / WebSocket 通信模块开发 4.负责游戏逻辑与服务端框架实现 5.负责系统性能优化及稳定性保障 #任职要求 1.负责棋牌游戏服务器架构设计、核心模块开发、性能优化和线上维护。 2.从 0 到 1 搭建完整的棋牌游戏服务端项目,包括网关、游戏房间、匹配、结算、用户状态、消息推送、日志、监控等模块。 3.负责 TCP、WebSocket 等长连接通信服务的设计与开发,保障客户端与服务端通信稳定、高效、低延迟。 4.负责高并发场景下的服务器性能优化,包括连接管理、消息分发、协程调度、内存优化、锁竞争优化等。 5.设计实现游戏核心逻辑,包括玩家匹配、断线重连、掉线托管、牌局状态恢复、防重

1

Signed Rivi🌙

25 Jun 2026, 08:44 UTC≈2,690 views1 reactionsread 7 August 2026

吉隆坡双休急招-高级测试工程师 🐌Telegram:@vinnie_bb

1

Signed Rivi🌙

19 Jun 2026, 12:34 UTC≈2,520 views2 reactionsread 7 August 2026

游戏运营 BGC 双休+菲假 # 岗位职责 1.根据项目的运营节奏及不同阶段的版本内容,制定游戏内运营活动及线上线下营销方案并推动实现和执行; 2.分析数据,并能根据游戏数据给出自己的改进建议并制定产品改进策略; 3.制定各种应急预案,妥善应对各种突发事件,保障项目稳定高速进行; 4.有效协调公司内部的合作资源,根据项目特色与内部平台进行合作构思并执行跟进,对合作效果进行良好的把控和分析,提升合作质量,有效调动公司内部资源为项目做出贡献。 5.熟悉pagcor和gli流程,编写合规送审文档。 #任职要求 1.三年以上棋牌游戏运营经验,有用户需求和游戏体验有洞察力; 2.熟悉移动网络游戏市场现状并深度了解棋牌类或休闲类游戏,有自己的想法; 3.数据导向,能基于数据分析并发现问题,并不断提升数据表现; 4.具有较强的人际沟通、协调和统筹策划能力,工作主动积极,认真负责,抗压能力强; 5.具有较强独立解决问题的能力,对数据有绝对

2

Signed Rivi🌙

19 Jun 2026, 08:52 UTC≈2,260 views2 reactionsread 7 August 2026

#待招岗位 游戏服务端(不限国籍) #工作地点 吉隆坡 双休 #薪资范围 面议 岗位职责: 1.负责游戏后端核心模块的设计、开发和持续优化,包括:用户系统、房间管理、匹配机制、游戏逻辑控制、实时对战等。 2.负责游戏服务的接入层与网关设计,确保游戏会话通信高效、稳定,并支持多游戏接入与状态隔离。 3.参与数据库与缓存架构设计,提升数据读写效率,确保游戏状态数据的一致性与高可用。 4.设计并实现游戏后端 API(REST/gRPC)接口,确保接口安全性、低延迟和良好扩展性,支持多平台(H5/客户端)调用。 5.负责游戏服务器的高并发支持、性能调优与稳定性保障,包括房间调度、限流机制、超时检测等。 6.参与部署、运维自动化及监控体系构建,提升服务可观测性,支持灰度发布和故障快速恢复。 7.撰写技术文档、代码评审,参与团队技术规范建设与技术攻坚任务。 任职要求: 1.本科及以上学历,计算机相关专业。 2.5 年以上后端开发经验,精

2

Signed Rivi🌙

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

Citation-graph rank — 1,121,276 of 1,350,102entries 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.

Mentions

Named by 2 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.

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.

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.

TG招聘|求职|人才聚集地✳️
@XCRLZP · 129,239
Telegram ranks this channel #8 of 82 here — alongside 81 others — read 13 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“🔖人事直聘|职缺列表|Rivi” (@Winnieachr), 3,282 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Winnieachr.

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.