Telegram RegisterThe public register of Telegram
Telegram profile photo for 全球直招!!

Channel

全球直招!!

@leyiHR888

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

10,175subscribers

+137 since we began measuring on 12 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1004442761724
TypeChannel
Username@leyiHR888
Created8 August 2026measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live31 August 2026
Measurements held18
Confirmed unchanged1 time, most recently 31 August 2026
On Telegramt.me/leyiHR888

Growth

10,03810,17510,106.512 August 2026 — 10,038 subscribers13 August 2026 — 10,044 subscribers14 August 2026 — 10,056 subscribers16 August 2026 — 10,061 subscribers17 August 2026 — 10,066 subscribers18 August 2026 — 10,090 subscribers19 August 2026 — 10,108 subscribers20 August 2026 — 10,120 subscribers21 August 2026 — 10,126 subscribers23 August 2026 — 10,138 subscribers24 August 2026 — 10,145 subscribers25 August 2026 — 10,152 subscribers26 August 2026 — 10,158 subscribers27 August 2026 — 10,161 subscribers28 August 2026 — 10,164 subscribers29 August 2026 — 10,167 subscribers30 August 2026 — 10,168 subscribers31 August 2026 — 10,175 subscribers12 August 202631 August 2026
18 measurements spanning 19 days, net +137. 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 10,017–10,196 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 14:3410,175+7
30 Aug 2026, 14:1610,168+1
29 Aug 2026, 15:3510,167+3
28 Aug 2026, 18:2410,164+3
27 Aug 2026, 15:0410,161+3
26 Aug 2026, 18:1610,158+6
25 Aug 2026, 20:0210,152+7
24 Aug 2026, 19:3510,145+7
23 Aug 2026, 01:0510,138+12
21 Aug 2026, 12:0610,126+6
20 Aug 2026, 14:3610,120+12
19 Aug 2026, 13:4410,108+18
18 Aug 2026, 15:4310,090+24
17 Aug 2026, 12:0610,066+5
16 Aug 2026, 02:0810,061+5
14 Aug 2026, 09:3710,056+12
13 Aug 2026, 01:5410,044+6
12 Aug 2026, 04:1510,038first reading

Engagement

11 posts held, back to 8 August 2026the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 24 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.98%
avg views ÷ 10,175 subscribers
Avg views / post
608
8 posts measured
Reaction rate
0.234%
reactions ÷ views · ER floor
Posts in window
11
of 11 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. It is computed over the 2 of 8 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 13 August 2026
Posts held11 (8 August 202613 August 2026)
Views total4,864
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 03:44 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.

Reaction mix

3 reactions across 1 post, in 1 kind.

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

Measured over the 11 most recent posts we hold, published 8 August 2026 to 13 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

13 Aug 2026, 14:19 UTCviews —

全球直招!! pinned «🌐 全球地区直招 🥰😐 😌🥰 🤢🤮 🏄‍♂ 📌到岗:日本🇯🇵新加坡🇸🇬亚美尼亚🇦🇲迪拜🇦🇪塞尔维亚🇷🇸 😒集团人事直招 ,英雄不问出处,无中介!!! 😒公司手续齐全一切合规 取得目标国国家博彩许可 😒公司背景:老牌博彩持证经营平台 😒 华人圈海外龙头企业之一 😒 全集团任何岗位绝对自由【不收私人手机】 😒 节假日礼金、生日礼金、过年红包,更有13-17薪福利 😒 发展空间大,团队稳定,福利完善。 😒 欢迎有能力、有冲劲的伙伴加入我们! 😒 亚美尼亚,塞尔维亚等项目岗位火热招聘中…»

13 Aug 2026, 14:19 UTC759 views3 reactionsread 29 August 2026

