Telegram RegisterThe public register of Telegram
Telegram profile photo for MT集团官方直招

Channel

MT集团官方直招

@MTPHJOB

On this record: Growth · Engagement · Posts · Citations · Cite this entry

257subscribers

-2 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001366206642
TypeChannel
Username@MTPHJOB
CreatedBetween 1 April 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/MTPHJOB

Growth

2572592587 August 2026 — 259 subscribers7 August 2026 — 259 subscribers13 August 2026 — 257 subscribers7 August 202613 August 2026
3 measurements spanning 7 days, net -2. 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 257–259 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 15:46257-2
7 Aug 2026, 01:33259no change
7 Aug 2026, 01:06259first reading

Engagement

19 posts held, back to 23 October 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
80.2%
avg views ÷ 257 subscribers
Avg views / post
206
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 19 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 21 July 2026
Posts held19 (23 October 202521 July 2026)
Views total206
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 01:33 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

21 Jul 2026, 11:25 UTC206 viewsread 7 August 2026

新增职缺:前端工程师 *1 必备react,负责vue程序的开发,三年以上经验,负责公司直播项目的开发 8小时 双休,菲假 薪资面议 菲/迪/台/泰入职 有意请联系:@MTvenny

14 Jul 2026, 12:21 UTC367 viewsread 7 August 2026
Photo

7月最新岗位职缺 多国可选择 详询:@MTvenny

22 May 2026, 12:24 UTC734 viewsread 7 August 2026

新增岗位:LINUX运维 3 年以上雲端或系統運維相關工作經驗,具備 On-Call 值班經驗,非上班時間可在 15 分鐘內響應 熟悉Linux作业系统操作,AWS、Azure、阿里云、腾讯云...等大型云端平台建制与维护经验, 具備 CDN 操作經驗(設定、緩存清除、線路切換),熟悉至少一家主流 CDN 廠商 薪资面议 8小时 双休,菲假 菲/迪/台/马/越/泰 入职 详询:@MTvenny

19 May 2026, 04:12 UTC713 viewsread 7 August 2026

新增岗位:在线客服 人员增加 5位 男女均可,35岁以下,需要有熟悉体育赛事及各种体育盘口 薪资:RMB 8485,转正RMB 9585 9小时,月休4-5天 转正后等级晋升 菲/迪 /泰/马/台 入职 详询:@MTvenny

12 May 2026, 09:14 UTC754 viewsread 7 August 2026
Photo

最新岗位职缺,多国可选择,菲/迪/泰/越/马享有房餐补、签证报销,欢迎投递简历 详情请咨询@MTvenny

23 Mar 2026, 07:37 UTC863 viewsread 7 August 2026

Java工程师持续招聘中,欢迎咨询,投递简历❤️

3 Mar 2026, 10:32 UTC≈1,000 viewsread 7 August 2026

新增岗位:Java工程师*2 3年以上工作经验。需具备体育经验、项目重构经验、性能优化经验,精通OC和swift语言 8小时 双休,菲假 , 薪资范围:30-40K 菲/迪/泰入职 更多详情欢迎咨询:@MTvenny

3 Mar 2026, 10:29 UTC924 viewsread 7 August 2026

新增岗位:安卓工程师*2 至少五年以上相关经验,要求重心是体育+kotlin开发经验,负责体育APP开发和日常维护工作 8小时 双休,菲假 , 薪资范围:30-40K 菲/迪/泰入职 更多详情欢迎咨询:@MTvenny

25 Feb 2026, 07:51 UTC924 viewsread 7 August 2026
Photo

最新岗位职缺,更多岗位,欢迎咨询:@MTvenny

27 Jan 2026, 07:09 UTC820 viewsread 7 August 2026

新增岗位:操盘/风控专员 0经验小白薪资:9000RMB-10000RMB 初级操盘手: >>>无经验者:试用期10000,转正12500 >>>至少1年经验者:试用期12500,转正15000 中级操盘手:试用期12500,转正15000RMB-18000RMB 至少1-2年操盘经验,需要能独立调控各项赛事早盘的盘口水位 高级操盘手:试用期15000,转正18000 有3年左右操盘经验,需要能独立调控各项赛事早盘/滚球的盘口水位 资深操盘手/操盘组长:薪资面议 有3年以上操盘经验,需要能独立调控各项赛事早盘/滚球的盘口水位,同时知悉跳盘调控原理,熟悉操盘后台的功能设计逻辑及原理 工作时间:9小时,三班倒制度,分早中晚三班(后续根据情况在调整多长时间轮换一次) 休假:每月休6天 上岗:菲律宾/码来/泰国/台湾(居家) 详询:@MTvenny

20 Jan 2026, 10:42 UTC687 viewsread 7 August 2026

新增岗位:ZB PO(直播运营) 岗位要求: 1.具备直播站运营相关经验,熟悉直播流程、规则及日常管理; 2.自带主播资源,或具备稳定的主播招募与合作渠道; 3.能接受长期凌晨班次工作,时间为 23:00 – 11:00; 4.具备良好的沟通协调能力与执行力,能独立推进相关工作; 5.通过分析数据/活动策划 优化主播结构与运营策略; 6..能独立完成主播引入与安排主播工作(开播培训,主播日常事务协调) 7. 必须熟悉体育赛事体系与赛程 薪资待遇: 12k 转15k ,周休1 菲/迪/马/泰/台 入职 详询:@MTvenny

Showing the 12 most recent of 19 posts we hold for @MTPHJOB. 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.

Citation-graph rank

Citation-graph rank — 1,389,890 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

“MT集团官方直招” (@MTPHJOB), 257 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/MTPHJOB.

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.