Telegram RegisterThe public register of Telegram
Telegram profile photo for 东南亚 - 求职招聘

Channel

东南亚 - 求职招聘

@v3581

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

5,002subscribers

-3,227 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002137482575
TypeChannel
Username@v3581
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live6 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/v3581

Growth

5,0028,2296,615.56 August 2026 — 8,229 subscribers6 August 2026 — 8,215 subscribers10 August 2026 — 8,163 subscribers13 August 2026 — 8,112 subscribers16 August 2026 — 8,096 subscribers19 August 2026 — 8,044 subscribers23 August 2026 — 5,497 subscribers26 August 2026 — 5,443 subscribers29 August 2026 — 5,415 subscribers2 September 2026 — 5,378 subscribers6 September 2026 — 5,002 subscribers6 August 20266 September 2026
11 measurements spanning 31 days, net -3,227. 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 4,518–8,713 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 03:215,002-376
2 Sept 2026, 05:425,378-37
29 Aug 2026, 23:425,415-28
26 Aug 2026, 13:355,443-54
23 Aug 2026, 07:575,497-2,547
19 Aug 2026, 18:388,044-52
16 Aug 2026, 17:378,096-16
13 Aug 2026, 12:468,112-51
10 Aug 2026, 06:308,163-52
6 Aug 2026, 23:308,215-14
6 Aug 2026, 12:338,229first reading

Engagement

151 posts held, back to 4 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 16 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.38%
avg views ÷ 5,002 subscribers
Avg views / post
269
100 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
100
of 151 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 22 August 2026
Posts held151 (4 August 202622 August 2026)
Views total26,886
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Aug 2026, 20:03 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.

Recent posts

22 Aug 2026, 03:12 UTC91 viewsread 22 August 2026

手里大量有人,有没有哪个靠谱老板可以小路接出去,没有护照没有护照!!我这边可以安排,成了给我安排茶水费 @luedehuaa

22 Aug 2026, 03:12 UTC84 viewsread 22 August 2026

你好,帮发一下,谢谢,找个老板,线上,线下业务都可做,目前在临沂,可以国内跑,长期稳定,懂感恩,非诚勿扰 @yz050

22 Aug 2026, 03:12 UTC83 viewsread 22 August 2026

你好,帮我发一下求职信息,谢谢本人中国人在柬埔寨,目前没有工作。嗯,现在急需找份工作。海外盘口不做体育盘,有公司缺人的联系我一下,一个人。本人有护照。正常, @fchd9999

22 Aug 2026, 03:12 UTC82 viewsread 22 August 2026

帮忙发一下求职 本人在亚美尼亚, 29岁, 有老板私人助理,公司行政与公司翻译,客服/电销管理的经验, 俄语,中文 ,英文 都很流利。 只考虑在亚美尼亚长期稳定的工作,其他国家的请勿扰 飞机号:@Liam1199

22 Aug 2026, 03:12 UTC81 viewsread 22 August 2026

泰国周边甩几个非洲人.人在曼谷,可以接的来.中介勿扰 @GGpk9999

22 Aug 2026, 03:12 UTC79 viewsread 22 August 2026

求职 人在国内宁夏银川两个人 真心要出去做事 有两年精聊工作经验 打字快 中介不谈 @zqzqmzsmzs

22 Aug 2026, 03:12 UTC82 viewsread 22 August 2026

有没有老板招小弟,线上,线下都可以做 国内国都可以跑腿,目前在杭州,长期稳定,懂感恩,非诚勿扰 @jc0360

22 Aug 2026, 03:12 UTC87 viewsread 22 August 2026

缅甸求职:一只团队都是中国人,目前有费用的,因原公司的原因打算换家公司,人是老手做过很对项目,也有组长管理,有实力靠谱的公司联系。 @xlsj998887

22 Aug 2026, 03:12 UTC88 viewsread 22 August 2026

求职:人在广东 有四年加密货币精聊经验 做过业务员 管理 去年刚从柬埔寨回来 目前寻求精聊公司管理岗位 国内外都可 寻求好大哥 包行程的来私 注意看内容信息再私@HKTV66666

22 Aug 2026, 03:12 UTC89 viewsread 22 August 2026

国内做过一段时间资金盘和股转,刷手,有没工作室能接收,国外待遇好也可以接受。走投无路了,急需找个路子,飞机 @zhanxiang098

22 Aug 2026, 03:12 UTC92 viewsread 22 August 2026

求职,24 岁,有护照,人在福建漳州,求工作,有过一段时间刷单经验,车队安保经验,会开车,跑腿什么都可以,有需要老板可联系 @a884223

22 Aug 2026, 03:12 UTC91 viewsread 22 August 2026

国内做过一段时间资金盘和股转,刷手,有没工作室能接收,国外待遇好也可以接受。走投无路了,急需找个路子,飞机 @zhanxiang098

Showing the 12 most recent of 151 posts we hold for @v3581. 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 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 6 September 2026 — this entry's latest reading, not the date you are reading this.

“东南亚 - 求职招聘” (@v3581), 5,002 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/v3581.

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.