Telegram RegisterThe public register of Telegram
Telegram profile photo for 海外远程 -到岗技术招聘

Channel

海外远程 -到岗技术招聘

@HSDY1023

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

7,743subscribers

+2,326 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001833260645
TypeChannel
Username@HSDY1023
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 November 2026
Measurements held27
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/HSDY1023

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 13 September 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 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 2 other registered channels. This entry also forms a group of 2 channels linked by matching posts. 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
@warming111/35832 Nov 2026, 03:41 UTC@HSDY1023/3821 · this entry2 Nov 2026, 03:41 UTC1.00under a minute
@HSDY1023/3823 · this entry2 Nov 2026, 09:11 UTC@warming111/35852 Nov 2026, 09:17 UTC0.997 minutes
@HSDY1023/3395 · this entry10 Aug 2026, 10:03 UTC@warming111/315910 Aug 2026, 10:05 UTC0.972 minutes
@warming111/316512 Aug 2026, 03:05 UTC@HSDY1023/3401 · this entry12 Aug 2026, 03:09 UTC0.974 minutes
@HSDY1023/3819 · this entry2 Nov 2026, 02:40 UTC@warming111/35812 Nov 2026, 02:45 UTC0.966 minutes
@HSDY1023/3393 · this entry10 Aug 2026, 07:40 UTC@warming111/315710 Aug 2026, 07:41 UTC0.952 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
@warming11115 (8/8 hand-verifiable sample passed)0.952 minutesthis entry (8–7)
@huhulc5009 (8/8 hand-verifiable sample passed)0.9820 minutes@huhulc500 (7–2)

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. 13 of the 14 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 97 comparable posts for this entry, running 4 August 2026 to 16 November 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 2 channels, the one whose matching posts we hold earliest is @warming111. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual, last confirmed 17 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 2 registered channels linked by matching posts. 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

2,7627,7885,2757 August 2026 — 5,417 subscribers8 August 2026 — 5,420 subscribers11 August 2026 — 5,435 subscribers15 August 2026 — 5,446 subscribers18 August 2026 — 5,462 subscribers21 August 2026 — 5,484 subscribers24 August 2026 — 5,498 subscribers27 August 2026 — 5,507 subscribers30 August 2026 — 5,512 subscribers2 September 2026 — 5,510 subscribers7 September 2026 — 5,457 subscribers12 September 2026 — 5,438 subscribers15 September 2026 — 5,425 subscribers25 September 2026 — 3,708 subscribers4 October 2026 — 3,168 subscribers10 October 2026 — 2,841 subscribers14 October 2026 — 2,774 subscribers17 October 2026 — 2,762 subscribers20 October 2026 — 7,780 subscribers23 October 2026 — 7,788 subscribers26 October 2026 — 7,785 subscribers29 October 2026 — 7,781 subscribers1 November 2026 — 7,779 subscribers3 November 2026 — 7,776 subscribers6 November 2026 — 7,761 subscribers10 November 2026 — 7,751 subscribers15 November 2026 — 7,743 subscribers7,7437 August 202615 November 2026
27 measurements spanning 100 days, net +2,326. 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 2,008–8,542 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
15 Nov 2026, 22:567,743-8
10 Nov 2026, 10:007,751-10
6 Nov 2026, 23:377,761-15
3 Nov 2026, 15:277,776-3
1 Nov 2026, 00:107,779-2
29 Oct 2026, 10:497,781-4
26 Oct 2026, 09:497,785-3
23 Oct 2026, 12:547,788+8
20 Oct 2026, 06:487,780+5,018
17 Oct 2026, 04:182,762-12
14 Oct 2026, 10:002,774-67
10 Oct 2026, 15:142,841-327
4 Oct 2026, 21:593,168-540
25 Sept 2026, 04:213,708-1,717
15 Sept 2026, 10:425,425-13
12 Sept 2026, 05:025,438-19
7 Sept 2026, 16:575,457-53
2 Sept 2026, 08:445,510-2
30 Aug 2026, 09:585,512+5
27 Aug 2026, 08:475,507first reading

Engagement

111 posts held, back to 4 August 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 35 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.57%
avg views ÷ 7,743 subscribers
Avg views / post
277
76 posts measured
Reaction rate
0.244%
reactions ÷ views · ER floor
Posts in window
76
of 111 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 14 of 76 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 17 November 2026
Posts held111 (4 August 2026 – 17 November 2026)
Views total21,017
Reactions total10
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 06:57 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.

