Telegram RegisterThe public register of Telegram
Telegram profile photo for 🚗《招聘求职-柬埔寨东南亚吃瓜》

Channel

🚗《招聘求职-柬埔寨东南亚吃瓜》

@zii33

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

101,892subscribers

-3,384 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1001551033719
TypeChannel
Username@zii33
Description#招聘 #求职 #找工作 #甩人 #曝光 #新闻 #迪拜求职 #迪拜 #柬埔寨 #菲律宾 #泰国 🔍曝光新闻: @qqt13 🔍求职招聘: @zii33 🔍国内吃瓜: @aii88 💁投放广告请联系: @RMB800 💁账号被限制请联系双向机器人: @rmb900_bot
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live6 November 2026
Measurements held60
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/zii33

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 10 August 2026 and assigned it the closest of 31 fixed categories, at 99% 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 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
@qiuzhi99/375327 Aug 2026, 07:01 UTC@zii33/38241 · this entry7 Aug 2026, 07:01 UTC1.00under a minute
@qiuzhi99/375347 Aug 2026, 07:55 UTC@zii33/38244 · this entry7 Aug 2026, 07:55 UTC1.00under a minute
@qiuzhi99/375377 Aug 2026, 08:46 UTC@zii33/38247 · this entry7 Aug 2026, 08:46 UTC1.00under a minute
@zii33/38251 · this entry7 Aug 2026, 09:45 UTC@qiuzhi99/375417 Aug 2026, 09:45 UTC1.00under a minute
@qiuzhi99/375447 Aug 2026, 10:03 UTC@zii33/38252 · this entry7 Aug 2026, 10:03 UTC1.00under a minute
@qiuzhi99/375457 Aug 2026, 10:11 UTC@zii33/38253 · this entry7 Aug 2026, 10:11 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@qiuzhi997 (7/7 hand-verifiable sample passed)1.00under a minutethis entry (7–0)

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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 11 comparable posts for this entry, running 7 August 2026 to 7 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 @qiuzhi99. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, 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

95,773106,759101,2667 August 2026 — 105,276 subscribers7 August 2026 — 104,979 subscribers8 August 2026 — 103,301 subscribers10 August 2026 — 102,057 subscribers11 August 2026 — 100,717 subscribers12 August 2026 — 99,433 subscribers13 August 2026 — 98,696 subscribers14 August 2026 — 97,705 subscribers15 August 2026 — 96,291 subscribers17 August 2026 — 104,024 subscribers18 August 2026 — 102,889 subscribers19 August 2026 — 101,805 subscribers20 August 2026 — 100,905 subscribers21 August 2026 — 99,725 subscribers22 August 2026 — 98,239 subscribers23 August 2026 — 106,759 subscribers25 August 2026 — 105,451 subscribers26 August 2026 — 103,954 subscribers27 August 2026 — 103,222 subscribers28 August 2026 — 102,129 subscribers29 August 2026 — 100,082 subscribers30 August 2026 — 98,186 subscribers31 August 2026 — 97,459 subscribers1 September 2026 — 104,526 subscribers2 September 2026 — 102,889 subscribers3 September 2026 — 101,737 subscribers5 September 2026 — 103,640 subscribers9 September 2026 — 99,051 subscribers11 September 2026 — 105,183 subscribers13 September 2026 — 101,654 subscribers15 September 2026 — 99,573 subscribers16 September 2026 — 104,366 subscribers19 September 2026 — 105,071 subscribers26 September 2026 — 99,421 subscribers4 October 2026 — 99,862 subscribers8 October 2026 — 99,911 subscribers13 October 2026 — 99,340 subscribers14 October 2026 — 102,111 subscribers15 October 2026 — 100,839 subscribers16 October 2026 — 100,074 subscribers17 October 2026 — 104,697 subscribers18 October 2026 — 104,056 subscribers19 October 2026 — 102,770 subscribers20 October 2026 — 101,176 subscribers21 October 2026 — 105,028 subscribers22 October 2026 — 103,314 subscribers23 October 2026 — 101,867 subscribers24 October 2026 — 100,399 subscribers25 October 2026 — 99,454 subscribers26 October 2026 — 97,651 subscribers27 October 2026 — 96,587 subscribers29 October 2026 — 95,773 subscribers29 October 2026 — 102,535 subscribers31 October 2026 — 100,628 subscribers31 October 2026 — 99,918 subscribers1 November 2026 — 102,017 subscribers3 November 2026 — 103,781 subscribers4 November 2026 — 103,110 subscribers5 November 2026 — 102,773 subscribers6 November 2026 — 101,892 subscribers101,8927 August 20266 November 2026
60 measurements spanning 91 days, net -3,384. 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 94,125–108,407 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 60
Measured (UTC)SubscribersChange
6 Nov 2026, 04:06101,892-881
5 Nov 2026, 00:09102,773-337
4 Nov 2026, 01:39103,110-671
3 Nov 2026, 01:00103,781+1,764
1 Nov 2026, 21:47102,017+2,099
31 Oct 2026, 22:2199,918-710
31 Oct 2026, 00:05100,628-1,907
29 Oct 2026, 23:06102,535+6,762
29 Oct 2026, 00:1895,773-814
27 Oct 2026, 23:5696,587-1,064
26 Oct 2026, 21:2197,651-1,803
25 Oct 2026, 23:1699,454-945
24 Oct 2026, 22:44100,399-1,468
23 Oct 2026, 21:36101,867-1,447
22 Oct 2026, 23:58103,314-1,714
21 Oct 2026, 20:29105,028+3,852
20 Oct 2026, 14:45101,176-1,594
19 Oct 2026, 16:16102,770-1,286
18 Oct 2026, 15:28104,056-641
17 Oct 2026, 16:07104,697first reading

