Telegram RegisterThe public register of Telegram

Channel

集团招聘 直招

@Kay202602

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

325subscribers

+1 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-1003814001684
TypeChannel
Username@Kay202602
CreatedBetween 1 February 2026 and 8 April 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/Kay202602

Topic

Job listings — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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.

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 word for word on 1 other registered channel. 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@J9zhizhao/25921 Apr 2026, 05:36 UTC@Kay202602/67 · this entry21 Apr 2026, 05:36 UTC1.00under a minute
@Kay202602/71 · this entry13 May 2026, 00:53 UTC@J9zhizhao/26413 May 2026, 00:53 UTC1.00under a minute
@Kay202602/75 · this entry21 May 2026, 01:54 UTC@J9zhizhao/26821 May 2026, 01:54 UTC1.00under a minute
@J9zhizhao/27017 Jun 2026, 10:08 UTC@Kay202602/77 · this entry17 Jun 2026, 10:14 UTC1.007 minutes
@J9zhizhao/27310 Jul 2026, 07:43 UTC@Kay202602/80 · this entry10 Jul 2026, 07:43 UTC1.00under a minute
@J9zhizhao/2746 Aug 2026, 10:18 UTC@Kay202602/81 · this entry6 Aug 2026, 10:18 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@J9zhizhao6 (6/6 hand-verifiable sample passed)1.00under a minute@J9zhizhao (42)

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. 1 of the 4 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 18 comparable posts for this entry, running 8 April 2026 to 6 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).

Across the whole group of 2, the earliest publisher we hold is @J9zhizhao. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 7 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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

324325324.57 Aug 2026, 07:16 — 324 subscribers7 Aug 2026, 12:15 — 325 subscribers7 Aug 2026, 07:167 Aug 2026, 12:15
2 measurements taken within a single day, net +1. 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 324–325 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 12:15325+1
7 Aug 2026, 07:16324first reading

Engagement

19 posts held, back to 8 April 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
16.0%
avg views ÷ 325 subscribers
Avg views / post
52.0
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 19 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 6 August 2026
Posts held19 (8 April 20266 August 2026)
Views total52
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 07:16 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

5 reactions across 3 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 3 of the 19 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 5reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 8 April 2026 to 6 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

6 Aug 2026, 10:18 UTC52 viewsread 7 August 2026
Photo

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

10 Jul 2026, 07:43 UTC228 viewsread 7 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. 负责账户信息修改审核、邮件回复及相关

18 Jun 2026, 05:29 UTC364 viewsread 7 August 2026

推广学徒 30 人 薪资:1800-2000 U 工作时间:9小时月休8天(12点-21点) 年龄:25岁以下 工作地点:亚美尼亚 1. 有过一年以上综合/电子/体育/C票/棋牌等平台的代理招商或代理维护工作经验 2. 打字每分钟40,服从领导安排完成日常工作,学习常用推广手法,脚本运作! 3. 有效学习完成当日加群,炒群等基本工作 4. 善于包装自己,提高自我认知及善于沟通,情商高,心态积极,具备抗压能力。 5.有过自媒体,抖音,快手,小红书,发布视频,评论经验! 6.学习后可以独立完成推广,转化,发展代理日常工作!

18 Jun 2026, 05:25 UTC341 viewsread 7 August 2026

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

17 Jun 2026, 10:14 UTC306 viewsread 7 August 2026

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

21 May 2026, 01:54 UTC440 viewsread 7 August 2026
Photo

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

15 May 2026, 09:26 UTC414 views1 reactionsread 7 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群,电报群,论坛,贴吧等进行代理招商 4

1

13 May 2026, 00:56 UTC385 viewsread 7 August 2026
Photo

