频道适合看内容,群组更适合继续交流。 SOSO 可以直接找热门群组,也能按关键词搜同类圈子。 先打开看看当前推荐。

Channel
探花俱乐部招聘求职
@hrdny
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
24,421subscribers
-3,551 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001242361249 |
|---|---|
| Type | Channel |
| Usernames | @hr_cctv5 @hrdny |
| Description | #人事 #求职 #找工作 #迪拜 #泰国 #柬埔寨 #菲律宾 #斯里兰卡 #特区 #缅甸 信息发布: @qingqing678902 商务合作: @Gx181 |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/hrdny |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 18:53 | 24,421 | -464 |
| 14 Aug 2026, 17:53 | 24,885 | -46 |
| 14 Aug 2026, 10:17 | 24,931 | -932 |
| 13 Aug 2026, 10:09 | 25,863 | -261 |
| 12 Aug 2026, 23:34 | 26,124 | -158 |
| 12 Aug 2026, 10:47 | 26,282 | -126 |
| 11 Aug 2026, 22:42 | 26,408 | -241 |
| 11 Aug 2026, 09:37 | 26,649 | -309 |
| 10 Aug 2026, 19:13 | 26,958 | -93 |
| 10 Aug 2026, 09:10 | 27,051 | -342 |
| 9 Aug 2026, 16:22 | 27,393 | -143 |
| 9 Aug 2026, 07:53 | 27,536 | -402 |
| 8 Aug 2026, 12:43 | 27,938 | -34 |
| 8 Aug 2026, 11:20 | 27,972 | no change |
| 8 Aug 2026, 11:19 | 27,972 | first reading |
Engagement
72 posts held, back to 6 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 23 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 10.2%
- avg views ÷ 24,421 subscribers
- Avg views / post
- 2,490
- 72 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 72
- of 72 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.
| Window | Rolling 30 days · latest post in window 15 August 2026 |
|---|---|
| Posts held | 72 (6 August 2026 – 15 August 2026) |
| Views total | 179,189 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Aug 2026, 19:39 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
- 379
- Videos
- 238
- Links
- 885
Lifetime counters from Telegram’s own channel header, read 15 August 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.
Recent posts
真心做事 懂感恩 国内求职! 做过欧美精聊 合约 远控 色敲 车队🚗 现求国内 附近工作室 团队!!! 看上的盘总请带走 必发财💰感谢发布。 @xxx667899
真心做事 懂感恩 国内求职! 做过欧美精聊 合约 远控 色敲 车队🚗 现求国内 附近工作室 团队!!! 看上的盘总请带走 必发财💰感谢发布@xxx667899
@C8118S 求职:远程居家工作 29岁 本科,护照正常后期考虑到岗,现在台湾居住,有BC工作经验,成人传媒运营工作经验,有财务经验会做账有会计证,有博彩产品运营经验,有意老板联系 长白班
求职 人在妙瓦底 有一年多美股和欧美精聊经验 因公司解散 向平台寻找稳定待遇好的公司 有相同项目公司招聘的联系 @ldun139799
老师在帮忙发下 我在柬埔寨做过美日韩精聊快杀,三年带团队经验,从0到1所有流程都会,年初回国一直没做事情,目前想在国内找公司重新做业务,线上不做的,自己买票,全程线下靠谱公司和老板DD~ @qiu3303 🙏🏻
本人在柬埔寨寻找公司,做过资金盘,快杀,股票,半精聊,接受无底薪,高提成,踏实做事可以安排接的公司介绍一个工作中国人。 @dghe00000
求职SEO总监,9年工作经验,有海外国内0-1的经验精通shell,站群,寄生虫,二级目录,劫持,渗透手法,只做x 柬埔寨太子离职 找一家靠谱公司 亚博 勿扰 @ggpk008
13人8年稳定的技术团队 做过棋牌盘、交易所、电子盘等等项目,寻实力老板或公司,说话算数的来谈;柬埔寨 缅甸勿扰 技术栈:c++/java/go/lua/js/unity/cocos等 @mike1050tt
找国内工作室 本人5年精聊经验,懂感恩。只要能够提供好的资源,从来不担心业绩做不出来。 @aaca8233
之前在泰国做过精聊和资金盘 国内没有出路带着两个兄弟想出来 有护照 只去正规公司 工资待遇这些要求实事求是 什么都不怕,就怕没钱! @yykdd88
国内远程项目求职,国内工作室有好的项目都行。之前湾湾盘带过组,国内有虚拟货币打粉、交易所拉新经验。一心谋出路 希望各位老板给个机会 学习能力强 能吃苦 炮灰项目勿扰 ! @v01203
Showing the 12 most recent of 72 posts we hold for @hrdny. 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 — 937,298 of 1,480,688entries 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 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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“探花俱乐部招聘求职” (@hrdny), 24,421 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/hrdny.
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.