Channel
@Tsukikeji
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
751subscribers
+10 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003740812731 |
|---|---|
| Type | Channel |
| Username | @Tsukikeji |
| Created | Between 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/Tsukikeji |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 06:53 | 751 | +10 |
| 7 Aug 2026, 13:30 | 741 | no change |
| 7 Aug 2026, 01:01 | 741 | first reading |
20 posts held, back to 24 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 1 pageof 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. It is computed over the 4 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 20 (24 July 2026 – 5 August 2026) |
| Views total | 6,200 |
| Reactions total | 6 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 01:01 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.
6 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 50.0% | |
| 😁 | 2 | 33.3% | |
| 🌚 | 1 | 16.7% |
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 4 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 6reactions 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 24 July 2026 to 5 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.
海外包网技术总监 ⭕️第三国远程, 需有海外包网项目经验 薪资：面议 岗位职责： 1. 负责包网平台整体技术架构设计与研发管理。 2. 带领研发团队，推动项目开发与技术落地。 3. 负责系统稳定性、性能优化及技术升级。 4. 与产品、运营团队协作，确保项目高效交付。 任职要求： 1. 5年以上包网行业经验，3年以上技术团队管理经验。 2. 目前已在第三国工作，有长期海外工作经验。 3. 熟悉包网整体业务架构及开发流程。 4. 有巴西包网项目经验者优先。 5. 熟悉熊猫包网或同类型包网产品者优先。 6. 精通 Java 、微服务、MySQL、Redis、Docker、Kubernetes 等主流技术。 7. 具备良好的团队管理能力、沟通能力及项目推动能力。 求职联系：@Tsuki618 @Daisymakati
亚美尼亚开放岗位： 高級前端/Go/視頻剪輯/ 非中國籍的—-》UX /會CRM的運營 1、运营总监 2、产品运营专员 3、客服助理，2000U，30以内。中国/马来籍。 4、推广专员 5、投放专员（马来/中国籍） 求职联系：@Tsuki618 @Daisymakati
岗位名称：golang工程师 工作时间：10小时，月休4 工作地点：菲律宾居家 薪资待遇：30~40K + 房补 + 餐补 + 项目奖金 工作内容：负责公司大型站群系统的开发和管理 相关经验：有CMS系统开发经验者优先 岗位职责 1. 负责公司CMS（内容管理系统）、门户网站矩阵及SaaS化内容服务平台的核心模块设计与Go语言后端开发。 2. 推进CMS系统的改造与高并发架构优化，满足千万级PV、高并发访问及海量数据存储的稳定性需求。 3. 能够设计灵活的内容模型（如自定义字段、多语言支持、分类体系）、权限管理（RBAC）及工作流引擎。 4. 设计并实现CMS插件化机制、模板引擎解析及API开放平台（如OpenAPI等），方便第三方系统集成与二次开发。 5. 对接各大CDN加速服务、对象存储（OSS）、搜索引擎（Elasticsearch）及第三方营销组件。 6. 编写高质量代码及技术文档，保障系统安全（防SQL注入、XSS…
职位需求更新（可远程）： 急召：cocos creator 学历：大专以上 薪资：25k内 待遇：出差按照到岗薪资算，3000日元/日补贴，提供住宿 补充：需要远程+出差（出差日本，办理3-5年旅游签证）
为什么目前大部分公司都要求开视频呢 因为代面横行 代工作的太多 还有明明是中国人还假装自己是其他国籍的人 用p图身份去弄 导致现在市场这样 入职了就变了个人工作 不诚信的人太多
❤1😁1
这种脑残真的不要来浪费大家时间 找工作很容易吗
🌚1😁1
马尼拉岗位： DBA 技术支持 java AI应用开发工程师 服务端开发 技术总监 测试总监 高级运维 高级网络工程师 dba值班 项目管理 PMO 用户界面设计师 高级投资经理 前端产品经理 游戏产品经理 flutter（移动客户端专家） 资深测试 战略运营总监 资深UI 设计师 资深真金游戏策划 资深游戏前端工程师 高级游戏厅前端工程师 高级游戏后端工程师 ui设计师 品牌活动经理 数据分析师/科学家 - 市场营销背景 求职联系：@Tsuki618 @Daisymakati
❤1
岗位名称：资深UI 设计师 薪资范围：面议 办公时间：双休 工作职责： 1. 负责游戏整体 UI 视觉设计，包括界面布局、图标/Icon、按钮、弹窗、HUD、背包与数值界面等。 2. 参与游戏风格制定，输出符合世界观与美术方向的 UI 视觉风格稿与规范文档。 3. 设计并维护 UI 组件库、主题皮肤及界面规范，确保后续版本的统一性与延续性。 4. 熟悉主流游戏 UI 风格，以休闲娱乐类为主（如卡牌、SLG、MMO、二次元、科幻等为次要），并具备良好的整体设计把控能力。 任职要求（Requirements） 1. 美术、视觉传达、交互设计等相关专业优先，本科及以上学历。 2. 3–5 年以上游戏 UI 设计经验，有完整项目上线经验者优先。 3. 熟练使用 Figma / Photoshop / Illustrator；熟悉 Spine / After Effects 等动效工具者为加分项。 软素质要求（Soft Skills）…
岗位名称：海外数字币盘产品负责人 工作时间：9小时月休6 工作地点：马来西亚 吉隆坡 薪酬范围：面议 岗位职责 1. 负责海外数字币平台（体育、真人、电子、虚拟币等）的产品规划和整体设计，制定产品发展路线图并推动落地。 2. 深入研究海外市场用户需求、行业趋势及竞品动态，持续优化产品体验和商业模式。 3. 负责用户增长、留存、充值转化及投注转化等核心指标，对产品经营结果负责。 4. 统筹产品需求管理，输出产品方案、原型及需求文档，协调研发、测试、运营等团队完成产品交付。 5. 负责数字货币相关业务设计，包括充值、提现、钱包、转账、返水、代理等核心功能。 6. 持续优化投注链路、会员体系、活动体系及数据分析体系，提高平台活跃度和用户价值。 7. 推动数据化运营建设，通过数据分析发现问题并制定优化方案。 8. 协调第三方供应商、游戏厂商及支付渠道的产品对接工作，保障项目顺利上线和稳定运营。 9. 建立产品规范及管理流程，提高团队整…
岗位名称：资深真金游戏策划(Senior RMG Designer) 薪资范围：面议 办公时间：双休菲假 岗位职责： 独立负责真金游戏的玩法设计、规则设计、系统设计及完整策划方案。 主导Paytable、Base Game、Free Spin、Bonus、Jackpot及特色机制设计。 与数值人员共同制定RTP、波动率、命中率、赔付结构和大奖分布。 负责游戏节奏、中奖反馈、演出逻辑及玩家体验设计。 深度拆解头部竞品，结合目标市场提出可落地的差异化玩法。 输出原型、流程图、配置表和详细策划文档，并推动程序、美术和音效落地。 负责版本验收和体验调优，解决玩法、数值及表现层问题。 分析上线后的局数、投注、留存和玩家行为数据，持续优化产品。 任职要求： 4年以上真金游戏策划经验，至少3款完整上线产品经验。 能够独立完成一款真金游戏从概念到上线的全部策划工作。 熟悉Slots常见结构及机制，如Ways、Clust…
❤1
资深游戏前端工程师（Senior Unity / Cocos D二veloper） 薪资范围：面议 办公时间：双休+菲假 岗位职责 负责 Slot、Casino、Mines、Bingo 等游戏客户端开发与迭代。 实现转轴、连消、Wild、Scatter、Free Spin、Bonus、Jackpot 等核心玩法和表现效果。 对接登录、钱包、下注、派彩、游戏记录、埋点及游戏 SDK。 负责动画、特效、音效、资源加载、断线重连和异常恢复。 参与游戏前端框架、公共组件和项目脚手架建设。 配合策划、美术、后端及 QA 完成联调、测试和上线。 任职要求 5 年以上游戏客户端开发经验。 熟练掌握 Unity 或 Cocos Creator，精通 C#、TypeScript 或 JavaScript。 熟悉动画、粒子、状态机、对象池、资源管理和网络通信。 具备移动端性能优化和复杂问题排查能力。 能独立负责一款游戏从开发、联调到上线。 加…
岗位名称：高级游戏厅前端工程师 薪资范围：面议 办公时间：双休+菲假 岗位职责 负责游戏大厅、游戏分类、推荐、搜索、活动及个人游戏记录等功能开发。 负责游戏启动器和游戏容器开发，支持 H5、Cocos、Unity WebGL 等游戏接入。 对接用户、钱包、余额、游戏列表、收藏、最近游戏及运营推荐能力。 负责大厅多语言、多币种、响应式布局及移动端适配。 优化首屏加载、游戏启动速度、资源缓存和弱网体验。 建设前端埋点、异常监控、性能监控和运营配置能力。 任职要求 5 年以上 Web 或移动端前端开发经验。 熟练掌握 JavaScript、TypeScript、HTML5 和 CSS3。 熟练使用 Vue 或 React 等主流框架。 熟悉前端工程化、状态管理、权限、缓存和网络通信。 具备大型前端项目架构设计和性能优化能力。 能独立负责游戏大厅模块设计、开发和上线。 加分项 有游戏平台、游戏大厅、棋牌、Casino 或内容聚合平…
Showing the 12 most recent of 20 posts we hold for @Tsukikeji. 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 — 233,002 of 1,480,944entries 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 18 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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“Tsuki_海外技术招聘求职中心” (@Tsukikeji), 751 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/Tsukikeji.
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.