Engagement

2,401 posts held, back to 7 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 186 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.75%
avg views ÷ 101,892 subscribers
Avg views / post
2,810
863 posts measured
Reaction rate
0.043%
reactions ÷ views · ER floor
Posts in window
867
of 2,401 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 15 of 863 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 6 November 2026
Posts held2,401 (7 August 2026 – 6 November 2026)
Views total2,421,252
Reactions total13
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 06:17 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
≈15,100
Videos
≈1,900
Links
≈13,600

Lifetime counters from Telegram’s own channel header, read 6 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
45m 22s
Average length
43s

Measured directly from 63 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

14 reactions across 13 posts, in 4 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍750.0%
❤535.7%
💩17.14%
😁17.14%

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 16 of the 1,000 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 14 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 1 October 2026 to 6 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: 0 of 867 posts held from the last 30 days (0%) 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).

6 Nov 2026, 06:03 UTC≈1,280 viewsread 6 November 2026
Photo

😀😀😀😀😀😀😀😀😀😀😀😀😀 😀【7T.COM】全球公认最稳! 😀😀😀😀😀😀😀😀😀😀 😀380亿U出款见证,持续为用户提供稳定可靠体验 😀😀😀😀😀😀😀😀😀😀 😀行业领先出款效率,58秒见证极速服务体验。 😀😀😀😀😀😀😀😀😀😀😀😀 持续稳定增长,都是各位老板的信任见证。 😀😀😀😀😀😀😀😀😀😀😀 实力积累,赢得行业各老板的认可。 😀😀😀😀😀😀😀😀😀😀 每月千万美金投入,致力打造行业品牌标杆。 😀😀😀😀:【7T.COM】 😀😀😀😀:【官方飞投】 😀😀😀😀:【@uuu7t】 😀😀😀😀😀😀😀😀😀😀😀

6 Nov 2026, 05:10 UTC≈2,270 viewsread 6 November 2026
Video

你好 想出去上班 帮忙发一下可以吧 有护照 人在国内 做事靠谱 不墨迹 有过敲键盘工作 有招人的公司可以联系 @deng888dai

6 Nov 2026, 05:10 UTC≈2,220 viewsread 6 November 2026
Video

你好,可以帮我发一个帖子吗,落难了有护照之前在国内朋友工作室做过日韩商城转股这些,想去国外闯几年,有缺人的联系 @canshenji

