Telegram RegisterThe public register of Telegram
Telegram profile photo for 公司直招

Channel

公司直招

@aerbaniyazhi

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

569subscribers

+86 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-1002671452381
TypeChannel
Username@aerbaniyazhi
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 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/aerbaniyazhi

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 why it has no browse page of its own yet.

Growth

4835695267 August 2026 — 483 subscribers8 August 2026 — 488 subscribers8 August 2026 — 488 subscribers14 August 2026 — 507 subscribers21 August 2026 — 514 subscribers29 August 2026 — 523 subscribers7 September 2026 — 551 subscribers15 September 2026 — 569 subscribers7 August 202615 September 2026
8 measurements spanning 39 days, net +86. 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 470–582 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 18:21569+18
7 Sept 2026, 23:37551+28
29 Aug 2026, 07:47523+9
21 Aug 2026, 11:04514+7
14 Aug 2026, 16:15507+19
8 Aug 2026, 04:31488no change
8 Aug 2026, 02:41488+5
7 Aug 2026, 10:32483first reading

Engagement

15 posts held, back to 17 July 2026the 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 15 posts for this entry, the most recent from 2 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

4 reactions across 4 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4100.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 5 of the 15 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 17 July 2026 to 2 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

29 Jul 2026, 12:51 UTC522 views1 reactionsread 8 August 2026

【投放运营】 薪资范围:2500u-3500u 职位定位 从运营角度切入投放工作,补足纯投放视角的盲区。协助投放负责人解读数据、制定计划,并串接运营端,让投放节奏与平台活动相互配合。 主要职责 1.⁠ ⁠从运营角度分析数据,补足投放盲点 解读各渠道用户质量(留存、复充、活动依赖度等),提供投放视角之外的判断 针对投放决策提出运营端可能的风险与建议 协助识别数据异常背后的运营原因 2.⁠ ⁠协助制定投放计划 参与渠道评估、预算分配、KPI 设定的讨论 使投放节奏与运营活动排期相互配合 3.⁠ ⁠建议并配合运营制定平台活动 对接运营团队,从获客角度提出活动建议 追踪平台活动对投放效果的影响并反馈 任职要求 必备 一年以上博彩用户运营/活动运营/增长运营相关经验 对广告投放有基本认知,能理解 ROI、ARPPU、留存、复充等指标 具备数据分析能力,能从数据推导出可执行的建议 良好的跨团队沟通协调能力 具备独立思考能力,敢于提出

1

28 Jul 2026, 12:28 UTC500 views1 reactionsread 8 August 2026

【CRM 运营】 薪资范围:3500u-4000u 工作职责: 1.⁠ ⁠生命周期自动化运营 负责用户全生命周期 CRM 自动化旅程的设计、搭建及持续优化,包括注册、首充、复充、留存、召回、VIP 等场景。 配置并维护 Email、Push、SMS、站内信等自动化触达流程。 2.⁠ ⁠CRM 策略支持与需求评估 与运营团队协作,评估 CRM 需求及营销方案的合理性。 基于用户行为数据、历史表现及业务目标,对活动目标、人群、触发条件、触达时机及长期运营策略提出建议。 推动 CRM 决策数据化,避免缺乏数据支撑的运营策略。 3.⁠ ⁠用户体验与运营治理 建立并持续优化 CRM 运营规范,包括频率控制、生命周期互斥、活动冲突管理及用户体验优化。 确保各生命周期及营销活动协同运行,避免重复触达和过度营销。 4.⁠ ⁠数据分析与持续优化 持续监控 CRM 核心指标,分析活动效果,并提出优化建议。 跟踪 A/B

1

28 Jul 2026, 11:39 UTC447 viewsread 8 August 2026

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

28 Jul 2026, 07:12 UTC443 views1 reactionsread 8 August 2026

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

1

27 Jul 2026, 06:42 UTCviews —

公司直招 pinned «7月27日 需求岗位 ✍️亚美尼亚🇦🇲 代理维护专员 媒体投手 产品运营专员 BI 数据分析专员 运营质检专员 初级项目管理 盘口运营 风控专员 网红推广/投放 ✍️越南🇻🇳: 1、运营组长(高级运营) 2、渠道与投放管理 3、运营经理 4、高级数据分析 【运营中心】 项目管理办公室(PMO)负责人 【业务调控中心】 不要台湾籍 调控中心助理 【自投部 】 1、广告投放专员(后期亚美尼亚) 2、资深投放专家/经理(夜班;有巴西市场经验) 3、AI短视频创意设计师…»

27 Jul 2026, 06:41 UTC451 viewsread 8 August 2026