🌐 全球地区直招 🥰😐 😌🥰 🤢🤮 🏄‍♂ 📌到岗:日本🇯🇵新加坡🇸🇬亚美尼亚🇦🇲迪拜🇦🇪塞尔维亚🇷🇸 😒集团人事直招 ,英雄不问出处,无中介!!! 😒公司手续齐全一切合规 取得目标国国家博彩许可 😒公司背景:老牌博彩持证经营平台 😒 华人圈海外龙头企业之一 😒 全集团任何岗位绝对自由【不收私人手机】 😒 节假日礼金、生日礼金、过年红包,更有13-17薪福利 😒 发展空间大,团队稳定,福利完善。 😒 欢迎有能力、有冲劲的伙伴加入我们! 😒 亚美尼亚,塞尔维亚等项目岗位火热招聘中 😒 岗位涵盖:技术开发、数据分析、运营、市场推广、财务、 职能、直播运营、风控、商务拓展等多个方向. 🌈 空缺岗位招聘: ✔推广✔客服✔运营✔财务✔人资✔数据 ✔管理层:面议 ✔技术部: 🌈高级UI 、产品经理、前端架构师、社群媒体经营 🌈golang后端工程师、用户运营

3

11 Aug 2026, 08:18 UTC766 viewsread 29 August 2026

🍇亚美尼亚岗位 审核风控专员(非大陆籍) 数据分析专员 高级运营视觉设计师 中级运营视觉设计师 高级 UI 设计师 💰您想咨询的岗位‼提供个人简历,我们可以更快为您匹配最适合您的岗位哦 求职联系TG😝: @leyiiiiiii

9 Aug 2026, 10:04 UTC727 viewsread 29 August 2026
Photo

推广专员 上班时间: 固定月休8天;轮班制 10:00-19:00;每月允许一次连休3天; 薪酬说明:2000USDT+高额提成、模式、经费面谈 房补 450美金 餐补 260美金 入职一周内报销机票费用 工作地点1:亚美尼亚 工作地点2:非中国非越南地区,其他地方均可应聘 年龄要求:34岁以内(超出年龄勿投递) 5️⃣任职要求 1. 有过一年以上综合/电子/体育/C票/棋牌等平台的代理招商或代理维护工作经验 2. 拥有有效的代理招商相关的推广手段和方法 3. 有优质代理及客户,有特殊获客渠道的优先 4. 善于包装自己,提高自我认知及善于沟通,情商高,心态积极,具备抗压能力。 5️⃣ 岗位职责 1. 负责公司综合平台(真人为主)C票/体育/棋牌/德州等产品的代理招商和代理维护工作 2. 熟知各类灰产聊天软件,通过广告及群发精聊代理及客户进行转化 3. 通过有效的个人推广手段及广告投放,如软文推广,QQ群,电报群,

9 Aug 2026, 10:04 UTC616 viewsread 29 August 2026
Photo

岗位名称:SVIP营销专员 工作地点: 亚美尼亚 薪资:薪资范围2000U起 房补 450美金 餐补 260美金 上班时间: 固定月休8天 国籍限制:非大陆籍 ​一、岗位职责 ​负责公司客户的一对一专属服务,建立并维护良好的客户关系。 ​根据客户需求,提供专业咨询、活动策划及解决方案,提升客户满意度与合作体验。 ​跟进客户日常服务流程,包括资料整理、需求沟通、问题反馈及售后跟进。 ​定期与客户保持联系,了解客户最新需求、使用情况及意见建议。 ​及时处理客户投诉、疑问及突发问题,并协调相关部门推动解决。 ​挖掘客户潜在需求,促进增值服务销售。 ​负责客户档案、服务记录及相关数据的整理与更新,确保信息准确完整。 ​完成公司安排的客户维护、业务跟进及相关服务指标。 ​二、岗位需求 ​市场营销、工商管理、客户服务等相关专业优先。 ​具备客户服务、销售、客户关系管理或相关工作经验者优先。 ​具有良好的沟通表达能力、服务意识及客户维护能

9 Aug 2026, 10:04 UTC541 viewsread 29 August 2026

