Channel
@Jdjd8845
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
56subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003854142304 |
|---|---|
| Type | Channel |
| Username | @Jdjd8845 |
| Created | Between 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Jdjd8845 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 08:00 | 56 | no change |
| 8 Aug 2026, 00:33 | 56 | first reading |
20 posts held, back to 5 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.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 20 (5 July 2026 – 5 August 2026) |
| Views total | 474 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 08:00 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.
Lifetime counters from Telegram’s own channel header, read 10 August 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
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 1 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 1reactions 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 5 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.
🍇数值策划（Slots 游戏方向） base新加坡 35岁以下 薪资面议 卡学历 本科起，学历院校填写真实的 岗位职责 负责 Slots（老虎机）类游戏的数值体系设计与维护，主导主题项目的数值配置工作； 设计并优化转轮符号权重、赔付线结构、赔率表、免费游戏触发概率、Bonus 奖励分布等核心数值模型； 运用 跑库算法 进行大规模模拟运算，验证数值模型的长期预期回报率（RTP）、波动性、玩家留存曲线等指标； 熟练使用 纸带算法（物理纸带/虚拟纸带）配置转轮停靠逻辑，确保游戏结果符合合规要求且体验流畅； 针对 官方牌照类游戏（如菲律宾 PAGCOR、英国 UKGC、马耳他 MGA 等监管标准），设计满足合规要求的数值方案，撰写相关技术文档； 与程序、美术、测试紧密协作，跟进数值实装后的表现，根据运营数据持续调优数值平衡； 参与新玩法、新功能的数值原型设计，输出清晰的数值需求文档。 任职要求 必备条件 数学、统计…
🍇Cocos Creator 前端开发工程师 base新加坡 35岁以下 薪资面议 卡学历 本科起，学历院校填写真实的 岗位职责 基于 Cocos Creator 引擎，负责 Slots（老虎机）类休闲游戏的客户端功能开发与维护，重点参与主题项目的迭代； 与策划、美术、后端紧密配合，完成游戏 UI 交互、动画特效、数值表现、资源管理等模块的设计与实现； 优化游戏性能，解决不同机型上的适配、内存、帧率等问题，确保流畅体验； 参与游戏 SDK 接入（支付、统计、广告等），处理原生平台兼容性问题； 编写清晰的技术文档，参与代码 Review，推动团队开发规范落地。 任职要求 本科及以上学历，计算机相关专业优先； 5年以上 Cocos Creator 实际项目经验，至少完整参与过一款上线手游（有 Slots/棋牌/休闲类游戏经验者优先）； 精通 TypeScript / JavaScript，熟悉 Cocos C…
🍇投放运营 薪资范围：2500u-3500u 亚美尼亚 不超过35岁 职位定位 从运营角度切入投放工作，补足纯投放视角的盲区。协助投放负责人解读数据、制定计划，并串接运营端，让投放节奏与平台活动相互配合。 主要职责 1. 从运营角度分析数据，补足投放盲点 解读各渠道用户质量（留存、复充、活动依赖度等），提供投放视角之外的判断 针对投放决策提出运营端可能的风险与建议 协助识别数据异常背后的运营原因 2. 协助制定投放计划 参与渠道评估、预算分配、KPI 设定的讨论 使投放节奏与运营活动排期相互配合 3. 建议并配合运营制定平台活动 对接运营团队，从获客角度提出活动建议 追踪平台活动对投放效果的影响并反馈 任职要求 必备 一年以上博彩用户运营／活动运营／增长运营相关经验 对广告投放有基本认知，能理解 ROI、ARPPU、留存、复充等指标 具备数据分析能力，能从数据推导出可执行的建议 良好的跨团队沟通协调能力 具备独…
➡ 商务拓展总监（游戏行业）- QP/品牌商务部 国籍不限，可以远程 薪资待遇：保底 5000U + 高额佣金 / 分成（根据资源质量及业务体量可灵活协商） ✅岗位要求： 1. 具备游戏或 iGaming 行业商务拓展或相关商业岗位经验，有成功案例者优先。 2. 拥有成熟且可快速落地的商户 / 平台 / 渠道资源，并具备实际转化能力。 3. 熟悉行业合作模式、分成结构及商务谈判逻辑。 4. 具备优秀的独立谈判能力与资源整合能力，执行力强。 5. 具备中英双语沟通能力（如资源能力突出，可适当豁免该要求）。 6. 国籍不限。 1. Proven experience in gaming / iGaming business development or related commercial roles, with a strong track record preferred. 2. Existing, ready-to-…
产品专员（包网业务方向）3位 薪资范围2500u-3000u，35以下 亚美尼亚🇦🇲 岗位职责 负责包网产品的日常配置工作，包括活动、游戏、支付、公告、站点等后台配置。 根据标准流程完成新包网复制工作，确保各项配置与模板保持一致。 负责产品功能验收及上线测试，及时发现并反馈问题，跟进开发修复直至上线。 对接运营、技术、客服等部门，收集业务需求，整理并跟进产品需求开发进度。 协助维护产品配置文档、业务流程及操作规范，确保各盘口配置标准统一。 跟进新功能、新活动上线情况，确认配置及前后台功能正常运行。 完成领导安排的其他产品支持工作。 岗位要求 具备1年以上互联网、游戏平台或博彩行业产品运营、产品配置相关经验优先。 熟悉后台配置流程，具备较强的执行能力及细节把控能力。 逻辑思维清晰，能够理解业务需求并准确执行产品配置。 熟练使用 Excel、Word 等办公软件，具备基础的数据整理能力。 具备良好的沟…
🍇私域代理开发维护 工作地点：亚美尼亚 招聘人数：2人 薪资待遇： 每日8.5小时｜月休4天｜3个月试用期 薪资面议 岗位职责： 负责代理开发与日常维护。 维护 Telegram、WhatsApp 等社群。 跟进代理推广情况与活动通知。 协助提升代理活跃与转化。 任职要求： 熟悉 Telegram、WhatsApp 等社交软件。 具备良好沟通能力与执行力。 工作认真负责，服从安排。 能接受海外工作与夜班班次。 优先录取项： 有博彩或社群运营经验优先。 有代理资源或渠道资源优先。 会西语或英语优先。
🍇大媒体投手岗位职责 亚美尼亚 9休4 薪资面议 1. 广告投放与优化 主要负责在Facebook/Meta、Google Ads (UAC)、Tiktok，WS，TG等渠道进行拉美地区的流量采买 测试、优化和规模化广告活动，制定周度/月度媒体采购计划并输出报告 运用Cloaking技术和反检测浏览器，在受限平台环境下稳定投放 2. 漏斗构建与转化 设计并优化PWA（渐进式Web应用） 获客漏斗，降低从点击到首次存款（FTD）的摩擦 通过AB测试持续优化落地页、Offer、创意素材和用户体验 结合Telegram/WhatsApp社群流量，驱动注册与存款转化 3. 数据驱动决策 深度追踪并优化核心指标：ROI、NGR、GGR、LTV、FTD、CAC等 根据归因模型和分群数据，快速调整策略 任职要求 硬性条件 2年以上广告媒体采购经验，其中至少1-2年专注于iGaming/Casino行业 精通Facebook Ad…
🍇高级运营（数据分析+活动策划） 2名 不要台湾籍贯 仅要中国籍或马来籍 不超过35岁 📍 工作地点：越南胡志明 📍 上班时间：12小时休4 📍 试用期间：3个月 📍 薪资范围：面议 一 岗位职责： 1.用户分层与精细化数据运营：负责构建CRM基础体系及用户RFM分层模型，基于用户行为数据建立精准标签体系，实现差异化精准触达，提升单用户价值（ARPU）及留存率 。 2.活动策划与流失用户召回：定期策划并执行高转化的用户激励活动（如充值激励、排名赛等） ；针对流失与沉睡用户制定分层召回机制，有效提升用户复活率与留存表 。 3.数据监控与策略迭代：负责日常运营核心指标的监控与看板建设，能熟练运用SQL/Python等工具进行用户行为数据分析，通过数据复盘持续优化运营路径 。 二 任职要求： 1.学历经验：大专及以上学历 ，具备3年以上海外菠菜运营经验，有扎实的用户增长及数据分析复合背景者优先 。 2.技术加分项：掌握…
🍇高级数学工程师 工作地点：新加坡 · 全职 · 现场 7000u起 9小时双休 ❤️我们正在招聘一名高级数学工程师，负责设计并验证真钱及社交娱乐场游戏（老虎机、桌面游戏、 Crash / 即开类产品）背后的数学模型。您将全面负责从概念到认证的游戏数学工作，把创意玩法转化为 稳健、可证明公平且经过商业调优的数学模型。此职位处于工作室的核心，需与游戏策划、工程师及产 品团队紧密协作。 💭主要职责 · 为老虎机、桌面及即开类游戏设计并搭建数学模型，根据产品需求定义 RTP（返奖率）、波动性、命 中频率及最高奖金结构。 · 开发卷轴（reel strips）、赔付表、奖励/特色玩法机制以及累积/头奖逻辑。 · 在上线前通过蒙特卡洛模拟与解析验证，确认 RTP、方差及赔付分布。 · 为工程团队及监管/实验室认证（如 GLI、BMM、iTech Labs）编写完整的数学规格文档与 PAR 表。 · 支持受监管市场的送审工作，并回应测试…
🍇【go语言支付工程师】 薪资：面议 💭岗位职责： 1. 参与海外支付系统的架构设计、核心功能开发及性能优化，确保高并发、低延迟、高可用； 2. 负责支付交易、清算、对账、风控等核心模块的开发与维护； 3. 优化支付系统与银行、第三方支付渠道的对接，提升交易成功率与稳定性； 4. 深入分析支付链路中的性能瓶颈，持续优化系统响应时间和吞吐量； 5. 保障支付数据的安全性和一致性，设计合理的容灾和降级方案； 6. 跟踪支付行业技术趋势，探索新技术在支付场景中的应用（如区块链、实时风控等 💭任职要求： 负责支付系统核心模块的设计、开发和优化，保障支付业务的高效、稳定与安全【必须要有支付经验】 英语可以工作，至少可以读写,年龄范围<40 1. 计算机相关专业本科及以上学历，3年以上支付或金融系统开发经验； 2. 扎实的编程基础，熟悉常用数据结构和算法，精通 Golang，能在现有项目（如 Vue 前端）进行二次开发； 3. 深入…
🍇VIP运营培训经理（巴西 / 墨西哥市场） 薪资面议 要求必须女性做过线下公关的 语言发一段对于大客户维护的经验分享视频 亚洲人 前期远程后期日本 岗位职责 1. 负责搭建并管理巴西、墨西哥市场VIP客户运营体系，制定VIP客户维护标准、服务流程及运营规范。 2. 负责招聘、培训和管理当地VIP客服团队，输出高价值客户维护经验，提升团队客户服务能力。 3. 根据自身高端客户服务经验，培训当地团队如何： * 建立VIP客户信任关系； * 分析客户需求和消费习惯； * 制定个性化维护方案； * 提升客户活跃度和忠诚度； * 做好客户关怀及流失召回。 4. 制定VIP客服培训体系，包括新人培训、日常指导、服务质量检查及团队能力提升。 5. 负责VIP客户维护策略优化，根据客户反馈和运营数据持续调整服务方式。 6. 协助建立VIP客户档案管理体系，指导团队记录客户信息、沟通情况及维护效果。 7. 管理VIP客服团队日常工作，制…
🍇游戏后端开发工程师（老虎机 / 休闲游戏） base新加坡 薪资：4kU-7kU ⭐️定位：主职开发老虎机与休闲游戏的**后端服务**（80%），兼做上线前代码审计与反套利排查（20%）。我们要的是资金和公平性上靠得住的后端——你写的服务直接经手玩家的钱和游戏结果，所以"能跑通"远远不够，**每一行都要经得起"会不会被套利、会不会算错钱"的推敲**。 --- ⭐️你要做的事 1. **游戏后端开发（主）**：开发老虎机 / 休闲游戏（含 provably-fair 公平类）的后端服务与引擎——下注、结算、幂等、状态机、种子承诺/揭示、与钱包/运营商的交互。数值（RTP、赔率、权重）由数据科学家设计，你负责**准确落地并写验证**。 2. **数值验证**：能用蒙特卡洛验证实测 RTP == 设计目标，能反推赔付表、算 EV 做交叉核对——不设计数值，但对"数值有没有被工程实现搞偏"负责。需要基本的概率 / 统计舒适度，…
Showing the 12 most recent of 20 posts we hold for @Jdjd8845. 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 — 272,536 of 1,345,403entries 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 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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“岗位职责jd” (@Jdjd8845), 56 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/Jdjd8845.
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.