Telegram RegisterThe public register of Telegram
Telegram profile photo for 欢迎收看打工人的日常➖搬砖人士聚集地

Channel

欢迎收看打工人的日常➖搬砖人士聚集地

@ITzhaopin001

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

1,313subscribers

+3 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001959616881
TypeChannel
Username@ITzhaopin001
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live19 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/ITzhaopin001

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

Growth

1,3031,3131,3087 August 2026 — 1,310 subscribers7 August 2026 — 1,310 subscribers11 August 2026 — 1,307 subscribers15 August 2026 — 1,309 subscribers17 August 2026 — 1,307 subscribers20 August 2026 — 1,305 subscribers30 August 2026 — 1,307 subscribers2 September 2026 — 1,303 subscribers6 September 2026 — 1,307 subscribers11 September 2026 — 1,309 subscribers14 September 2026 — 1,312 subscribers19 September 2026 — 1,313 subscribers7 August 202619 September 2026
12 measurements spanning 42 days, net +3. 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,302–1,315 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 06:361,313+1
14 Sept 2026, 09:551,312+3
11 Sept 2026, 05:161,309+2
6 Sept 2026, 03:191,307+4
2 Sept 2026, 00:231,303-4
30 Aug 2026, 05:131,307+2
20 Aug 2026, 23:481,305-2
17 Aug 2026, 20:161,307-2
15 Aug 2026, 01:381,309+2
11 Aug 2026, 20:321,307-3
7 Aug 2026, 22:321,310no change
7 Aug 2026, 18:531,310first reading

Engagement

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

Reaction mix

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

Measured over the 20 most recent posts we hold, published 15 June 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, 00:43 UTC210 viewsread 7 August 2026

📢📢📢以下岗位支持远程 • AIGC(远程/驻场) • 产品经理(远程/驻场)- 具备支付产品相关经验,熟悉 USDT 支付流程者优先 • 安卓逆向工程师(远程/驻场) 应聘方式:【简历 + 基本信息】发送至✈️ @HR0929

4 Aug 2026, 03:09 UTC270 views1 reactionsread 7 August 2026

产品工程师(本地) 不限国籍 工作地点:马来西亚(其他国家前期可以远程一个月) 薪资区间:20-33k 上班时间:09:30-18:30 周末双休 餐补 :420P-550P/天(依据当月天数) 房补 : 22000P/月 岗位职责: 1、 独立负责平台APP项目产品调研、功能规划、需求定义、开发、测试和上线的全流程, 2、 保证产品上线质量,把控产品体验,并跟进产品上线后的用户反馈和数据指标,持续进行分析、总结、优化; 3、 深度参与业务,收集运营、产品、客服等相关业务需求,梳理出清晰的业务流程,形成产品方案; 4、 以提升转化率和用户体验为目标,持续优化产品体验和探索产品的玩法。 任职要求: 1.3年以上互联网行业产品经验,需1年以上完整APP项目产品策划经验 2.有过AI产品经验的应用类等行业经验,熟悉彩票和体育包网类业务; 3.能够熟练运用Axure RP、Visio、MindManager等常用工具 4.有基础

1

3 Aug 2026, 06:59 UTC299 views1 reactionsread 7 August 2026

测试专员 不限国籍 工作地点:远程办公(中国大陆除外) 薪资区间:18-20k 上班时间:09:30-18:30 周末双休 餐补 :420P-550P/天(依据当月天数) 房补 : 17000p-22000P/月 岗位要求: 计算机相关专业学历背景 具备完整的软件测试经验,能够独立制定测试计划与测试流程 具备较强的问题分析能力,能够推动问题定位与解决 熟悉 Web / H5 产品测试流程,能够协调开发、产品推进项目进度 熟悉接口测试,能够使用浏览器 F12、Postman 等工具进行问题排查 具备良好的文档整理与测试报告输出能力 沟通协调能力强,逻辑清晰,有责任感 加分项: 喜欢体育 有彩票相关经验或兴趣 有带领测试团队经验优先 了解自动化测试、接口测试优先 工作内容: 负责产品整体测试流程与质量把控 制定测试方案、测试计划及测试规范 跟进项目测试进度,协调开发与产品沟通 负责线上问题排查、风险预警及版本验收 管理

1

3 Aug 2026, 06:48 UTC254 viewsread 7 August 2026

2026年8月招聘岗位: 日本🇯🇵技术岗位: 1、Rust工程师👨‍💻 2、Cocos前端工程师🧑‍💼 3、高级产品经理👨‍💻 4、高级测试工程师👩‍💻 5、运维工程师👨‍💻 日本🇯🇵其他岗位: 1、客服专员(台湾或马来西亚籍) 2、数据分析师(非中国籍) 3、产品调研专员(非中国籍) 4、人事主管(非中国籍) 其他非日本岗位: 1、视讯厅运营经理🧑‍💼 薪资:30~40k,非中国籍,中英文流利 2、现场值班客服 薪资:15~19k,非中国籍,中英文流利 基本要求:所有日本岗位🧮需具有全日制统招本科学历。 签证:日本岗位统一办理日本技术人文签证,公司缴纳雇佣保险+劳灾保险+社会健康保险+厚生年金,有兴趣的欢迎咨询。 应聘方式:【简历 + 基本信息】发送至✈️ @HR0929

2 Aug 2026, 12:59 UTC311 viewsread 7 August 2026

运营专员 有经营国内盘网站的经验 工作目标:不打广告的情况下,使用活动或是其他方式让网站营业数据提升 台湾籍女性或中国籍女性为主 可远程办公 年紀37以下 薪资20000~面议 应聘方式:【简历 + 基本信息】发送至✈️ @HR0929