运营专员 工作内容: 1. 负责线上线下活动,并针对运营工作或运营活动进行资料跟踪分析及总结, 根据数据效果,推进网站的改进和营销策略的改变; 2. 负责网站的运营规划,结合产品需求与市场调查分析, 制定一系列完善的产品整体运营规划并执行; 3. 各类活动/优化需求运营验收与开发、设计对接等; 4. 日常运营维护、线上问题即时处理,事故处理并即时反馈相应部门,降低事故损失; 5. 与其他部门有效沟通及共同完成项目策划及执行工作; 6. 主管交办的其他事宜。 岗位需求: 1. 2年以上平台运营或用户运营经验,熟悉word/ excel优先考虑; 2. 良好的沟通能力,协调能力,做事清晰,做人简单; 3. 对数据敏感和日常运营维护能力; 4. 抗压能力强,责任心强,能接受KPI指标

9 Aug 2026, 10:04 UTC522 views0 reactionsread 29 August 2026

🆕Telegram社群运营 国/籍:中国 薪/资:2300-2500美 人数:2人 工作时间:9小时月休8天(12点-21点) 工作地点:亚美尼亚 岗位职责: • 负责Telegram群组和频道的日常管理与运营,确保社群活跃度和正面氛围; • 制定并实施Telegram社群运营策略,包括内容规划、活动策划及用户互动方案; • 分析社群数据(如用户增长、活跃度、用户反馈等),定期汇总报告,并持续优化运营策略; • 通过各种手法将目标客户引流到群或频道, • 处理突发状况和用户投诉,维护社群稳定 • 跟踪Telegram平台新功能及行业动态,及时调整运营策略以适应市场变化。 岗位要求: • 对Telegram平台及其运营机制有深入了解,熟悉各项功能和规则; • 拥有较强的数据分析能力,能够根据数据结果优化运营方案; • 良好的沟通协调能力,耐心细致,具备解决突发问题的应变能力; • 具备相关社群运营或新媒体运营经

9 Aug 2026, 10:03 UTC499 viewsread 29 August 2026
Photo

在线客服 国/籍:非大陆籍,年龄21-30 薪/资:2000-2500USDT 人数:3人 工作时间:9小时月休8天 工作地点:亚美尼亚 岗位要求: 1、学历要求:高中及以上 2、1年以上客服或电服经验 3、熟悉常用办公软件如excel、word、outlook、客服工作基本流程等相关专业知识 4、打字速度80字/分以上 5、普通话(中文)标准,不带过重口音 6、技巧职能: ​做事有条理,肯吃苦耐劳,愿意接受轮班工作(三班倒) ​思路清晰,有销售意识,有服务概念 ​学习能力强,有目标、稳定性强,长期工作计划 ​有耐心,善于沟通,语言表达能力强 ​良好的团队沟通协调能力、应变能力 岗位职责: 1. 负责在线文字客服工作,及时回复客户咨询并处理相关问题。 2. 负责客户账户、额度、优惠及游戏相关事项处理。 3. 负责内部工作群沟通及业务事项跟进,包括存取款、运维、游戏及运营相关事务。 4. 负责账户信息修改审核、邮件回复及相关

9 Aug 2026, 10:03 UTC434 viewsread 29 August 2026
Photo

社区专员 薪资:2700U+ 房补+餐补:450U+300U 工作地点:亚美尼亚 岗位职责 1.主播管理与排班 负责论坛直播主播的招募、培训及日常管理,确保主播团队高效运作; 制定主播排班计划,协调直播时间,保障直播内容的稳定输出; 监督主播表现,定期反馈优化建议,提升直播质量与用户互动体验。 2.活动策划与执行 策划并组织论坛直播相关活动(如专题直播、节日活动、用户互动等),提升用户参与度和粘性; 跟踪活动数据,分析效果并优化后续方案,确保活动目标的达成; 协调内外部资源,推动活动顺利落地执行。 3.产品优化与验收 收集用户及主播反馈,提出直播产品功能优化建议,推动技术团队迭代改进; 参与新功能或改版测试,负责验收并反馈问题,确保产品体验符合预期; 监测直播平台运行状况,及时跟进并解决突发问题。 4.数据分析与运营优化 定期分析直播数据(如观看量、互动率、转化率等),制定运营策略调整方案; 结合行业动态和竞品分析,探

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

Citation-graph rank — 743,170 of 1,629,518 entries 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.

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.

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.

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

“全球直招!!” (@leyiHR888), 10,175 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/leyiHR888.

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.