Telegram RegisterThe public register of Telegram
Telegram profile photo for 岗位JD

Channel

岗位JD

@AJgangweijd

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

629subscribers

+112 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002547960993
TypeChannel
Username@AJgangweijd
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 November 2026
Measurements held13
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/AJgangweijd

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 21 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@AJgangweijd/535 · this entry24 Jul 2026, 06:21 UTC@haiwaiJD/34824 Jul 2026, 07:22 UTC1.0061 minutes
@AJgangweijd/547 · this entry7 Aug 2026, 05:32 UTC@haiwaiJD/3597 Aug 2026, 07:00 UTC1.0088 minutes
@AJgangweijd/534 · this entry24 Jul 2026, 06:20 UTC@haiwaiJD/34724 Jul 2026, 07:21 UTC0.9561 minutes
@AJgangweijd/543 · this entry3 Aug 2026, 06:45 UTC@haiwaiJD/3563 Aug 2026, 06:56 UTC0.9511 minutes
@AJgangweijd/536 · this entry24 Jul 2026, 06:22 UTC@haiwaiJD/34924 Jul 2026, 07:24 UTC0.9262 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@haiwaiJD5 (5/5 hand-verifiable sample passed)0.9661 minutesthis entry (5–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 18 comparable posts for this entry, running 18 July 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 3 channels, the one whose matching posts we hold earliest is @haiwaiJD. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

5176295737 August 2026 — 517 subscribers8 August 2026 — 517 subscribers15 August 2026 — 530 subscribers24 August 2026 — 550 subscribers1 September 2026 — 549 subscribers10 September 2026 — 555 subscribers19 September 2026 — 579 subscribers8 October 2026 — 598 subscribers15 October 2026 — 608 subscribers22 October 2026 — 611 subscribers28 October 2026 — 613 subscribers5 November 2026 — 622 subscribers15 November 2026 — 629 subscribers7 August 202615 November 2026
13 measurements spanning 100 days, net +112. 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 500–646 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Nov 2026, 08:10629+7
5 Nov 2026, 19:39622+9
28 Oct 2026, 23:46613+2
22 Oct 2026, 20:39611+3
15 Oct 2026, 18:47608+10
8 Oct 2026, 00:55598+19
19 Sept 2026, 16:15579+24
10 Sept 2026, 03:15555+6
1 Sept 2026, 05:56549-1
24 Aug 2026, 08:13550+20
15 Aug 2026, 15:06530+13
8 Aug 2026, 04:03517no change
7 Aug 2026, 12:32517first reading

Engagement

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

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

5 reactions across 5 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤5100.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 6 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 5 reactions 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 16 July 2026 to 7 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

7 Aug 2026, 05:32 UTC134 viewsread 8 August 2026

【体育产品总监】 base深圳南山 岗位职责 全权负责海外体育竞技类产品整体规划,聚焦竞技对战、赛事竞玩、比分推演、体育闯关、球星对战等核心竞技玩法设计,面向东南亚、拉美等海外市场制定产品周期规划,对流水、付费转化、次日 / 7 日留存、LTV 核心指标负责。 深挖海外球迷喜好(足球、篮球、美式体育为主),结合联赛赛程周期性上新竞技模式:实时赛事对战、多人 PK 竞技、赛季天梯排位、赛事挑战赛、球星阵容养成竞技体系,完成玩法创新、迭代、淘汰全生命周期管理。 搭建竞技商业化体系:竞技门票、赛季通行证、球星卡牌养成礼包、竞技专属道具、段位特权会员等变现模块设计,兼顾竞技平衡性与营收收益,避免逼氪流失。 以数据驱动竞技玩法迭代,分析对战胜率、玩法参与率、付费节点、流失节点,落地 A/B 测试优化竞技平衡性、匹配机制、奖励体系,提升用户竞技时长与复玩频次。 联动研发、风控、运营、本地化团队落地版本排期、灰度上线、赛季更新;针对不同国…

5 Aug 2026, 13:15 UTC173 views1 reactionsread 8 August 2026

活动运营(海外市场) 薪资:20K-35K 上班时间:12小时月休4 中国籍/马来籍贯 不超过35岁 base胡志明 可接猎头 岗位职责 负责美区、拉美、东南亚及印度市场的线上活动运营,结合当地用户特征、文化习惯及节庆热点,制定区域化活动策略。 独立策划并落地大型线上活动,包括方案设计、资源协调、上线执行、风险控制及效果复盘。 参与营收功能和付费玩法的设计与优化,如会员、订阅、虚拟道具、充值激励及用户付费成长体系等。 基于用户行为、付费数据及活动数据,搭建分析模型,持续优化活动机制、奖励结构和商业化效率。 制定活动核心指标并进行效果监控,推动用户活跃、留存、付费转化、ARPU及营收增长。 协同产品、研发、设计、市场及本地化团队,保障项目按期、高质量交付。 持续跟踪海外市场趋势、竞品动态及优秀案例,沉淀可规模化复用的活动运营方法论。 任职要求 本科及以上学历,3年以上互联网活动运营、用户运营或商业化运营经验。 对美区、拉美、东…

❤1

5 Aug 2026, 10:25 UTC159 viewsread 8 August 2026

技术三部 base新加坡 35岁以下 薪资面议 卡学历 本科起(要看学校,不然也是进不去)学历院校填写真实的 数值策划(Slots 游戏方向) 岗位职责 负责 Slots(老虎机)类游戏的数值体系设计与维护,主导主题项目的数值配置工作; 设计并优化转轮符号权重、赔付线结构、赔率表、免费游戏触发概率、Bonus 奖励分布等核心数值模型; 运用 跑库算法​ 进行大规模模拟运算,验证数值模型的长期预期回报率(RTP)、波动性、玩家留存曲线等指标; 熟练使用 纸带算法(物理纸带/虚拟纸带)配置转轮停靠逻辑,确保游戏结果符合合规要求且体验流畅; 针对 官方牌照类游戏(如菲律宾 PAGCOR、英国 UKGC、马耳他 MGA 等监管标准),设计满足合规要求的数值方案,撰写相关技术文档; 与程序、美术、测试紧密协作,跟进数值实装后的表现,根据运营数据持续调优数值平衡; 参与新玩法、新功能的数值原型设计,输出清晰的数值需求文档…

5 Aug 2026, 10:25 UTC159 viewsread 8 August 2026

技术三部 base新加坡 35岁以下 薪资面议 卡学历 本科起(要看学校,不然也是进不去)学历院校填写真实的 Cocos Creator 前端开发工程师岗位职责 基于 Cocos Creator​ 引擎,负责 Slots(老虎机)类休闲游戏的客户端功能开发与维护,重点参与主题项目的迭代; 与策划、美术、后端紧密配合,完成游戏 UI 交互、动画特效、数值表现、资源管理等模块的设计与实现; 优化游戏性能,解决不同机型上的适配、内存、帧率等问题,确保流畅体验; 参与游戏 SDK 接入(支付、统计、广告等),处理原生平台兼容性问题; 编写清晰的技术文档,参与代码 Review,推动团队开发规范落地。 任职要求 本科及以上学历,计算机相关专业优先; 5年以上 Cocos Creator 实际项目经验,至少完整参与过一款上线手游(有 Slots/棋牌/休闲类游戏经验者优先); 精通 TypeScript / Ja…

3 Aug 2026, 06:45 UTC233 views1 reactionsread 8 August 2026

经营创新管培生(BC投流行业) 薪资:12-18K 工作时间:12小时 休息:周休半天 中国籍或者马来籍 学历本科 要有数分基础和投放基础 不超过26岁 base越南 一、岗位介绍 我们是一家高速发展的互联网营销公司。 相比于寻找一个"执行者",我们更希望寻找一位持续探索、持续学习、持续创新的人。 如果你喜欢研究新事物、喜欢拆解问题、喜欢验证自己的想法,希望通过一次次实验推动整个公司的成长,那么这个岗位可能非常适合你。 你的工作,不是完成每天固定重复的任务,而是帮助公司不断寻找更高效率的方法、更低成本的方案以及新的增长机会。 二、岗位职责 1、经营创新 持续关注行业变化,主动寻找新的业务模式、流量渠道、营销方式及管理方法,为公司提供创新解决方案。 2、实验设计与验证(AB Test) 针对公司经营过程中存在的问题,设计测试方案并进行小规模实验,包括但不限于: 广告投放策略测试 素材AB测试 账户测试 落地页测试 商务合作…

❤1

30 Jul 2026, 11:28 UTC331 viewsread 8 August 2026

推广专员 薪资:13K 工作时间:晚上8点到早上9点 月休2 工作地点:亚美尼亚埃里温 岗位职责: 负责与客户沟通广告活动相关事宜,维护良好的客户关系; 协助工作主管完成日常运营及推广相关工作; 配合团队完成广告推广任务,跟进活动执行情况; 及时反馈客户需求及工作进展,提升推广效果。 岗位要求: 年龄优先考虑 28岁以下,有较强学习能力和发展意愿; 有推广、销售、客服或相关行业工作经验者优先; 工作认真负责,积极主动,具备良好的沟通能力; 能吃苦耐劳,适应团队工作节奏; 短期内无回国计划,能够稳定长期发展

28 Jul 2026, 12:37 UTC384 views1 reactionsread 8 August 2026

CRM 运营 所属部门: 技术一部 工作地点: 亚美尼亚 工作时间: 每日8.5小时,月休4天,具体班次根据部门安排 试用期: 3个月 薪资范围:3500u-4000u 工作职责: 1.⁠ ⁠生命周期自动化运营 负责用户全生命周期 CRM 自动化旅程的设计、搭建及持续优化,包括注册、首充、复充、留存、召回、VIP 等场景。 配置并维护 Email、Push、SMS、站内信等自动化触达流程。 2.⁠ ⁠CRM 策略支持与需求评估 与运营团队协作,评估 CRM 需求及营销方案的合理性。 基于用户行为数据、历史表现及业务目标,对活动目标、人群、触发条件、触达时机及长期运营策略提出建议。 推动 CRM 决策数据化,避免缺乏数据支撑的运营策略。 3.⁠ ⁠用户体验与运营治理 建立并持续优化 CRM 运营规范,包括频率控制、生命周期互斥、活动冲突管理及用户体验优化。 确保各生命周期及营销活动协同运行,避免重复触达和过…

❤1

28 Jul 2026, 11:47 UTC354 viewsread 8 August 2026

财务专员 所属部门: 技术一部 工作地点: 亚美尼亚 工作时间: 每日8.5小时,月休4天,具体班次根据部门安排 试用期: 3个月 薪资范围 2200u-2500u 崗位職責: 负责日常账务处理、凭证编制、费用报销审核等基础财务工作; 协助进行业务财务支持,包括合同审核、收支核算、利润分析等; 跟进项目的成本核算、毛利测算及相关报表编制; 协助税务申报、对接审计、完成财务月结及年结工作; 配合业务部门提供财务数据分析与决策支持,优化业务流程。 任职资格: 【会计类专业应届生也可】 财务、会计相关专业,大专及以上学历,有初级会计职称优先; 2年以上财务工作经验,具备业务财务支持经验者优先; 熟练操作财务软件及Excel,具备良好的数据分析能力; 做事细致严谨,责任心强,沟通能力良好,能适应快节奏工作环境。

28 Jul 2026, 07:12 UTC348 viewsread 8 August 2026

四方支付商务专员 只要台湾籍或者马来籍 不超过35岁 但是资源丰富的可放宽年纪 岗位职责 1. 市场拓新:负责墨西哥全境支付业务开发,挖掘本地聚合支付服务商、连锁商户、跨境电商等核心客户,落地本地化拓客方案,完成交易流水、商户新增等业绩指标; 2. 商务落地:独立完成商务洽谈、费率对接、合同签约、方案定制,跟进支付通道对接、技术联调及上线全流程,协调国内团队解决业务卡点; 3. 客户运维:维护存量合作渠道与商户,监控通道稳定性、交易数据,处理对账、结算、故障问题,提升客户留存及交易规模; 4. 市场调研:实时跟进墨西哥支付监管政策、本地支付生态及竞品动态,输出市场分析报告,提供业务优化建议; 5. 合规风控:落实本地支付合规要求,完成商户入网审核、备案,配合风控排查交易风险、合规风险,保障业务稳健运营; 6. 资源搭建:维护本地行业资源,定期汇总业务数据、工作进度,同步总部落实海外业务战略。 任职要求 1. 学历经验:…

24 Jul 2026, 13:30 UTC422 viewsread 8 August 2026

BI数据分析专员(1位) 所属部门: 技术一部 工作地点: 亚美尼亚 工作时间: 每日8.5小时,月休4天,具体班次根据部门安排 试用期: 3个月 薪资范围:2500u-3000u 岗位职责 负责平台各项经营数据的统计、监控及分析,包括用户、充值、留存、投注、活动、风控等核心数据。 独立开展数据分析工作,发现业务异常、数据波动及潜在风险,并分析原因及影响。 定期输出经营分析报告,客观评价各项业务表现,并提出数据分析结论及改善建议。 建立及维护各类数据分析模型、指标体系及监控机制,为管理层提供准确的数据支持。 配合各业务部门提供数据分析支持,但保持分析工作的独立性,确保分析结果客观、公正。 定期向管理层汇报分析结果,为业务决策、资源投入及风险控制提供数据依据。 岗位要求 具备2年以上数据分析、BI分析或商业分析相关工作经验。 数据敏感度高,具备独立分析问题及发现业务异常的能力。 熟练使用 Excel(熟悉函…

24 Jul 2026, 12:22 UTC403 views1 reactionsread 8 August 2026

产品专员(包网业务方向)3位 所属部门: 技术一部 工作地点: 亚美尼亚 工作时间: 每日8.5小时,月休4天,具体班次根据部门安排 试用期: 3个月 薪资范围:2500u-3000u 岗位职责 负责包网产品的日常配置工作,包括活动、游戏、支付、公告、站点等后台配置。 根据标准流程完成新包网复制工作,确保各项配置与模板保持一致。 负责产品功能验收及上线测试,及时发现并反馈问题,跟进开发修复直至上线。 对接运营、技术、客服等部门,收集业务需求,整理并跟进产品需求开发进度。 协助维护产品配置文档、业务流程及操作规范,确保各盘口配置标准统一。 跟进新功能、新活动上线情况,确认配置及前后台功能正常运行。 完成领导安排的其他产品支持工作。 岗位要求 具备1年以上互联网、游戏平台或博彩行业产品运营、产品配置相关经验优先。 熟悉后台配置流程,具备较强的执行能力及细节把控能力。 逻辑思维清晰,能够理解业务需求并准确执行…

❤1

24 Jul 2026, 06:22 UTC398 viewsread 8 August 2026

远程商务专员5名 商务专员需要开发和建立大量的优质代投团队合作,并且自带代投团队资源优先。目前主要拓展菲律宾市场,有商务1年经验,业绩能带到10W U以上优先考虑。 一、 基本信息 招聘岗位:商务专员/组长 所属部门:商务部门 汇报对象:商务主管 工作地点:远程 岗位性质:全职规范 公司愿景:共创 ・ 共生 ・ 共荣,连接全球资源,共创无限价值。 二、 岗位简介与使命 控风险,控成本,控信息,保障业务高效、有序执行。扩展资源渠道,建立公司外部的代投团队生态,为公司创造更多更优质的流量增长。 三、 岗位职责(核心职责) 成本管控:对钱有敬畏,对于放出的每一笔预算认真、负责。 数据整理:负责数据整理、制表,保证数据真实性,不修饰、不隐瞒,日报清晰。 风险管控:不超预算,不私自更改规则,投流有边界感,不指挥策略。 商务对接:对于基础指标理解到位,具备甲方立场意识,信息传递准确,对外沟通规范,对接流程完整。 完成上级安排的其他工作事项…

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

Mentions

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

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 15 November 2026 — this entry's latest reading, not the date you are reading this.

“岗位JD” (@AJgangweijd), 629 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/AJgangweijd.

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.