6 Nov 2026, 04:41 UTC≈2,980 viewsread 6 November 2026
Video

想出国做事,有护照,脑子灵活 ,博彩不做 勿扰。 有需要的大哥可以联系 @yswz6889

6 Nov 2026, 04:41 UTC≈3,180 viewsread 6 November 2026
Video

你好,发布一下,有需要外籍员工 话务 模特 翻译 马来西亚女翻译 联系我 @zypp6688

6 Nov 2026, 03:31 UTC≈3,280 viewsread 6 November 2026
Video

人在马来做过资金盘,精聊,,有没有靠谱的公司需要人的联系我,@HYJsjdhh

6 Nov 2026, 03:31 UTC≈3,490 viewsread 6 November 2026
Video

求职找事做!人在广州着急出去做事,护照港澳通行证都齐全,🉑随时出发,国内有好项目的工作室也🉑联系 @man18509

6 Nov 2026, 02:21 UTC≈2,340 viewsread 6 November 2026
Video

人在国内,除了技术岗基本上都没行,有老板需要的联系 @kesuu008

6 Nov 2026, 02:21 UTC≈1,480 viewsread 6 November 2026
Video

台湾女 求职 行政 翻译 后勤助理 人在马来 护照在手随时飞 直接发公司地址 岗位和待遇 非诚勿扰 @wml996

6 Nov 2026, 01:10 UTC≈2,930 viewsread 6 November 2026
Video

人在国内,出不去中国,想找份合适的工作,骗子绕道。菠菜,财务,客服,股转,刷单,都做过。最高业绩月一千万,如果有老板看得上,可以私聊 @hxl1995

6 Nov 2026, 01:10 UTC≈2,930 viewsread 6 November 2026
Video

6个中国人在秒瓦底,现急找能长期做下去的公司上班,能接的联系✈️ @bxnzn6764 做欧美精聊的 ,

5 Nov 2026, 22:10 UTC≈3,950 viewsread 6 November 2026
Photo

新群变化快,手动找很容易漏。 SOSO 会展示最近同步的新群入口,适合快速补充新的群组来源。 🔗 本频道专属邀请链接 https://t.me/sosoo?start=autopromo_-1001551033719_7214222580_newgroups_d75922b9

Showing the 12 most recent of 2,401 posts we hold for @zii33. 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.

Posts recorded as deleted after publishing

We recorded 1 post on @zii33 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
20 September 2026
Most recent seen missing
20 September 2026
Median time before seen missing
27 hours
Seen missing in the last 30 days
0

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