What this channel posts

Photos
22
Links
316

Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

12 reactions across 12 posts, in 1 kind.

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

Measured over the 111 most recent posts we hold, published 4 August 2026 to 17 November 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

Telegram’s own ‘edited’ marker: 6 of 76 posts held from the last 30 days (7.89%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

17 Nov 2026, 03:19 UTC120 viewsread 17 November 2026

❗️❗️❗️❗️❗️❗️❗️ 远程更新 必须本科学历 ✅职位:产品经理(远程 -可国内远程) ✅薪资:20-30k 单休 ✅要求:不限制包网行业经验,首选有支付经验(USDT) 和 AI 产品相关经验 💥💥💥💥💥💥媛媛

17 Nov 2026, 03:08 UTC129 viewsread 17 November 2026

❤️ 技术总监/java技术专家 ❤️ 💰 薪资:8000~10000 USDT 🌍 国籍:不限 🎓 学历:需具有全日制统招本科学历 ⏰ 上班时间:8 小时,周休 1 日 🔥 地点:日本东京周边 🍐 岗位职责 🍐 • 支付系统前瞻性技术储备,负责规划技术路线,制定产品技术方案; • 负责系统性能、可用性、扩展性、安全性、伸缩性等做系统级的把握; • 负责技术难点攻关,核心技术研究和攻关工作,解决各类技术难题或问题; • 参与过企业大型应用系统群的集成技术架构设计、大型海量系统的技术架构设计。 • 负责搭建技术框架,核心功能的架构与代码模板编写。 • 参与部门技术路线规划,新技术的探索研究,并落地应用到具体产品中,同时组织内部技术分享; • 负责技术部门团队管理。 🦆 任职要求 🦆 • 统招本科及以上学历,计算机相关专业 • 10年以上Java开发经验,熟练掌握多线程等基础类库,熟悉分布式缓存等技术 • 5年以上互联网行业架构…

17 Nov 2026, 03:05 UTC121 viewsread 17 November 2026

❗️❗️❗️❗️❗️❗️❗️ 到岗 #本科学历 #日本大阪岗位: ✅产品经理(区块链金融方向) ✅外籍游戏数据分析师 ✅外籍客服专员 ✅资深 Golang 后端工程师(Web3方向) ✅高级测试开发工程师 (区块链钱包方向) #东京周边 ✅Rust工程师 ✅区块链与直播系统运维工程师 ✅外籍人资行政专员 ✅外籍技术客服 福利 🔥年假:每年15天+机票,未使用可换补贴 🔥餐食:供餐+餐补 🔥住宿:提供宿舍1人或2人一间 🔥签证:公司统一办理日本『技术人文国际』签证 🔥税金:由公司全額承擔 (雇佣保险+劳灾保险+社会健康保险+厚生年金) 🔥其他福利:每月团建、生日礼金、四节红包、春节加倍工资、饮料水果、生活用品、日本手机话费补贴… 签证资格:需具有全日制统招本科学历 簽證優勢:可申请家属随行,享有与日本居民相同的居留、教育、医疗与社会福利 💥💥💥💥💥💥媛媛

17 Nov 2026, 03:03 UTC111 viewsread 17 November 2026

❗️❗️❗️❗️❗️❗️❗️ 亚美尼亚到岗 支付项目|9小時週休一 ✅资深运维工程师(支付钱包方向) ✅资深前端工程师 (支付钱包方向) ✅资深 Java(支付钱包方向) 💥💥💥💥💥💥

17 Nov 2026, 03:02 UTC117 viewsread 17 November 2026

❗️❗️❗️❗️❗️❗️❗️ 菲律宾makati居家办公 提供房补餐补 薪资40-60k ✅C++工程师 任职要求 •扎实的 C/C++ 开发能力,有实际项目经验。 • 熟悉 OpenCV,具备一定图像处理、计算机视觉及算法基础。 • 熟练使用 Python,能够进行AI、算法及自动化开发。 • 有硬件 SDK/API、TCP/UDP、串口等对接经验。 • 有 AI大模型、OCR、二维码/扫码、视觉识别 项目经验。 • 熟悉 Qt/MFC/其他C++桌面开发框架 者优先。 • 具备较强的学习能力、独立解决问题能力及一定抗压能力。 💥💥💥💥💥💥媛媛

16 Nov 2026, 03:53 UTC233 views1 reactionsread 17 November 2026

❗️❗️❗️❗️❗️❗️❗️ 新增海外远程 ✅产品交付(iGaming / SaaS) 远程 | 每周休一天 | 提供年假 | 需人在海外 工作方式 海外远程办公,地点不限 (候选人目前不得在中国大陆境内工作) 工作时间 以 GMT+8 时间为准,每周休一天,提供年假,产品重大上线、版本发布及紧急事故需配合支援 薪资范围 20K – 25K / 月,根据能力与经验面议 面试流程 一般为两轮面试,重要岗位可安排三轮 ✅海外 Cocos 游戏工程师 远程 | 周休一日 | 提供年假 | 需人在海外 工作方式 海外远程办公,地点不限 (候选人目前不得在中国大陆境内工作) 工作时间 以 GMT+8 时间为准,周休二日,提供年假 薪资范围 [币种] 25K – 45K / 月,依能力与经验面议 面试流程 一般为两轮面试,重要职位可安排三轮 其他福利 依公司福利制度办理 ✅Go 后端开发工程师 远程 | …

❤1

14 Nov 2026, 05:13 UTC299 viewsread 17 November 2026

❗️❗️❗️❗️❗️❗️❗️ 岗位: java 高级开发工程师 薪资:30K-50K(具体面议) 年龄:35岁(优秀可以放宽) 性别: 男 国籍: 中国籍,会中文 上班时间 :面议 上班地址:泰 岗位职责: 1. 完成核心和主要业务的需求分析、任务的评估拆解和梳理、技术方案设计、编码实现。 2. 参与需求评审、测试用例评审,跟踪任务迭代计划确保程序能按时按质的交付上线。 3. 负责代码的Review控制代码质量,以及确保技术的实现细节符合既定的技术方案和技术标准。 4. 参与技术难点攻关。 5. 技术培训,提升团队整体的技术水平。 6. 人员的招聘和面试,为公司寻觅人才。 任职要求: 1. Java基础扎实,熟悉各类JSR规范,掌握基本的Java多线程编程,了解JVM原理,具备一定的调优能力 2. 能熟练使用各种开源框架,如:spring全家桶、dubble、mybatis、jpa等等 3. 熟练掌握各种开发用到的工…

14 Nov 2026, 03:37 UTC291 viewsread 17 November 2026

❗️❗️❗️❗️❗️❗️❗️ 工作地点:斯里兰卡(现场办公) ✅工作时间:9小时/天(含1小时用餐) ✅月休:6天 ✅投递需知:看清楚每个职位的国籍要求 🩶🩶🩶🩶🩶🩶🩶🩶🩶🩶🩶🩶 ✅推广经理 ✅国籍要求:香港、台湾、马来西亚及其他国籍华侨 ✅薪资待遇:面议 + 绩效奖金(常见薪资范围 4,000 U 起) 🩶🩶🩶🩶🩶 ✅总经理秘书 / 生活助理 ✅招聘对象:仅限女性 ✅国籍要求:台湾、马来西亚及其他国籍华侨(除大陆籍) ✅薪资待遇:面议(参考范围 2,000–3,000 U) 🩶🩶🩶🩶🩶 ✅财务专员 ✅国籍要求:台湾、马来西亚及其他国籍华侨(除大陆籍) ✅薪资待遇:面议 🩶🩶🩶🩶🩶 ✅泰国市场行销主管 ✅工作模式:远端办公(WFH) ✅国籍要求:不限 ✅语言要求:精通泰文,另需具备良好的中文或英文能力 ✅薪资待遇:面议 🩶🩶🩶🩶🩶 ✅泰国市场助理 ✅国籍要求:不限(除大陆籍) ✅语言要求:精通泰文,…

14 Nov 2026, 03:33 UTC198 viewsread 17 November 2026

❗️❗️❗️❗️❗️❗️❗️ ✅工作地点:越南胡志明到岗 ✅职位:测试 ✅薪资:30-36k 单休 岗位要求: 1.计算机、网络工程、软件等大专以上学历或同等资历 2.3年以上相应工作经验 3.有必要的测试相关理论知识:软件工程、测试类别、测试方法… 4.掌握测试用例编写 5.掌握基于web,android和iOS的终端测试方法:功能和界面 6.掌握后端微服务系统的测试 7.掌握devops下相关的测试方式和方法 8.掌握性能测试的方法 9.敏捷经验 10.熟悉容量测试和压力测试佳 11.熟悉自动化脚本编写佳 12.掌握灰度测试方法者佳 13.掌握自动化测试系统搭建甚佳 🙂不压护照-包食宿 🙂上班时间:8:00-18:30 单休 午休1.5h 🙂其他福利:满半年15天带薪年假,满一年13薪,半年还有5%的返岗绩效,吃住全包 💥💥💥💥💥💥媛媛

14 Nov 2026, 03:32 UTC183 views1 reactionsread 17 November 2026

❗️❗️❗️❗️❗️❗️❗️ ✅薪资:30-50k ✅地点:台北办公室 ✅投递需知:只要台湾籍 ✅Golang 后端游戏 【职务需求】 1. 具备 Go 语言基础,了解基本语法、Package Management 及常见的开发与除错方式 2. 具备基本软件设计概念,能将业务逻辑适当模块化,理解接口抽象、依赖注入与解耦等原则 3. 能撰写结构清楚、易于维护的程序代码,并具备基本测试观念 4. 认同「开发即观测(Observability by Design)」的工程思维,能在功能开发时同步规划 Logging、Metrics、Tracing 与问题排查机制 5. 具备将 AI 助理融入日常开发流程的实务经验,或对此抱持高度学习意愿,例如: ・使用 AI 工具协助程序代码生成、Debug、测试、重构或 Code Review ・能清楚描述需求、补充上下文,并透过有效 Prompt 与 AI agen…

❤1

14 Nov 2026, 03:31 UTC163 views1 reactionsread 17 November 2026

❗️❗️❗️❗️❗️❗️❗️ DBA数据分析资料库 工作型态:马来到岗 性别:不限 国籍:不限(华人优先) 时间:弹性(配合公司工作职责) 试用:30000RMB 转正:35000RMB 一、 职位目标 负责公司核心数据库的架构设计、性能优化及数据分析支持,确保数据底层架构的高可用性,并为业务决策提供精准的数据基础。 二、 核心职责 1. 架构设计: 规划数据库物理结构、分表分库策略,确保系统具备扩展性。 2. 效能优化: 负责索引优化、SQL 语句审核及缓存机制,解决高并发下的延迟问题。 3. 分析支持: 协助构建数据仓库(Data Warehouse)或数据看板,自动化产出业务分析报表。 4. 运维保障: 执行数据备份、恢复演练及异地灾备,确保 24/7 数据安全不丢失。 三、 任职要求 • 技术功底: 精通 MySQL、PostgreSQL 或 MongoDB 等主流数据库(至少一项)。 • 实战经验: 2 年…

❤1

14 Nov 2026, 03:29 UTC152 viewsread 17 November 2026

❗️❗️❗️❗️❗️❗️❗️ 【客服质检】 10-12K 📱马来新山 岗位职责: 1. 负责客服团队服务质量监控与评估,定期输出质检报告 2. 制定和优化客服质检标准,确保服务符合公司要求 3. 分析客服沟通问题,提出优化建议,向管理层反馈质量情况 4. 协助培训部门制定培训与改进计划,提升整体服务能力 5. 分析客户投诉与应对处理方式,提出流程或话术优化方案 6. 组织客服质检回顾会议,关注人员成长与服务表现改进 任职要求: 1年以上客服质检或客服管理经验者优先 3. 熟悉客服质检流程,能独立建立质检标准体系 4. 注重细节,具备良好的数据分析与问题解决能力 5. 熟练掌握 Excel、Word 等办公软件,能独立撰写质检报告 6. 良好的团队协作意识与沟通能力,能配合培训部门工作推进 💥💥💥💥💥💥

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

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

DeJob—Web3招聘求职频道📮
@DeJob_official · 48,023
Telegram ranks this channel #40 of 94 here — alongside 93 others — read 27 August 2026
TG招聘|求职|人才聚集地✳️
@XCRLZP · 104,460
Telegram ranks this channel #62 of 82 here — alongside 81 others — read 13 August 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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.

“海外远程 -到岗技术招聘” (@HSDY1023), 7,743 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/HSDY1023.

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.