一个朋友求职翻译类工作岗位,英式发音,有留学经历。 @fernanp98 频道只发送求职.自行测试是否是骗子 频道 :@Uozzo 群主 :@Pu551

Channel
安危.招聘.求职.找工作
@uozzo
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
16,003subscribers
-1,055 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001886830907 |
|---|---|
| Type | Channel |
| Username | @uozzo |
| 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 | 25 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/uozzo |
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 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 01:59 | 16,003 | -84 |
| 17 Sept 2026, 05:01 | 16,087 | -17 |
| 15 Sept 2026, 06:17 | 16,104 | -44 |
| 13 Sept 2026, 16:38 | 16,148 | -49 |
| 11 Sept 2026, 18:57 | 16,197 | -45 |
| 9 Sept 2026, 05:35 | 16,242 | -42 |
| 5 Sept 2026, 19:56 | 16,284 | -10 |
| 3 Sept 2026, 17:38 | 16,294 | -32 |
| 2 Sept 2026, 09:12 | 16,326 | -39 |
| 1 Sept 2026, 06:37 | 16,365 | -19 |
| 31 Aug 2026, 04:05 | 16,384 | -13 |
| 30 Aug 2026, 06:24 | 16,397 | -47 |
| 29 Aug 2026, 07:13 | 16,444 | -28 |
| 28 Aug 2026, 06:13 | 16,472 | -19 |
| 27 Aug 2026, 07:54 | 16,491 | -28 |
| 26 Aug 2026, 06:09 | 16,519 | -43 |
| 25 Aug 2026, 07:22 | 16,562 | -58 |
| 24 Aug 2026, 08:12 | 16,620 | -73 |
| 22 Aug 2026, 19:27 | 16,693 | -104 |
| 21 Aug 2026, 09:07 | 16,797 | first reading |
Engagement
717 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 53 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 14.4%
- avg views ÷ 16,003 subscribers
- Avg views / post
- 2,310
- 157 posts measured
- Reaction rate
- 0.03%
- reactions ÷ views · ER floor
- Posts in window
- 157
- of 717 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 3 of 157 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 3 September 2026 |
|---|---|
| Posts held | 717 (7 August 2026 – 3 September 2026) |
| Views total | 363,021 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 09:57 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
- Video runtime
- 11m 13s
- Average length
- 27s
Measured directly from 25 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
6 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 83.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5 | 83.3% | |
| 💩 | 1 | 16.7% |
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 11 of the 717 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 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 717 most recent posts we hold, published 7 August 2026 to 3 September 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
求职翻译,有海外留学经历,具备良好的英语听说读写能力,英式发音标准,现求职翻译、英语口译或笔译相关岗位。 @fernanp98 频道只发送求职.自行测试是否是骗子 频道 :@Uozzo 群主 :@Pu551
人在国内,没有护照,只能走小路,打算出去搞一波,以前做过精聊,快杀,求职东南亚各地区,想搞一条代理线自己做,黑公司,中介勿扰自己就要出去 有实力的大哥带一下。 @ridhes 频道只发送求职.自行测试是否是骗子 频道 :@Uozzo 群主 :@Pu551
自己几年前出去过,现在和几个兄弟一起。在国内出事了着急出去,想找一个靠谱的老板。头脑灵活,急切想挣钱。有需要的老板看到请联系我,中介勿扰 @facai666689 频道只发送求职.自行测试是否是骗子 频道 :@Uozzo 群主 :@Pu551
找工作,本人有精聊资金盘经验,目前人在国内,想找公司出去上班,做事踏实肯干有上进心,希望有缺人的老板可以联系我详谈, @acd147258 频道只发送求职.自行测试是否是骗子 频道 :@Uozzo 群主 :@Pu551
你好可以帮忙发一个帖子嘛,有护照正在低谷期跟朋友想去东南亚那边打拼闯一下,有缺人要人的联系 @lmswxf1 频道只发送求职.自行测试是否是骗子 频道 :@Uozzo 群主 :@Pu551
有博彩经验,之前一直在国内做,现在想去外面做 @alzos467 频道只发送求职.自行测试是否是骗子 频道 :@Uozzo 群主 :@Pu551
自己几年前出去过,现在和几个兄弟一起。在国内出事了着急出去,想找一个靠谱的老板。头脑灵活,急切想挣钱。有需要的老板看到请联系我,中介勿扰 @facai666689 频道只发送求职.自行测试是否是骗子 频道 :@Uozzo 群主 :@Pu551
😲全球生意,快人一步;全球收付,安全托付。😲 😘全料😘全料😘全料😘全料 ✨别人还在审核,你已经到账; 💵别人还在换汇,你已经回款。 🥰代收代付,认准(龍盛集團) 快,是标配;稳,是底线。🔥 ❤负责人:@LongSheng_Bosco ❤鹰皇国际:@YHGJ_mengmeng ❤漫威国际:@MWGJ_LOGAN ❤凱旋國際:@KXGJ_MoChou ❤騎士國際:@QSGJ_kefu09 ❤狮王支付:@SWZF_xiaofan @SWZF_zhazha
找工作,本人有精聊资金盘经验,目前人在国内,想找公司出去上班,做事踏实肯干有上进心,希望有缺人的老板可以联系我详谈, @acd147258 频道只发送求职.自行测试是否是骗子 频道 :@Uozzo 群主 :@Pu551
人事客服推广都做过几年 找一份工作目前不考虑推广 别的都可以 @peterghh 频道只发送求职.自行测试是否是骗子 频道 :@Uozzo 群主 :@Pu551
甩人seo男人柬埔寨,目前没有赔付有9年seo工资经验,有国内综合盘口经验,海外菲律宾,巴西,印尼,经验 ,有团队来个招聘seo的 不是推广 骗招不要来了 @hjhjhj99999 频道只发送求职.自行测试是否是骗子 频道 :@Uozzo 群主 :@Pu551
Showing the 12 most recent of 717 posts we hold for @uozzo. 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
Named by 5 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.
@av266 · 191,34623 posts日本国产无码破解Av少妇自慰高潮
@Av926 · 41,95123 postsAv关键词搜索
@av938 · 12,46623 posts【东南亚安危吃瓜】
@bc721 · 71,66223 posts吃瓜搞笑
@cg776 · 9,33523 posts越南美女吃瓜搞笑猎奇软色色
@Cg900 · 3,72223 posts日本无码Av中文字幕经典合集
@obcos · 59,34123 posts频道合集.防封中专
@pu229 · 4,40623 posts捷克欧美黑人无码精品合集
@pu772 · 42,75923 posts日本无码Av/Fc2PPV自慰强奸口交
@Rav522 · 16,78323 posts东南亚头条吃瓜
@svipzz · 89,70823 posts78.COM-官方频道@DF78
@tg78com · 19,9923 postswhdbeus
@whdbeus · 83 posts搜女出海 / TG群发 / TG拉群 / TG引流
@a4163 · 21 postViber云控|Viber跨境营销|Viber海外营销
@henfan8 · 31 postoooo6790
@oooo6790 · 51 postxiangcaofanbingbing
@xiangcaofanbingbing · 51 post尊利体育|新币娱乐|澳门娱乐
@youcaigungun · 11 post求职招聘|全网找工作
@zsls45 · 11 post
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
- 3
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 3
- vacant every time we have ever looked
@uozzo named 3 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 7 posts, 8 August 2026 – 3 September 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
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.
@XCRLZP · 121,976
Telegram ranks this channel #6 of 82 here — alongside 81 others — read 13 August 2026
@xii34 · 101,191
Telegram ranks this channel #13 of 69 here — alongside 68 others — read 15 August 2026
@dubaiuuu · 114,192
Telegram ranks this channel #15 of 67 here — alongside 66 others — read 17 August 2026
@qiuzhi008 · 238,544
Telegram ranks this channel #16 of 72 here — alongside 71 others — read 11 August 2026
@feixingzhe_qzzz · 629,041
Telegram ranks this channel #16 of 67 here — alongside 66 others — read 9 August 2026
@Dubaiqzzp · 95,231
Telegram ranks this channel #17 of 64 here — alongside 63 others — read 17 August 2026
@zii33 · 99,421
Telegram ranks this channel #17 of 78 here — alongside 77 others — read 16 August 2026
@qzzpfabu888 · 641,187
Telegram ranks this channel #17 of 72 here — alongside 71 others — read 9 August 2026
@YTT789 · 317,214
Telegram ranks this channel #21 of 68 here — alongside 67 others — read 10 August 2026
@dibai2025 · 307,520
Telegram ranks this channel #24 of 74 here — alongside 73 others — read 10 August 2026
@XMZPK · 86,448
Telegram ranks this channel #25 of 76 here — alongside 75 others — read 16 August 2026
@dibaidddd · 120,900
Telegram ranks this channel #25 of 70 here — alongside 69 others — read 13 August 2026
@JPZshibao888 · 76,978
Telegram ranks this channel #35 of 44 here — alongside 43 others — read 18 August 2026
This channel appears in 13 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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“安危.招聘.求职.找工作” (@uozzo), 16,003 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/uozzo.
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.