🇵🇭菲行者:求职招聘
@feixingzhe_qzzz · 626,084
#1
东南亚求职跳槽 🔰
@tiaocao · 12,703
#2
东南亚安危曝光
@DNYZPH · 22,687
#3
迪拜求职招聘
@dibai2025 · 306,003
#4
求职招聘频道
@DBZPH · 48,645
#5
📢【BOSS直聘】求职|招聘
@qiuzhi008 · 234,885
#6
东南亚求职🙋‍♀️《东南亚找工作》海外求职
@cii77 · 13,453
#7
🇦🇪迪拜求职招聘
@dibaidddd · 112,178
#8
《斯里兰卡求职》◒泰国代理&缅甸招聘
@xii34 · 102,536
#9
菲律宾找工作🇵🇭《菲律宾求职》国外招聘
@zhaogongzuo9 · 13,291
#10
柬埔寨招聘●柬埔寨找工作●招聘频道
@zhaopin44 · 14,223
#11
🇦🇪迪拜:求职招聘
@dubaiuuu · 87,674
#12
⚔️吃瓜曝光《缅北缅甸泰国》
@qqt13 · 199,609
#13
人才网求职中心
@qiuzhi69 · 7,841
#14
菲柬迪泰求职中心
@quanqiuqiuzhi · 1,589
#15
迪拜 东南亚求职招聘
@Dubaiqzzp · 90,444
#16
安危.招聘.求职.找工作
@uozzo · 15,753
#17
东南亚|求职|人才【博牛招聘】
@bnzpgf · 2,460
#18
BOSS直聘|招聘|求职|工作🕵️‍♂️
@hr10060 · 25,452
#19
迪拜大事件|迪拜新闻|Dubai生活资讯攻略
@dubai0 · 89,041
#20
招聘求职频道 @ur866
@jpzqzpd · 7,264
#21
头条事件
@toutiaoshijian · 66,820
#22
TG招聘|求职|人才聚集地✳️
@XCRLZP · 95,473
#23
吃瓜搞笑视频🤡
@DNYQZZP · 57,443
#24
海外求职招聘
@zhaopin666999 · 2,329
#25
《柬埔寨找工作》柬埔寨招聘|柬埔寨甩人
@xii62 · 28,453
#26
求职招聘🔮东南亚全球中东欧洲亚洲
@kq666666 · 7,248
#27
缅甸 泰国 金三角特区求职频道
@mktxxyl · 7,724
#28
华人资讯【求职&招聘】
@Huaren_zhaopin_qiuzhi · 1,074
#29
迪拜 东南亚求职招聘甩人
@qiuzhi0999 · 47,471
#30
全网求职甩人频道
@QQT601 · 1,773
#31
全球曝光求职
@AirdropVerifieSdss · 58,373
#32
东南亚大事件 @svip
@bx666 · 462,518
#33
菲律宾华人事件
@svip40 · 131,769
#34
🇸🇽菲岛【求职甩人】
@FJD926 · 1,616
#35
51找工作/招聘
@tghrzx · 2,579
#36
中亚体育综合盘总部直招频道
@hrfenda · 766
#37
招聘求职信息发布
@ZhaopinQiuzhi01 · 1,137
#38
菲龙网新闻中文媒体【官方】
@feilongwang · 70,953
#39
海外IT技术远程/到岗招聘
@huhulc500 · 6,247
#40
海外IT技术招聘群
@PAZP7 · 5,534
#41
🌎菲律宾招聘平台|招聘|找工作|求职
@zhaopin19955 · 471
#42
招聘求职频道 @ur866
@zhaopine · 7,258
#43
海外IT技术招聘群
@siss67888 · 6,438
#44
《🙋‍♀️柬埔寨吃瓜》每日吃瓜 |吃瓜频道
@aii88 · 10,574
#45
柬埔寨新闻《柬埔寨曝光》
@sii76 · 202,023
#46
菲柬迪求职频道
@qiuzhi2023 · 390
#47
🇦🇪 Henry Tan |迪拜招聘
@overseasrecruiterhenrytan · 587
#48
菲律宾新闻大事件
@flb608 · 70,950
#49
技术全球招聘求职中心
@xiaobeivvdd · 2,466
#50
菲律宾大事件|菲律宾新闻|The Philippines生活资讯
@flb00 · 16,643
#51
🔥多个国家月休8天工作交流(每周更新)
@shuangxiugognzuo · 7,007
#52
海外项目技术招聘
@Bf36998 · 2,636
#53
尊龙凯时市场部直招 🇹🇭 @SekaiTopjob🌈
@TopSekai · 2,877
#54
Ginnie 海外技術工作 日本🇯🇵泰國🇹🇭越南🇻🇳馬來🇲🇾...
@philippingwork · 3,987
#55
欢欢欢欢乐乐乐乐
@sus_hhll · 4,952
#56
迪拜求职招聘工作Dubai Job
@DubaiJob5566 · 829
#57
海外技术招聘/远程/驻场/🌱
@HHJason123 · 8,969
#58
海外技术招聘服务热线频道
@YZFC1699 · 1,148
#59
🌏迪拜新闻曝光-安危头条🇦🇪迪拜通🔥
@dibaiTT · 160,971
#60
海外IT技术招聘|海外程序员工作
@haiwaiIt · 6,544
#61
远程工作招聘频道
@aerfahc1 · 16,577
#62
海外远程/到岗技术招聘
@keepondoing888 · 4,636
#63
依依 海外求职招聘 IT技术 jobs👉🏼
@ferm_yiyi · 6,974
#64
海外技术远程/驻场/招聘群
@YCSL588 · 7,210
#65
iGaming 華人技術招聘 | 迪拜 塞爾維亞 新加坡 遠端 Golang Cocos 運維大盤
@Jerryleung030 · 1,436
#66
🌏迪拜求职招聘🇦🇪迪拜通🔥
@dibaiSB · 34,905
#67
💻东南亚靠谱招聘HR资源🖥
@mdjc6 · 259
#68
迪拜黑料大曝光
@kk4568 · 107,332
#69
博聘优选™国际猎头|求职|招聘|人才聚集地|圈子最专业的招聘频道
@bopinfabu · 3,567
#70
DDG-求职群
@DMCCrc · 242
#71
远程/到岗技术招聘求职IT群
@warming111 · 6,083
#72
海外工作-(技术/职能岗)
@OBstarshine · 5,567
#73
全球求职---招聘频道 🌏👇👇👇
@juan886007 · 1,328
#74
人才.ph - 全球精英人才聚集地
@rencaiphchannel · 581
#75
NexTech招聘官方频道🇦🇪
@nextech666 · 1,620
#76
👋🏻 求职频道
@skljjhjnn · 2,858
#77
迪拜招聘【国外工作】东南亚招聘
@shuairen6 · 888
#78

