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

Channel

岗位JD

@leyigw

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

2subscribers

+0 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1004446881517
TypeChannel
Username@leyigw
Created11 August 2026measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live3 September 2026
Measurements held2
On Telegramt.me/leyigw

Growth

212 August 2026 — 2 subscribers13 August 2026 — 2 subscribers12 August 202613 August 2026
2 measurements spanning 2 days. 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 1–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 22:342no change
12 Aug 2026, 04:162first reading

Engagement

6 posts held, back to 11 August 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.

ERR · 30 days
690.0%
avg views ÷ 2 subscribers
Avg views / post
13.8
5 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
6
of 6 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 August 2026
Posts held6 (11 August 202611 August 2026)
Views total69
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 22:34 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.

Recent posts

11 Aug 2026, 08:13 UTC17 viewsread 13 August 2026

审核风控专员(非大陆籍) 薪资:2100U起 工作时间:9小时/天 三班倒 双休+法定假期 补贴:房补450U 餐补300U 工作地点:亚美尼亚 职位职责/Job Responsibilities: 1. 审核公司所有产品的提款提案; 2. 各产品洗码优惠的计算和审核; 3. 审核各产品推出的促销优惠; 4. 游戏套利/游戏异常排查; 5. 存款和在线支付的复核; 6. 额度丢失的判定和补额度; 7. 报表数据处理 8. 领导交代的其他工作。 职位要求/Job Requirements: 1. 大专以上学历,逻辑思维好,理解领悟能力好; 2. 熟悉游戏套利与玩法 3. 高度的工作责任心, 对工作一丝不苟认真细心; 4. 能接受排班(含长期小夜)大夜班工作,工作

11 Aug 2026, 08:13 UTC18 viewsread 13 August 2026

数据分析专员 薪资:2400U起 工作时间:9小时/天 9am-6pm 双休+法定假日 补贴:房补450U 餐补300U 工作地点:亚美尼亚 职位职责 1、岗位概要:负责数据的抓取计算和分析,对数据波动做出解释性报告,并提出解决建议 2、工作内容: A、通过业务平台,抓取基础数据,计算业绩数据。 B、通过月报形式,反馈运营情况。 C、对关键数据进行分析,制定业绩与费用标准。 D、对数据波动进行每月的分析判断,汇报原因,提出解决方案。 E、拥有良好的团队协作能力,善于沟通,执行力出色。 职位要求 1、专业知识:熟悉数据跟踪、抓取、分析,有数据敏感性,能及时从基础数据波动中发现问题。 2、专业技能:精通excel,有其他数据分析应用程序基础者更佳 3、行业背景:互联网产品、金融业、网络游戏或同业背景 4、所需经验:一年以上的数据分析经验 5、性格特点:细致认真,善于思考,主动性强 6、其他要求:要求职业道德良好,无不良记录,无频

11 Aug 2026, 08:11 UTC14 viewsread 13 August 2026

高级运营视觉设计师 薪资:3500-5000美 地点:亚美尼亚 房补餐补:450+300美金 岗位职责 岗位职责 1. 负责公司重点运营项目、品牌活动及大型营销活动的整体视觉创意与设计输出,包括活动主视觉、专题页面、Banner、广告投放素材及品牌推广视觉等。 2. 能够深入理解业务目标、用户特征及营销策略,将运营需求转化为具有视觉吸引力和商业传播价值的创意设计方案。 3. 能够独立负责大型项目从创意概念、视觉方向、Moodboard、主视觉设计到多渠道延展及最终落地的完整设计流程。 4. 能够主导重要活动的视觉方向制定,并建立完整的视觉体系,确保不同页面、素材及传播渠道具有统一且具有辨识度的视觉语言。 5. 具备较强的创意策划与视觉表现能力,能够针对不同业务场景提出多种创意方向,并推动优秀方案落地。 6. 熟练运用 Photoshop、Illustrator、Figma 等设计工具,并能够根据项目需求建立高效的设计工作流

11 Aug 2026, 08:11 UTC11 viewsread 13 August 2026

中级运营视觉设计师 薪资:3000-4000美 地点:亚美尼亚 房补餐补:450+300美金 岗位职责 1. 根据运营、市场及产品需求,负责 Banner、活动页面、专题视觉、社交媒体素材等运营视觉设计。 2. 能够准确理解需求,在既定的品牌视觉规范和设计方向下,独立完成视觉方案设计及最终交付。 3. 能够根据不同活动主题进行视觉创意,并熟练运用构图、色彩、字体、光影、材质、合成等设计手法提升画面表现力。 4. 负责活动视觉在不同平台、尺寸及终端的适配与延展,保证不同渠道的视觉统一性。 5. 熟练使用 Photoshop、Illustrator、Figma 等主流设计工具,能够独立完成日常运营设计需求。 6. 能够运用 Midjourney、Stable Diffusion / FLUX、Adobe Firefly、ChatGPT 等 AI 工具辅助进行创意探索、素材生成及设计生产,提高工作效率。 7. 能够对 AI 生成

11 Aug 2026, 08:11 UTC9 viewsread 13 August 2026

高级 UI 设计师 薪资:4000-5000美 地点:亚美尼亚 房补餐补:450+300美金 岗位职责 1. 负责公司产品的 Web / H5 / App 等产品界面设计,从需求分析、信息架构到 UI 设计及最终落地,完整参与产品设计流程。 2. 深入理解产品业务及用户需求,将业务目标转化为清晰、合理且具有良好体验的界面设计方案。 3. 建立并持续完善 产品设计规范及 Design System(设计系统),包括颜色、字体、间距、组件、交互状态等,提升产品设计的一致性与设计效率。 4. 熟练使用 Figma 进行界面设计、组件搭建、Auto Layout、Variants、Prototype 等工作,并能够建立规范化、可复用的设计文件。 5. 具备较强的系统化设计思维,能够从整体产品体验出发解决复杂页面、功能模块及多端适配问题,而不仅局限于单页面视觉表现。 6. 与产品经理、开发工程师及其他设计师密切协作,推动设计方案落地

Showing the 6 most recent of 6 posts we hold for @leyigw. 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 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.

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

“岗位JD” (@leyigw), 2 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/leyigw.

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.