Telegram RegisterThe public register of Telegram
Telegram profile photo for 泰国招牌 迪拜求职 斯里兰卡找工作频道

Channel

泰国招牌 迪拜求职 斯里兰卡找工作频道

@HR_fugui

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

79subscribers

-3 since we began measuring on 13 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001681757220
TypeChannel
Username@HR_fugui
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live27 September 2026
Measurements held4
Confirmed unchanged3 times, most recently 27 September 2026
On Telegramt.me/HR_fugui

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 28 September 2026 and assigned it the closest of 31 fixed categories, at 64% 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

798280.513 August 2026 — 82 subscribers13 August 2026 — 82 subscribers21 August 2026 — 80 subscribers7 September 2026 — 79 subscribers13 August 20267 September 2026
4 measurements spanning 25 days, net -3. 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 79–82 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 00:5779-1
21 Aug 2026, 02:2580-2
13 Aug 2026, 02:4682no change
13 Aug 2026, 01:1882first reading

Engagement

9 posts held, back to 17 December 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 9 posts for this entry, the most recent from 17 December 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
4s
Average length
4s

Measured directly from 1 video 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

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.0%

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

Measured over the 9 most recent posts we hold, published 17 December 2024 to 17 December 2024, 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

17 Dec 2024, 14:11 UTC≈1,580 viewsread 13 August 2026

国内白资金,安全收款,支持易换交易 usdt~人民币 12/17 汇率 7.14 详情咨询客服💁@gxy106

17 Dec 2024, 14:06 UTC≈1,400 viewsread 13 August 2026
Forwarded from @gongzuozhaopinqiuzhi

RLZYZX 岗位:数据支持专员【偏offer发放】(2名) 国籍:外籍 性别:女 语言要求:中文流利 年龄:21-28岁 薪资待遇 : 10K转12K 工作时间 : 9小时月休4 办公地:菲 (愿意随部门搬迁去泰国或其他国家) 岗位要求: 1、有一定表格基础优先; 2、有人事助理等工作基础优先; 3、做事细致,有耐心; 4、良好的沟通能力; 岗位职责: 1、按要求整理、检查offer基础资料; 2、求职者基础信息核查; 3、offer发送; 4、信息台账整理、更新; 5、其他岗位相关工作; 需要的滴滴我telegram :@ziyu_88

17 Dec 2024, 13:53 UTC≈2,870 views1 reactionsread 13 August 2026

♥️泰国🇹🇭曼谷♥️ 24小时接单,全城可上门 详情咨询客服💁 @gxy106 主营业务 越南🇻🇳妹子♥️ 中国🇨🇳妹子♥️ 明码标价,拒绝任何套路 一手妹子♥️ 一手妹子♥️ 一手妹子♥️ 详情咨询客服💁@gxy106 总频道💁 https://t.me/qqabc88900

❤1

17 Dec 2024, 13:53 UTC≈2,410 views0 reactionsread 13 August 2026
Photo

🇻🇳越南🇻🇳嫩芽🌱 年龄19岁 净身高167cm 真实胸部🐻,全身无整形 没生育小孩,高挑苗条身材 🉑️喝酒🍻🉑️舌吻💋🉑️69👅 套餐一12000泰铢1小时一次 套餐二25000泰铢6小时夜 套餐三35000泰铢12小时夜

17 Dec 2024, 13:53 UTC≈2,960 viewsread 13 August 2026
Photo

曼谷🇹🇭 🇻🇳越南🇻🇳极品真胸新茶 身高165cm,甜美妩媚型 天然真胸🐻,皮肤白滑嫩 没生过小孩,紧致完美身材 🉑️流利中文🉑️喝酒🍻🉑️接吻💋 套餐一12000泰铢1小时一次 套餐二25000泰铢6小时夜 套餐三35000泰铢12小时夜

Showing the 9 most recent of 9 posts we hold for @HR_fugui. 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

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 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 7 September 2026 — this entry's latest reading, not the date you are reading this.

“泰国招牌 迪拜求职 斯里兰卡找工作频道” (@HR_fugui), 79 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/HR_fugui.

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.