求职:人现在在柬埔寨 做过股转和欧美精聊日韩商城 会整套操作流程 现在公司停工解散状态 想向稳定待遇好的公司求职 只做杀盘 不做体育之类的项目 勿扰 @ldodd139
🔥22😍17👍15

Channel
@feixingzhe_qzzz
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
601,098subscribers
-63,715 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 316,228–1,000,000.
| Telegram ID | -1001830952551 |
|---|---|
| Type | Channel |
| Username | @feixingzhe_qzzz |
| Description | 🏆🔥东南亚求职招聘首选菲行者频道🔥🏆 🇵🇭求职招聘: @feixingzhe_qzzz 🇵🇭骗子曝光: @feixingzhe_baoi 🇵🇭吃瓜中心: @feixingzhe_cgzx 🇵🇭人事大队: @feixingzhe_rsdd 一键加入所有:https://t.me/addlist/w3RWGTVoKt1iOGYx 🤝商务合作 @fxzswh 📝频道小编 @fxzpdzy #国外华人行走必备群组 #求职招聘第一线 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 67 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/feixingzhe_qzzz |
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 8 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 the other topics.
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.
Posts published here appear in near-verbatim form on 9 other registered channels. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @feixingzhe_qzzz/54439 · this entry7 Aug 2026, 06:32 UTC | @jianpuzhai_03/76827 Aug 2026, 11:39 UTC | 1.00 | 5.1 hours |
| @feixingzhe_qzzz/54519 · this entry10 Aug 2026, 13:02 UTC | @jianpuzhai_03/773411 Aug 2026, 05:36 UTC | 1.00 | 17 hours |
| @feixingzhe_qzzz/54649 · this entry17 Aug 2026, 10:37 UTC | @jianpuzhai_03/783418 Aug 2026, 11:31 UTC | 1.00 | 25 hours |
| @feixingzhe_qzzz/54832 · this entry25 Aug 2026, 14:06 UTC | @jianpuzhai_03/800425 Aug 2026, 15:48 UTC | 1.00 | 1.7 hours |
| @feixingzhe_qzzz/55061 · this entry5 Sept 2026, 12:27 UTC | @jianpuzhai_03/83735 Sept 2026, 12:38 UTC | 1.00 | 11 minutes |
| @feixingzhe_qzzz/55166 · this entry11 Sept 2026, 04:27 UTC | @jianpuzhai_03/855011 Sept 2026, 05:56 UTC | 1.00 | 89 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @jianpuzhai_03 | 15 (8/8 hand-verifiable sample passed) | 1.00 | 1.8 hours | this entry (15–0) |
| @dibaiSB | 15 (8/8 hand-verifiable sample passed) | 1.00 | 2.1 hours | this entry (15–0) |
| @QZZPP66 | 11 (8/8 hand-verifiable sample passed) | 1.00 | 89 minutes | this entry (10–1) |
| @dibai2025 | 6 (6/6 hand-verifiable sample passed) | 0.98 | 2.2 hours | this entry (5–1) |
| @qiuzhi008 | 6 (6/6 hand-verifiable sample passed) | 1.00 | 3.5 hours | this entry (4–2) |
| @YTT789 | 6 (6/6 hand-verifiable sample passed) | 1.00 | 78 minutes | this entry (6–0) |
| @SLLKQZ1 | 5 (5/5 hand-verifiable sample passed) | 1.00 | 1.5 hours | this entry (5–0) |
| @dibaidddd | 5 (5/5 hand-verifiable sample passed) | 1.00 | 19 minutes | @dibaidddd (5–0) |
| @zhaopinqiuzhi580 | 5 (5/5 hand-verifiable sample passed) | 1.00 | 3.8 hours | this entry (5–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. 9 of the 9 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 532 comparable posts for this entry, running 7 August 2026 to 17 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.
Of the group of 3 channels, the one whose matching posts we hold earliest is @dibaiSB. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_source, last confirmed 18 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.
This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Nov 2026, 08:16 | 601,098 | -9,493 |
| 12 Nov 2026, 22:00 | 610,591 | -3,824 |
| 10 Nov 2026, 17:59 | 614,415 | -3,079 |
| 9 Nov 2026, 08:21 | 617,494 | -3,524 |
| 8 Nov 2026, 03:05 | 621,018 | -2,639 |
| 7 Nov 2026, 02:58 | 623,657 | -2,427 |
| 5 Nov 2026, 23:57 | 626,084 | +14,608 |
| 4 Nov 2026, 21:21 | 611,476 | +12,792 |
| 3 Nov 2026, 20:38 | 598,684 | +6,149 |
| 2 Nov 2026, 23:36 | 592,535 | +6,236 |
| 2 Nov 2026, 01:49 | 586,299 | -30,675 |
| 1 Nov 2026, 04:20 | 616,974 | +8,973 |
| 31 Oct 2026, 02:59 | 608,001 | +18,286 |
| 30 Oct 2026, 00:14 | 589,715 | -3,538 |
| 28 Oct 2026, 22:49 | 593,253 | -2,253 |
| 27 Oct 2026, 23:06 | 595,506 | +3,622 |
| 26 Oct 2026, 21:59 | 591,884 | +679 |
| 26 Oct 2026, 01:10 | 591,205 | +7,617 |
| 24 Oct 2026, 23:36 | 583,588 | -2,375 |
| 24 Oct 2026, 01:41 | 585,963 | first reading |
2,023 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 212 pages of Telegram’s post history, 20 posts per page.
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 530 of 532 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 17 November 2026 |
|---|---|
| Posts held | 2,023 (6 August 2026 – 17 November 2026) |
| Views total | 4,549,889 |
| Reactions total | 29,333 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Nov 2026, 04:32 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.
Lifetime counters from Telegram’s own channel header, read 18 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.
Measured directly from 54 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.
46,814 reactions across 853 posts, in 28 distinct kinds. The most used accounts for 13.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 6,351 | 13.6% | |
| 🎉 | 6,276 | 13.4% | |
| ❤ | 5,924 | 12.7% | |
| 🔥 | 5,823 | 12.4% | |
| 😁 | 3,961 | 8.46% | |
| 😘 | 2,761 | 5.90% | |
| 🕊 | 2,389 | 5.10% | |
| ⚡ | 2,305 | 4.92% | |
| 🥰 | 2,237 | 4.78% | |
| 👏 | 2,219 | 4.74% | |
| 😎 | 2,215 | 4.73% | |
| 🤩 | 2,189 | 4.68% | |
| 😍 | 2,068 | 4.42% | |
| 🥱 | 17 | 0.036% | |
| 👎 | 15 | 0.032% | |
| 👌 | 14 | 0.03% | |
| 🍌 | 13 | 0.028% | |
| 😢 | 10 | 0.021% | |
| ❤🔥 | 8 | 0.017% | |
| 💔 | 5 | 0.011% | |
| 8 further kinds | 14 | 0.03% |
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 853 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 46,814 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 2 October 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.
Telegram’s own ‘edited’ marker: 1 of 637 posts held from the last 30 days (0.157%) 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).
求职:人现在在柬埔寨 做过股转和欧美精聊日韩商城 会整套操作流程 现在公司停工解散状态 想向稳定待遇好的公司求职 只做杀盘 不做体育之类的项目 勿扰 @ldodd139
🔥22😍17👍15
求职:本人目前在国内(广东)今年暂时不想出国 做过国内精聊海外精 做过A股和快杀 @zhaosi2026
😍23👍19⚡11
🇵🇭菲行者:求职招聘 pinned a photo
🤩🤩🤩 9U国际—PG官方合作伙伴 👉PG/WG每日首充50% ⬆️关注9U彩金秘籍 优惠不迷路 ⚡️官网: 9U.COM 9️⃣官方客服 : @KF9U 9️⃣官方客服 : @KF9U1 9️⃣官方客服 : @KF9U2(无会员可联系) 🤑投注机器人: @VIP9U 🥰官方频道 @www9ucom 💎#付费广告SVIP
🤩31🎉11👍11
现在有没有哪个靠谱老板可以小路偷渡把我兄弟接出去,我这边可以配合出发,有实力的老板欢迎对接 @mingming893
⚡20🕊20🎉14
求职!!英文翻译 要求底薪4000美以上,目前在菲律宾,带领6个员工,之前做美的,找除了缅以外的公司,有招的直接发工资待遇公司地址给我,啥也不发的一律不回 我飞机 @Lingkong222
👏29🔥15👍10
求职 人在国内 找个国内工作室 有经验 做事认真 有需要的老板可以联系 @fengfeng369369
🔥21😘21😎11
🇵🇭菲行者:求职招聘 pinned a photo
🔥柬 | 泰 | 菲 | 迪 | 兰卡【集团直招】🔥 👑 PG体育👑 常招岗位 ➡业绩岗—养老职能岗—技术岗⬅ 实时岗位信息请参考官方频道: PG集团岗位需求 🫵🫵🫵🫵🫵🫵🫵🫵🫵🫵🫵🫵🫵 🎯PG集团 多国直招:业绩岗、职能岗、技术岗,薪资优厚,多个岗位可供选择,期待您的加入! 🎯泰国 | 斯里兰卡 | 重点招募维护,带薪培训入职!综合薪资 20k-30k,纯中文办公环境,轻松无压力。多国职场任选 🎯部分岗位接受零经验小白(入职即享带薪培训);职能岗全员覆盖绩效激励;技术岗最高可达底薪50%的高额KPI奖金⚡️ 🎯推广重金扶持,底薪1W起,点位提成-行业前列,不禁足,可外宿(享有补贴) ✅行业龙头企业,不骗不坑,值得想稳定发展的人才选择。 😘公司福利😘 🎁 节日礼金:春节 / 中秋 / 端午 / 元旦等 🎁 工作时间:9小时制-月休4天 🎁补贴福利:外宿补贴、餐补、生日礼金 🎁年假福利:满 1 年享带薪年假 …
😘24🕊18⚡12
国内求职.任何赚钱项目都可以,本人做事利索,人 靠谱.嘴严.保密意识强.之前做过不少业务,国内任何地方都可以去,不出国.叫做炮灰 勿扰 @bs9199
👍30🤩13🕊12
甩人seo男人柬埔寨,目前没有赔付有9年seo工资经验,有国内综合盘口经验,海外菲律宾,巴西,印尼,经验 ,有团队来个招聘seo的 不是推广 骗招不要来了 @flztseo
⚡22🥰19👍13
您好,请帮忙发下,印度资金盘,亚洲和欧美精料在前公司都做出过成绩,也带过很多新人,国内也有很多做海外市场的,所以想在国内找个有实力背景的公司好好做事,本人在国外带组总业绩上千万美金,请联系 @ @mnb0078
😎31😍14👍9
Showing the 12 most recent of 2,023 posts we hold for @feixingzhe_qzzz. 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.
@feixingzhe_qzzz edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
We recorded 3 posts on @feixingzhe_qzzz 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.
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.
@feixingzhe_qzzz named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was 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.
Read from Telegram’s recommendation API, most recently 9 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.
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.
This channel appears in 29 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“🇵🇭菲行者:求职招聘” (@feixingzhe_qzzz), 601,098 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/feixingzhe_qzzz.
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.