Channel
@jishuJD
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
796subscribers
-2 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002592913706 |
|---|---|
| Type | Channel |
| Username | @jishuJD |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/jishuJD |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 15:13 | 796 | -2 |
| 9 Aug 2026, 02:51 | 798 | no change |
| 8 Aug 2026, 09:01 | 798 | first reading |
20 posts held, back to 22 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 1 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 31 July 2026 |
|---|---|
| Posts held | 20 (22 July 2026 – 31 July 2026) |
| Views total | 4,090 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 09: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.
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 22 July 2026 to 31 July 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.
【财务专员】 Financial Specialist 待遇： • 工作时段 - 依照排班 - 12 H • 地点 - 菲律宾 • 月休- 2 日 • 试用期- 30 日 • 底薪 - 10000-16000 RMB 小白 • 底薪 - 12000-17000 RMB 有经验 • 生活补助 - 400 RMB / 月 • 生日补贴：260 RMB • 绩效奖金 - 0~3000 RMB • 满 6 个月未回国奖金 - 3000~6000 RMB • 公司包吃住 工作要求： ⚡东南亚外籍，中文听、说、读、写 熟练 ⚡熟练使用 Word / Excel ⚡学习能力强，理解能力好 ⚡对数字敏感、逻辑思维能力强者 优先 ⚡限女 工作职责: ✨监控支付通道 ✨下发、审核款项 ✨支付相关费用 ✨制作及维护财务报表 ✨跨部门沟通与协调 🔗返回簡介 …
🍇CRM 运营 薪资范围：3500u-4000u 亚美尼亚 35岁以下 工作职责： 1. 生命周期自动化运营 负责用户全生命周期 CRM 自动化旅程的设计、搭建及持续优化，包括注册、首充、复充、留存、召回、VIP 等场景。 配置并维护 Email、Push、SMS、站内信等自动化触达流程。 2. CRM 策略支持与需求评估 与运营团队协作，评估 CRM 需求及营销方案的合理性。 基于用户行为数据、历史表现及业务目标，对活动目标、人群、触发条件、触达时机及长期运营策略提出建议。 推动 CRM 决策数据化，避免缺乏数据支撑的运营策略。 3. 用户体验与运营治理 建立并持续优化 CRM 运营规范，包括频率控制、生命周期互斥、活动冲突管理及用户体验优化。 确保各生命周期及营销活动协同运行，避免重复触达和过度营销。 4. 数据分析与持续优化 持续监控 CRM 核心指标，分析活动效果，并提出优化建议…
#亞美尼亞 #網站運營高管 薪资五万起-面议 亚美上班，欧美籍也可 职位名称 网站运营高管（Website Operations Manager） 工作内容（Job Description） 负责网站日常运营及活动规划，确保各项活动如期上线并顺利执行。 *与产品部门协作，规划网站首页、专题页及产品展示配置，优化用户浏览体验。 *与技术团队沟通需求，协调前端页面开发、修改及功能优化，追踪开发进度并验收成果。 *负责活动页、Banner、商品资讯、图片及文案等内容的上架与维护。 跨部门协调设计、产品、技术、营运等团队，确保需求正确落地并按时完成。 规划网站版位配置，提升网站整体视觉呈现及转换效果。 监控网站活动成效，分析流量、点击率、转换率等数据，提出优化建议。 负责网站内容品质管理，定期检查页面异常、连结错误及功能运行情况。 制定网站运营流程及标准，提高跨部门合作效率。 完成主管交办之其他网站运营相关事项。 …
#亞美尼亞 #商戶 商户管理专员／商户经理 工作内容： 负责公司合作商户的日常管理与维护，建立长期合作关系。 定期分析商户营运数据： 营收 会员数 留存率 转换率 活跃度 提出改善建议。 1. ）协助商户完成产品上架、活动配置、功能设定及相关营运需求。 2. ）与产品、技术、客服、风控及财务团队协调，确保商户需求顺利落地。 3. ）规划并执行商户营运方案，提高商户营收及平台使用率。 定期与商户召开线上或线下会议，回报营运成果并收集需求。 负责商务文件、合作合约及相关资料管理。 4. ）处理商户问题、客诉及紧急事件，提供快速解决方案。 持续挖掘商户需求，推广新产品、新功能及促销活动，提高合作深度。 5. ）完成主管交办事项。 任职条件 大专以上学历。英文流利 2 年以上 Account Manager、Merchant Management、Customer Success 或平台营运相关经验。 良好的沟通与协调能力…
#亞美尼亞 职位名称：UX设计师 / 用户体验设计师（海外/博彩方向） 职位描述： 我们正在寻找一位对产品逻辑敏锐、熟悉海外/国际合规博彩（iGaming）业务的 UX 设计师。你将负责公司博彩类网站及产品的 Web/H5/App 端信息架构规划、页面交互与排版布局设计，打造符合国际合规要求、顺畅且具备高转化率的用户体验。 任职要求 1. 行业经验（硬性要求）： 本科及以上学历；拥有 3 年以上 Web 端 UX 设计 / 交互设计经验，必须具备国际合规博彩（iGaming / Sportsbook / Casino）网站或 App 的实际 UX/交互设计经验（必须附带作品集）。 2. 业务与合规理解： 熟悉海外博彩用户的核心路径（KYC 身份认证、充值提现、游戏选择、投注流程等）。 理解国际合规要求（如 UKGC、MGA、Curacao 等常见牌照下的 UX 规范与“责任博彩”设计细则）。 3. 专业技能： …
包网产品经理 办公地址：塞尔维亚 岗位职责： 负责博彩C端(现金网、娱乐城)系统的整体规划与设计 · 包含前台网站、后台管理、中控系统、支付系统、代理系统、风控系统、报表系统等全链路模块。 · 明确功能规划、写作产品文档、绘制流程图/原型图。 负责业务需求分析与解决方案输出 · 对接运营、商务、客户成功团队，拆解需求并转化为可实现的产品方案。 · 输出 PRD、用例、数据结构设计等。 持续优化平台体验与数据表现 · 进行业务数据分析，提出用户体验优化方案与营收增长策略。 · 推进游戏接入、支付接入、活动工具、新版 UI、代理工具等迭代。 竞品分析与市场调研 · 熟悉各大竞品平台Stake、BC.Game、Bet365等。 · 输出竞品分析报告，为平台策略提供依据。 客户需求支持 · 支持商务谈单：提供…
招聘需求｜私域代理开发维护专员 工作地点： 亚美尼亚 工作时间： 每日8.5小时，月休4天，具体班次根据部门安排 试用期： 3个月 薪资待遇： 面议 岗位职责 负责代理资源的开发、对接及日常关系维护 负责Telegram、WhatsApp等私域社群的运营与管理 跟进代理推广进度，收集问题并协调处理 提升代理活跃度、推广效率及转化表现 定期整理代理数据及工作进展。 维护老代理开发新代理 具备数据分析能力 任职要求 熟悉Telegram、WhatsApp等社交及通信工具； 具备良好的沟通能力、服务意识和执行能力； 工作认真负责，具备团队协作意识，服从工作安排； 能够适应海外工作环境及夜班轮班安排。 优先录取 具有博彩行业、代理开发或社群运营经验； 会西语加分 🔗返回簡介 🌐 联系hr
❤1
大媒体投手岗位职责 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 Ads、Google Ads等主流投放平台，有…
🇮🇩🇮🇹🇭🇳 | 📌 职位：会计专员 🖋行业性质：交易所、钱包、电商、游戏等 💰 薪资福利： 薪资范围：10,000 ~ 18,000 AED 性别：不限 地点：迪拜、市中心 年龄：< 40 国籍：马来、台湾、越南、印尼 工作时间：10 小时，月休4 🎁 Benefits | 员工福利： 1、餐补：60 AED /工作日 2、房补：3000～4000 AED （仅限外宿人员) 3. 薪资结构：13薪 4. 年休假：每年两次年休假，未使用满两次年假者可获得一个月基本工资的补贴 5. 每周五提供员工下午茶时光。各部门每季度组织一次团队建设活动。 6. 公司承担工作签证费用（服务满一年后公司不再追偿） 7. 公司报销入职所用单程机票（转正后，无需承担费用） 8. 节假日提供过节红包 🎯 Responsibilities | 工作职责 1、制定公司财务目标、策略和计划，包括预算编制、资金筹集和资金分配等 2、负责编制财务报告，包…
岗位：产品经理 （迪拜） 薪资： 面议 📋岗位职责 1、负责视频播放器产品的规划、设计及迭代，围绕播放体验、会员能力、广告变现、数据统计等核心场景持续优化产品功能。 2、负责客服系统及相关业务平台的产品设计与维护，包括工单管理、在线客服、智能客服、用户反馈处理等模块建设。 3、深入理解业务需求，独立完成需求调研、竞品分析、产品方案设计、原型输出及PRD编写。 4、负责需求全生命周期管理，推动产品需求高质量落地，确保项目按计划交付。 5、协调研发、测试、运营等团队资源，推进项目实施，及时发现并解决项目风险和问题。 6、关注行业动态及用户反馈，通过数据分析持续优化产品体验和业务指标。 7、负责产品上线后的效果跟踪和运营支持，推动产品持续迭代升级。 📝任职要求 1、本科及以上学历，5年以上互联网产品经理经验。 2、具备独立负责产品模块或完整项目经验，能够独立推进需求落地。 3、熟悉产品设计流程，能够熟练使用 Axure、Figm…
🇲🇾｜📌 职位：高级私厨 💰 薪资福利： 薪资范围：20,000 RMB 起步 性别：不限 主要办公地点：马来西亚 出差地区：日本、香港、迪拜、法国等（根据业务安排轮动） 年龄：< 40 国籍：马来西亚 工作时间：10小时（包含1小时休息），月休4天 注意事项：中文流利、愿意出差 🎯 Responsibilities | 工作职责 1、负责会所日常餐饮制作及菜品出品质量把控 2、根据VIP需求制定及调整菜单 3、负责食材处理、备料及厨房卫生管理 4、控制出品标准，确保口味稳定与食品安全 5、根据不同接待需求完成宴请、私宴等餐饮安排 6、配合领导或VIP外出时提供随行餐饮服务（如有安排） 7、厨房成本控制及食材管理 📝 Qualifications | 任职要求 1、性别不限，年龄不限（身体健康即可） 2、具备扎实厨艺基础，能独立完成菜品制作 3、擅长粤菜、湘菜、川菜、福建菜其中一种或多种菜系优先 4、有会所、私房菜、高端餐…
🇲🇾｜📌 职位：会所助理 - 女 💰 薪资福利： 薪资范围：8,000 ~ 12,000 MYR 主要办公地点：马来西亚 或迪拜 出差地区：日本、香港、法国等（根据业务安排轮动） 年龄：< 32 工作时间：10小时（包含1小时休息），月休4天 注意事项：中英文流利、仪表整洁 国籍：马来、台湾 🎯 Responsibilities | 工作职责 1、跟随公司VIP进行国内外出差、协助处理行程安排、日程协调及现场事务支持。 2、迎接到访会员／宾客，办理签到、登记、指引至会所设施或活动场所。 3、回应宾客的咨询、需求或投诉，及时转交相关部门并跟进结果，确保贵宾体验满意。 4、协助会所活动或大型会议期间的会员服务执行，如用餐安排、饮品服务、场地指引等。 5、检查会所公共区域、休闲设施、会议／宴会场地是否整洁、安全、设备完好，发现问题及时上报或跟进维修。 6、协助配合清洁、安全、餐饮、娱乐等团队保持会所环境品质，营造舒适、专业的会所氛…
Showing the 12 most recent of 20 posts we hold for @jishuJD. 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 — 947,592 of 1,481,502entries 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 1 registered channel — 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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“JD - Ginnie 人才岗” (@jishuJD), 796 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/jishuJD.
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.