招聘专员 工作地点:亚美尼亚 上班时间:8小时,月休7-9 薪 资:面议 工作内容: 1、主要针对部门岗位需求做招聘 2、发布职位需求信息,做好公司形象宣传; 3、搜集简历,组织面试 4、组织相关人员协助完成复试工作,确保面试工作的及时开展及考核结果符合岗位要求; 5、负责招聘广告的撰写,招聘网站的维护和更新,以及招聘网站的信息沟通; 6、招聘费用的申请、控制和报销; 7、建立企业人才储备库,做好简历管理与信息保密工作; 8、其他交办事宜 岗位需求: 1、性别不限,国籍不限,学历不限,35岁以内 1年以上的招聘工作经验 2、高度责任心,较强的沟通协调能力及逻辑性; 3、高度抗压,有自己的招聘渠道

13 May 2026, 00:53 UTC326 viewsread 7 August 2026

区块链技术负责人 岗位职责: 负责区块链整体技术架构设计与演进; 主导高并发、高可用、高安全性的 Web3 系统建设; 负责公链 / Layer2 / 钱包 / 智能合约 / 节点服务等核心模块研发; 设计并优化链上数据服务、交易系统、风控系统及资产系统; 推动多链生态集成,包括 EVM、Solana、TON、Bitcoin 等; 负责智能合约安全、Gas 优化及链上性能优化 建立 DevOps、CI/CD、监控与自动化运维体系; 任职要求: 本科及以上学历,计算机相关专业优先; 8 年以上后端 / 分布式系统开发经验; 3 年以上区块链相关研发经验; 2 年以上团队管理经验(Manager / Director 级别需更强管理经验);

13 May 2026, 00:51 UTC334 views3 reactionsread 7 August 2026
Photo

🤩🤩🤩行业老牌龙头公司直招,欧洲火热招募中,9休8双休+法定假期 岗位多多 假期多多 餐补400P/天+房补20000P起/月🤩🤩🤩 HR:kay 职缺: 欧洲岗位:❤️ 职能: 招聘专员 薪资:面议 国籍不限,必须要有招聘经验 SVIP营销专员 薪资:2000U起 产品运营专员 薪资:3000U起 产品专员 薪资:4000-5000U 运营专员 薪资:2500U起 数据分析专员 薪资:2500-3000USD 人资主管 薪资面议 业绩岗位:❤️ SEO专员(新) 薪资:2000USD-4000USD 需要提供案例 推广专员 薪资:2000USD+高额提成 远程推广专员 薪资:1500-2300USD+高额提成 技术岗位:❤️ Linux系統運維工程師 薪资面议 运维工程师 薪资面议 测试工程师 薪资面议 塞尔维亚办公 产品专员(第三国) 薪资面议 塞尔维亚办公 在泰岗位:🥰 销售客服(泰国)

3

8 May 2026, 06:48 UTC297 viewsread 7 August 2026
Photo

🤩🤩🤩行业老牌龙头公司直招,欧洲火热招募中,菲律宾和泰国也有岗位,9休8双休+法定假期 岗位多多 假期多多 餐补400P/天+房补20000P起/月🤩🤩🤩 HR:kay 职缺: 在菲岗位:❤️ 职能: 人资专员 薪资:2000U起 菲华优先,可以接受小白 HRBP 薪资:面议 国籍不限,必须要有HRBP经验 法务专员 薪资:3000U起 产品运营专员 薪资:3000U起 产品专员 薪资:4000-5000U 运营专员 薪资:2500U起 审核风控专员 薪资:2100U起 财务BP 薪资:面议 数据分析专员 薪资:2500-3000USD 人资主管 薪资面议 业绩岗位:❤️ 销售客服 薪资:2100U+奖金,国籍不限 急招🐾 招商代理 薪资:1800USD起 SEO专员(新) 薪资:2000USD-4000USD 需要提供案例 SEO学徒 薪资:1800USD 远程推广专员 薪资:1500-2300US

Showing the 12 most recent of 19 posts we hold for @Kay202602. 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 — 678,378 of 1,151,006entries 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 3 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 7 August 2026 — this entry's latest reading, not the date you are reading this.

“集团招聘 直招” (@Kay202602), 325 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/Kay202602.

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.