接机😎
❤1👏1
Channel
@BUDINGZHIZHAO
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
136subscribers
-1 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002174823095 |
|---|---|
| Type | Channel |
| Username | @BUDINGZHIZHAO |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/BUDINGZHIZHAO |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 02:02 | 136 | -1 |
| 9 Aug 2026, 03:31 | 137 | first reading |
17 posts held, back to 17 February 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 1 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 29 July 2026 |
|---|---|
| Posts held | 17 (17 February 2026 – 29 July 2026) |
| Views total | 468 |
| Reactions total | 3 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 03:31 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.
17 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 88.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 15 | 88.2% | |
| 👏 | 1 | 5.88% | |
| 🥰 | 1 | 5.88% |
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 6 of the 17 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 17reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 17 February 2026 to 29 July 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.
接机😎
❤1👏1
招商,推广,包网招商(迪拜市区入职) 统筹助理。客服专员。报告编辑,助理,法务代表,资产专员,育儿师,网管(迪拜市区入职) 监察(需要有内部查舞弊的经验)泰国曼谷入职
❤1
拒绝一眼望到底的日子,拒绝拿着微薄的薪水精打细算!在这个处处充满机会的时代,只要你敢拼、敢要高薪,我们就能给你提供绝佳的舞台。 岗位:招商 /推广/代理发展/人事/各种技术岗位/职能岗位 要求:不甘平庸、执行力强、渴望实现财富自由 福利:底薪+高额提成,付出与回报绝对成正比 坐标: 迪拜🇦🇪 斯里兰卡🇱🇰 ✅✈️: @HRxiatian88888888 ✅✈️ :@HRxiatian888888888 ✅✈️ :@HRxiatian8888888 ✔️赔付透明 /包机票 ✔️提供迪拜合法的白产工作签 💗【点击这里,返回主页】
统筹助理目前2个需求: 1位初级统筹助理,优先考虑函数表格做过的,优秀中国籍也可以。 1位高级统筹助理,要求必须会函数表格,优秀中国籍也可以。 在迪拜入职,后面要去兰卡 有简历请多多推荐。
远程岗位如下 远程招聘专员 远程产品助理(区块链/金融方向) Java开发专员 WEB开发专员 flutter开发专员 虚拟币财务专家顾问
产品助理(区块链/金融方向),职能岗/专员级/需求1人 Java开发专员,职能岗/专员级/需求2人 WEB开发专员,职能岗/专员级/需求1人 flutter开发专员,职能岗/专员级/需求1人 虚拟币财务专家顾问,职能岗/专员级/需求1人
俄语商务接待 10位,优秀斯坦级也要 入职的是商务公司,业务涵盖:差旅管理、商务旅游、商务接待、商务会议、会展业务等
java岗 职能岗 专员 1人 办公区域:线上远程全职办公,严禁远程兼职 其他备注:无bc经验 岗位要求 1.招聘渠道:直招 2.薪资待遇:14-20k 按能力和投入度评估,转正后有绩效评定,具体面议 3.工作时间:10休4 12:00-10:00 4.人选性别:不限 5.人选年龄:35岁内 6.国籍要求:仅限中国籍 7.地区限制:回族、新疆籍、斯坦籍、埃及籍 8.学历要求:大专及以上 9.语言要求:中文,英文 岗位职责 1.计算机相关专业,本科以上学历,5年以上互联网后端技术开发经验,有较 深厚的技术背景和实践经验; 2.精通Java语言,及主流开源框架(Springmvc,springboot,sping cloud,mybatis及mybatis-plus(,具有较强的系统分析,设计能力; 3.熟悉mysql数据库相关技术,对mysql的承载性能与优化方案有深入理解; 4.有一定的区块链钱包开发或三方钱包集成…
❤8
flutter/前端全栈岗 职能岗 专员 1人 不接受目前在迪的人选入职! 线上远程全职办公 办公区域:线上远程全职办公,严禁远程兼职 其他备注:无bc经验 1.招聘渠道:直招 2.薪资待遇:18-25k 按能力和投入度评估,转正后有绩效评定,具体面议 3.工作时间:10休4 12:00-10:00 4.人选性别:不限 5.人选年龄:35岁内 6.国籍要求:仅限中国籍 7.地区限制:回族、新疆籍、斯坦籍、埃及籍 8.学历要求:大专及以上 9.语言要求:中文,英文 岗位要求 1.本科及以上学历,5年以上前端开发经验; 2.熟练掌握JavaScript,HTML,CSS/SASS/LESS,flutter等前端开发技术; 3.熟练使用Vue,对React,Angular或其它前端MVC框架有一定的了 解; 4.精通Dart语言,深入理解Flutter框架原理,能解决复杂问题; 5.熟悉App模块化开发,深入理解多应用开…
❤4
【前端全栈需求】 必须要以flutter为主,同时要会vue/react,最好也做过一点原生(ios和Android,加分项)
数据组长 办公区域:斯里兰卡( 可直接旅游签入职) ⚠️ 重要说明: 入职当天安排测试 未通过测试者,当天解除录用,相关费用需自理 招聘渠道:直招 薪资待遇:试用期18K,转正20K+绩效0-3K 工作时间:每天10小时,月休 3 天 人选性别:不限 人选年龄:20-38岁 国籍要求:外籍华人、马来籍、台湾藉(优秀的中国籍也可以考虑) 地区限制:中国籍、斯坦藉 语言要求:中文 岗位职责 1.熟悉 Excel,能熟练使用表格及常用函数公式 2.具备良好的理解能力与沟通能力 3. 会使用或了解 编程语言(如 Python、SQL 等)者优先 4.有数据相关或相近岗位经验者优先 5.不接受小白、不接受不会使用表格公式 岗位要求 1.负责公司各部门数据汇总、整理和分析工作; 2.滿足日常相关部门提出的数据需求; ✅✈: @HRxiatian88888888 ✅✈ :@HRxiatian888888888 ✅✈ :@HRxiati…
网络工程师 山东、河南、福建不考虑 办公区域:斯/迪(会有调动,不固定) 1.招聘渠道:直招 2.薪资待遇:20-35k 试用期2个月 3.工作时间:9小时,月休4,三班倒 4.人选性别:男生 5.人选年龄:21-38岁 6.国籍要求:不限 7.地区限制:山东、河南、福建除外 8.学历要求:大专及以上 9.语言要求:中文沟通顺畅 10.办公地点:不固定,斯或迪,根据工作需求安排。 岗位要求 1、良好掌握思科设备高级网络知识(交换如VLAN、STP、VTP、二层安全等;路由如RIP/OSPF/EIGRP/BGP/MPLS VPN等);精通思科交换、路由、安全、无限,并具备在大中型企业交换路由网络运维实操及架构设计经验;掌握H3C或者华为、juniper、H3C等厂商任意一们交换路由知识的优先考虑; 2、要求掌握思科、JUNIPER(ScreenOS-JUNOS)、华为、华3C安全产品如防火墙中的任意一家的日常运维操作; 3、…
Showing the 12 most recent of 17 posts we hold for @BUDINGZHIZHAO. 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 — 227,100 of 1,480,944entries 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.
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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“布丁直招 DUBAI GROUP” (@BUDINGZHIZHAO), 136 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/BUDINGZHIZHAO.
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.