7月27日 需求岗位 ✍️亚美尼亚🇦🇲 代理维护专员 媒体投手 产品运营专员 BI 数据分析专员 运营质检专员 初级项目管理 盘口运营 风控专员 网红推广/投放 ✍️越南🇻🇳: 1、运营组长(高级运营) 2、渠道与投放管理 3、运营经理 4、高级数据分析 【运营中心】 项目管理办公室(PMO)负责人 【业务调控中心】 不要台湾籍 调控中心助理 【自投部 】 1、广告投放专员(后期亚美尼亚) 2、资深投放专家/经理(夜班;有巴西市场经验) 3、AI短视频创意设计师 4、中英俄投放助理 (base亚美) 【户管马甲包部】 广告投放账户主管 越南籍户管 【客维部】 不要台湾籍 2、墨西哥客服1名,需要女生 要会英语。(薪资800U,次月递增50U*4,1000U封顶) 3、客维主管(海外BC产品客户维护经验优先,15K-30K) 【总监助理】 1、投放助理(中+英+西+葡 12-15K 能接受出差)

24 Jul 2026, 13:13 UTC493 viewsread 8 August 2026

最新招聘需求: ✅ 代理维护专员 ×2 ✅ 媒体投手 ×2 ✅ 产品运营专员 ×3 ✅ BI 数据分析专员 ×1 ✅ 运营质检专员 ×1 薪资:2,500U–3,000U 年龄:35 岁以下 Base亚美尼亚 手慢无

24 Jul 2026, 13:09 UTC476 views0 reactionsread 8 August 2026

【BI数据分析专员】(1位) 岗位职责 负责平台各项经营数据的统计、监控及分析,包括用户、充值、留存、投注、活动、风控等核心数据。 独立开展数据分析工作,发现业务异常、数据波动及潜在风险,并分析原因及影响。 定期输出经营分析报告,客观评价各项业务表现,并提出数据分析结论及改善建议。 建立及维护各类数据分析模型、指标体系及监控机制,为管理层提供准确的数据支持。 配合各业务部门提供数据分析支持,但保持分析工作的独立性,确保分析结果客观、公正。 定期向管理层汇报分析结果,为业务决策、资源投入及风险控制提供数据依据。 岗位要求 具备2年以上数据分析、BI分析或商业分析相关工作经验。 数据敏感度高,具备独立分析问题及发现业务异常的能力。 熟练使用 Excel(熟悉函数、数据透视表、Power Query 等),具备 SQL 能力者优先。 能够独立编写数据分析报告,对数据结果进行客观评价,并提出具有参考价值的改善建议。

23 Jul 2026, 06:10 UTC483 views1 reactionsread 8 August 2026

7月23日 需求岗位 ✍️亚美尼亚🇦🇲 代理维护 盘口运营 风控专员 网红推广/投放 ✍️越南🇻🇳: 1、运营组长(高级运营) 2、渠道与投放管理 3、运营经理 4、高级数据分析 【运营中心】 项目管理办公室(PMO)负责人 【业务调控中心】 不要台湾籍 调控中心助理 【自投部 】 1、广告投放专员(后期亚美尼亚) 2、资深投放专家/经理(夜班;有巴西市场经验) 3、AI短视频创意设计师 4、中英俄投放助理 (base亚美) 【户管马甲包部】 广告投放账户主管 越南籍户管 【客维部】 不要台湾籍 2、墨西哥客服1名,需要女生 要会英语。(薪资800U,次月递增50U*4,1000U封顶) 3、客维主管(海外BC产品客户维护经验优先,15K-30K) 【总监助理】 1、投放助理(中+英+西+葡 12-15K 能接受出差) 2、总监业务助理两名(要求985本科,年龄27以内,有全国数学竞赛拿奖的优先)

1

23 Jul 2026, 05:42 UTC428 viewsread 8 August 2026

盘口运营X2 风控X1 (只要有相关工作经验的) 不超过35岁 可接受中国或马来籍贯 薪资一万二转一万五 Base亚美尼亚 手慢无

21 Jul 2026, 11:37 UTC461 viewsread 8 August 2026

【高级运营】(数据分析+活动策划) 2名 中国籍或马来籍 35- 📍 工作地点:胡志明 📍 上班时间:12小时休4 📍 试用期间:3个月 📍 薪资范围:面议 一 岗位职责: 1.用户分层与精细化数据运营:负责构建CRM基础体系及用户RFM分层模型,基于用户行为数据建立精准标签体系,实现差异化精准触达,提升单用户价值(ARPU)及留存率 。 2.活动策划与流失用户召回:定期策划并执行高转化的用户激励活动(如充值激励、排名赛等) ;针对流失与沉睡用户制定分层召回机制,有效提升用户复活率与留存表 。 3.数据监控与策略迭代:负责日常运营核心指标的监控与看板建设,能熟练运用SQL/Python等工具进行用户行为数据分析,通过数据复盘持续优化运营路径 。 二 任职要求: 1.学历经验:大专及以上学历 ,具备3年以上海外菠菜运营经验,有扎实的用户增长及数据分析复合背景者优先 。 2.技术加分项:掌握基础的SQL、Pyth

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

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

“公司直招” (@aerbaniyazhi), 569 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/aerbaniyazhi.

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.