国内求职 人在广东 做过股转 资金盘 精聊 快杀 做过欧美地区跟亚洲地区 基本上目前常见的项目都做过 人很懂事 机灵 带过人 参与过策划 做过国内杀鱼 现在想找个国内的好项目好老板 有团队可以叫人 广东深圳地区优先选择过去 (不出国 不做线上)知恩图报 联系 @facai_1000

Channel
东南亚求职 - 缅甸 柬埔寨 国内 菲律宾 迪拜
@yatai003
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
36,341subscribers
-4,729 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1003254318439 |
|---|---|
| Type | Channel |
| Username | @yatai003 |
| Created | Between 1 October 2025 and 31 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 58 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/yatai003 |
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 10 September 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 22:36 | 36,341 | -1,490 |
| 4 Nov 2026, 19:25 | 37,831 | -1,314 |
| 3 Nov 2026, 20:00 | 39,145 | -2,706 |
| 2 Nov 2026, 19:38 | 41,851 | -3,337 |
| 1 Nov 2026, 16:39 | 45,188 | +31,328 |
| 31 Oct 2026, 18:07 | 13,860 | -112 |
| 30 Oct 2026, 17:11 | 13,972 | -1,877 |
| 29 Oct 2026, 16:58 | 15,849 | -2,211 |
| 28 Oct 2026, 16:07 | 18,060 | -168 |
| 27 Oct 2026, 12:46 | 18,228 | -29 |
| 26 Oct 2026, 09:49 | 18,257 | -14 |
| 25 Oct 2026, 08:44 | 18,271 | -102 |
| 24 Oct 2026, 10:15 | 18,373 | -226 |
| 23 Oct 2026, 11:27 | 18,599 | -37 |
| 22 Oct 2026, 08:27 | 18,636 | -3 |
| 21 Oct 2026, 04:56 | 18,639 | -9 |
| 20 Oct 2026, 04:40 | 18,648 | -2 |
| 19 Oct 2026, 07:50 | 18,650 | -2 |
| 18 Oct 2026, 10:05 | 18,652 | -43 |
| 17 Oct 2026, 10:20 | 18,695 | first reading |
Engagement
822 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 65 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3.01%
- avg views ÷ 36,341 subscribers
- Avg views / post
- 1,090
- 113 posts measured
- Reaction rate
- 0.177%
- reactions ÷ views · ER floor
- Posts in window
- 113
- of 822 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 13 of 113 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 5 November 2026 |
|---|---|
| Posts held | 822 (6 August 2026 – 5 November 2026) |
| Views total | 123,635 |
| Reactions total | 13 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 5 Nov 2026, 17:10 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.
Reaction mix
15 reactions across 15 posts, in 2 distinct kinds. The most used accounts for 86.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 13 | 86.7% | |
| ❤ | 2 | 13.3% |
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 19 of the 822 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 15 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 822 most recent posts we hold, published 6 August 2026 to 5 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: 1 of 113 posts held from the last 30 days (0.885%) 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).
求职 人在妙瓦底 有一年多美股和欧美精聊经验 因公司解散 向平台寻找稳定待遇好的公司 有相同项目公司招聘的联系 @dogsa80008
求职,人在国内,做过电商、直播、盲盒、链游数藏,能做产品运营、推广获客、商务对接,也带过团队。有靠谱项目缺人的老板联系,具体私聊。@JinLance0422
诚心找靠谱公司老板!能给茶水的,小路能接的联系没有护照在国内,人靠谱,我是中介,看清楚再来联系,需要的联系: @banghjio
你好 想出去上班 帮忙发一下可以吧 有护照 人在国内 做事靠谱 不墨迹 有过敲键盘工作 有招人的公司可以联系 @deng888dai
一个身边的朋友求职英国市场的翻译。@fernanp98
国内求职.任何赚钱项目都可以,本人做事利索,人 靠谱.嘴严.保密意识强.之前做过不少业务,国内任何地方都可以,不出国.叫做炮灰 勿扰 @bs9199
你好,可以帮我发一个帖子吗,落难了有护照之前在国内朋友工作室做过日韩商城转股这些,想去国外闯几年,有缺人的联系 @canshenji
求职: 寻找线上日语翻译 女生声优 话务工作。在日十年,线上翻译声优话务工作三年经验,专业级日语,擅长和日本人沟通业务能力能打,可对应日盘一切模式(公检不做)寻靠谱公司收全职翻译,不去线下只线上外协,不接散单。聊手解决不了的疑难杂症,别人电话上和日本人谈不下来的深度交涉,找我一切搞定。 TG:@YoYoikoen10
国外回流人员,背景干净,目前在国内,不打算出去了,精通大部分海外项目,现在寻找在国内的海外盘口,小作坊就不要来了,找个实力强的,粉稳定的盘口,希望老板给个机会 @duguzui
#团队求职 柬埔寨迪拜做过美日韩精聊快杀,三年带团队经验,从0到1所有流程都会,目前想在国内找公司重新做业务,希望能找到一个靠谱稳定的公司,或者不差事的老板,有信心短时间内出成绩 ,线上不做的,全程线下靠谱公司和老板DD~ @gnd203
国内求职 人在广东 做过股转 精聊 快杀 打粉做过欧美地区跟亚洲地区 基本上目前常见的项目都做过 人很懂事 机灵 执行力强 快过年了 希望找个国内的好项目好老板 有团队可以叫人 南方地区优先选择过去 (不出国 不做线上)知恩图报 联系 @ac219219
Showing the 12 most recent of 822 posts we hold for @yatai003. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 3 registered channels — 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.
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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@yatai003 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.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 2 posts, 2 September 2026 – 2 September 2026 · confirmed gone 1 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 18 August 2026 – 18 August 2026
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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“东南亚求职 - 缅甸 柬埔寨 国内 菲律宾 迪拜” (@yatai003), 36,341 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/yatai003.
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.