Read from Telegram’s recommendation API, most recently 16 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

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.

《斯里兰卡求职》◒泰国代理&缅甸招聘
@xii34 · 102,536
Telegram ranks this channel #1 of 69 here — alongside 68 others — read 15 August 2026
⚔️吃瓜曝光《缅北缅甸泰国》
@qqt13 · 199,609
Telegram ranks this channel #5 of 75 here — alongside 74 others — read 11 August 2026
📢【BOSS直聘】求职|招聘
@qiuzhi008 · 234,885
Telegram ranks this channel #5 of 72 here — alongside 71 others — read 11 August 2026
求职招聘
@qzzpfabu888 · 607,992
Telegram ranks this channel #5 of 72 here — alongside 71 others — read 9 August 2026
🇵🇭菲行者:求职招聘
@feixingzhe_qzzz · 626,084
Telegram ranks this channel #5 of 67 here — alongside 66 others — read 9 August 2026
迪拜 东南亚求职招聘
@Dubaiqzzp · 90,444
Telegram ranks this channel #6 of 64 here — alongside 63 others — read 17 August 2026
🇦🇪迪拜:求职招聘
@dubaiuuu · 87,674
Telegram ranks this channel #6 of 67 here — alongside 66 others — read 17 August 2026
迪拜求职招聘
@dibai2025 · 306,003
Telegram ranks this channel #6 of 74 here — alongside 73 others — read 10 August 2026
求职招聘频道
@DBZPH · 48,645
Telegram ranks this channel #7 of 46 here — alongside 45 others — read 25 August 2026
🇦🇪迪拜求职招聘
@dibaidddd · 112,178
Telegram ranks this channel #7 of 70 here — alongside 69 others — read 13 August 2026
亚太求职/甩人/找工作
@YTT789 · 296,322
Telegram ranks this channel #7 of 68 here — alongside 67 others — read 10 August 2026
TG招聘|求职|人才聚集地✳️
@XCRLZP · 95,473
Telegram ranks this channel #10 of 82 here — alongside 81 others — read 13 August 2026
🇵🇭菲行者:吃瓜中心
@feixingzhe_cgzx · 151,870
Telegram ranks this channel #39 of 63 here — alongside 62 others — read 12 August 2026
泰国大事件|全球大事件曝光 悬赏
@xinwen0888 · 79,499
Telegram ranks this channel #42 of 70 here — alongside 69 others — read 17 August 2026
东南亚黑暗事件
@aq7777 · 50,474
Telegram ranks this channel #43 of 64 here — alongside 63 others — read 23 August 2026
菲律宾新闻大事件
@flb608 · 70,950
Telegram ranks this channel #44 of 80 here — alongside 79 others — read 14 August 2026

This channel appears in 16 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 6 November 2026 — this entry's latest reading, not the date you are reading this.

“🚗《招聘求职-柬埔寨东南亚吃瓜》” (@zii33), 101,892 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/zii33.

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.