29 Jul 2026, 03:53 UTC517 viewsread 7 August 2026

运维工程师 办公:马来西亚 薪资:25~35K 餐补:12600P 房补:22000-32000P 享受13薪,月休8天。 岗位职责: 1,负责跟进应用系统的立项评审、部署发布、监控、维护和优化; 2,负责应用系统的性能分析与架构优化,不断提高系统运行效率; 3,协调开发,测试,运维等各个团队,以更好的提高线上产品运行质量; 4,主动发现生产环境的问题和隐患,通过开发或推进自动化运维工操作的维护成本; 6,能够运用主机监控,日志分析,APM等工具进行复杂问题定位,参与到oncall值班轮转中,响应和处理7x24监控同学升级反馈的问题。 任职资格: 1,本科以上学历,计算机或者相关专业优先; 2,熟悉Linux系统,了解网络基本技术,熟悉TCP/IP协议工作原理,对Docker有深入研究者优先; 3,熟悉shell,熟悉python/perl/php脚本语言的一种以上;有面向对象开发经验者优先; 4,熟悉至少一种配置管理工

23 Jul 2026, 01:51 UTC641 viewsread 7 August 2026

🌸🌸🌸迪拜公司7月招聘如下: AI全栈开发工程师(Vue3 + Go) 薪资面议 AI研发架构师 (Vue3 + Go) 薪资面议 AI技术负责人(Go/Vue3)薪资面议 候选人需具备实际AI开发项目经验,面试过程中将进行AI辅助开发实操测试,仅了解AI工具但缺乏实际项目落地经验者不作为优先考虑对象 工作地点:阿联酋迪拜 薪资:具备竞争力薪资福利,具体面议。 应聘方式:【简历 + 基本信息】发送至✈️ @HR0929

21 Jul 2026, 08:52 UTC619 views0 reactionsread 7 August 2026

国内远程岗位来咯,抓紧投递!!! 🌿AIGC 🌿安卓逆向工程师 应聘方式:【简历 + 基本信息】发送至✈️ @HR0929

10 Jul 2026, 07:38 UTC858 views1 reactionsread 7 August 2026

产品经理(iGaming / SaaS) Remote(海外远程)|GMT+8|月休4天 职位介绍 我们正在寻找一位兼具产品思维与客户成功意识的产品经理,负责 iGaming SaaS 平台从产品交付、需求管理到持续迭代优化的全生命周期。 你将深入理解客户业务场景,推动产品落地,与研发、运营、客服等团队协作,不断提升平台能力与客户体验。 岗位职责 产品规划与需求管理 收集客户反馈、业务需求及市场信息,输出产品需求文档(PRD)。 梳理业务流程,分析痛点,持续推动产品优化与功能迭代。 将业务需求拆解为可执行方案,与研发团队沟通并推进落地。 跟踪产品版本开发进度,协调测试、验收及上线。 产品交付与客户成功 负责 SaaS 平台客户开站、配置、上线及交付流程。 协助客户快速完成产品接入,提高产品使用效率。 持续跟踪客户使用情况,推动产品价值落地,提高客户满意度。 建立并维护产品知识库、操作手册及培训文档。 跨部门协作 协调研发、运

1

10 Jul 2026, 05:49 UTC696 viewsread 7 August 2026

🍇🍇游戏后端开发工程师(老虎机 / 休闲游戏) base新加坡 薪资:4kU-7kU 9小时,双休,不包吃住,学历本科以上,优先要在新加坡有签证(或者已经在新加坡)的人选 ⭐️定位:主职开发老虎机与休闲游戏的后端服务(80%),兼做上线前代码审计与反套利排查(20%)。我们要的是资金和公平性上靠得住的后端——你写的服务直接经手玩家的钱和游戏结果,所以"能跑通"远远不够,每一行都要经得起"会不会被套利、会不会算错钱"的推敲。 应聘方式:【简历 + 基本信息】发送至✈️ @HR0929

6 Jul 2026, 06:10 UTC774 viewsread 7 August 2026

🍇亚美尼亚-测试 急招1位自动化测试(25-35岁) 能够使用AI自动化测试处理团队项目过程中的业务和数据工作 base:亚美尼亚 薪资:30-35K 应聘方式:【简历 + 基本信息】发送至✈️ @HR0929

30 Jun 2026, 07:02 UTC918 views1 reactionsread 7 August 2026

2026年7月岗位招聘 日本🇯🇵技术岗位: 1、Cocos前端工程师👨‍💻 2、高级产品经理🧑‍💼 3、Rust工程师👨‍💻 4、测试工程师👩‍💻 日本🇯🇵其他岗位: 1、客服专员(台湾或马来西亚籍) 2、数据分析师(非中国籍) 3、产品调研专员(非中国籍) 其他非日本岗位: 1、视讯厅运营经理🧑‍💼 薪资:30~40k,非中国籍,中英文流利 2、现场值班客服 薪资:15~19k,非中国籍,中英文流利 基本要求:技术岗位🧮需具有全日制统招本科学历,计算机相关专业。运营类💁‍♀️岗位需要有大学学历 签证:日本岗位统一办理日本技术人文签证,公司缴纳雇佣保险+劳灾保险+社会健康保险+厚生年金,有兴趣的欢迎咨询。 应聘方式:【简历 + 基本信息】发送至✈️ @HR0929

1

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

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.

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.

远程工作者
@remote_cn · 25,016
Telegram ranks this channel #51 of 85 here — alongside 84 others — read 15 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 19 September 2026 — this entry's latest reading, not the date you are reading this.

“欢迎收看打工人的日常➖搬砖人士聚集地” (@ITzhaopin001), 1,313 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/ITzhaopin001.

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.