Telegram RegisterThe public register of Telegram

Channel

婆婆丁

@DAZP99

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

32subscribers

+0 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-1001851681304
TypeChannel
Username@DAZP99
DescriptionGO/JAVA/WEB/PHP/DBA/产品/运维/PHTHON/UNIAP(总部直招) 招聘频道:https://t.me/DAZP99
CreatedBetween 1 October 2022 and 31 August 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/DAZP99

Growth

327 August 2026 — 32 subscribers11 August 2026 — 32 subscribers7 August 202611 August 2026
2 measurements spanning 4 days. 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 31–33 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 02:1532no change
7 Aug 2026, 13:4132first reading

Engagement

15 posts held, back to 7 January 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.

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

What this channel posts

Photos
69
Videos
6
Links
18

Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
11s
Average length
11s

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

3 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
266.7%
💩133.3%

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

Measured over the 15 most recent posts we hold, published 7 January 2025 to 26 May 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

26 May 2026, 15:01 UTC97 viewsread 11 August 2026

GW :客服维护 QD: ZZ/NT XB : 不限 NL : 必须满 20岁 XL : 不限 GJ : 不限 YYYQ : 中文流利 XZDY : 试用期两个月,试用期10000+转正绩效提成 GZSJ : 9小时,月休4(倒班) GWXQ : 1. 中文沟通无障碍,普通话流利,理解能力强; 2. 良好的沟通表达能力、情绪管理能力和抗压能力,团队协作能力强; 3. 热爱游戏,能快速了解客户心理和游戏需求; 4. 接受轮休和排班 5. 电脑操作打字熟练,掌握基础操作办公软件; 不接受推广类岗位经验 有维护经验,如电销、电维,客户维护,客服等经验皆可 GWZZ : 1. 主要负责平台客户的常规业务问题解决与回复; 2. 有服务意识和服务精神,拥有较强的执行能力,良好的团队协作能力; 3. 挖掘并分析客户需求,对客户提出的意见和建议进行整理反馈及时跟进; 4. 能快速了解客户心理和游戏

25 Apr 2026, 14:02 UTC163 viewsread 11 August 2026

GW:监察专员/组长/主管 4名 GJ:国籍不限,外籍优先 NL:21-35岁 XL:大专及以上 XZDY:10k-25k区间 GZDD:TH GWXQ: 1. 具备三年以上的监察岗位经验,有充分的查舞弊的经验及技能。 3. 对中文理解无障碍,逻辑思维有组织,语言表达清晰,抗压能力强。 4. 取证经验丰富,面谈技巧丰富。 5. 有过全流程舞弊调查经验的优先,接受返聘,但需要特批的都不考虑。 6. 具有保密意识。 GWZZ: 1.通过财务数据,分析与查找舞弊线索,并进一步排查与锁定舞弊事项。 2.通过各飞机群组核查舞弊举报线索,并进一步查证事项的真实性与责任人。 3.接受举报投诉进行查证,梳理举报反映问题线索,形成专项报告。

3 Apr 2026, 10:40 UTC264 viewsread 11 August 2026

GW : 游客客服专员 40名 QD : NT/ZZ XB : 不限 NL : 18-35 GJ : 中国、马来、越南 YYXQ : 中文沟通顺畅 XZDY : 12000 GZSJ : 9小时 GZDD : KJY *不接受 推广, SEO,商推 ,招商,代理, YHWH 离职返聘 ,不接受推广类岗位经验。有客服经验优先 GWXQ: 1. 中文沟通无障碍,普通话流利,理解能力强;中籍: 要求大专以上学历,外籍:要求本科以上学历 2. 良好的沟通表达能力、情绪管理能力和抗压能力,团队协作能力强; 3. 热爱游戏,能快速了解客户心理和游戏需求; 4. 接受轮休和排班 5. 电脑操作打字熟练,掌握基础操作办公软件; GWZZ : 1.协助会员处理存取款以及优惠问题 2. 有服务意识和服务精神,拥有较强的执行能力,良好的团队协作能力; 3. 挖掘并分析客户需求,对客户提出的意见和建议进

1 Apr 2026, 10:22 UTC206 viewsread 11 August 2026

GW:后台专员 29名 XB:不限 NL:21-31 GJ:台湾/马来/印尼 YYXQ:中文流利 XL:大专以上 XZDY:12K-14K +绩效(根据人员表现) GZSJ: 9小时 月休四(三班倒) GZDD:KJY (9名) DB (20名) GWXQ: 1、中文沟通无障碍,普通话流利,思维反应灵敏,理解能力强; 2、有行业经验优先,最好对体育盘口有一定的了解; 3、较强的服务意识,反应能力较强,有耐心,独立解决问题能力佳; 4、能接受三班倒及夜班,轮班排休制度,保密意识强; 5、熟练使用办公软件excel、word文档 GWZZ : 1、负责全站线上活动的组织策划; 2、日常活动派彩、活动数据统计,制作活动分析 3、结合节日、赛事、热点及产品方向制定整站活动策略; 4、负责活动的推进执行,细化工作流程,与各部 门协调沟通,保证活动按计划上线; 5、活动效果监控,总结及优化; 6、按质、按量、按时完成上级交办的

1 Apr 2026, 10:21 UTC177 viewsread 11 August 2026

GW:用户反馈专员 6名 XB:不限 NL:21-30 GJ:中国 (非大陆河南、山东,福建均可) YYXQ:中文 读、听、写佳(打字40/分) XL:大专以上 XZDY:1390U-1950U GZSJ: 9小时 月休四(三班倒) GZDD:SLK * 接受小白不要做过TG的人选 GWXQ: 操作后台处理会员反馈留言问题,类似在线客服工作。 GWZZ : 需要按照部门标准,规范的回复问题,有主动积极良好的服务意识,有国内相关的服务行业经验的优先。

7 Apr 2025, 07:16 UTC924 viewsread 11 August 2026

后勤专员(斯里兰卡) 薪资待遇:10k-12K 有绩效 餐补 工作时间:9am-6pm,周日休 人选性别:不限 国籍要求:外籍华人/中国籍 学历要求:大专及以上 语言要求:中英文 办公区域:斯里兰卡 人数要求:3人 岗位需求增加以下 1、具备熟练的英语口语及文笔表达能力,中文能正常交流 2、具备海外工作经验 3、善于管理时间,处理多项任务和优先级,应变能力强,确保高效工作 4、熟练应用办公软件,如excel、wps等 5、学习能力强,具有良好的职业道德和团队协作精神

27 Mar 2025, 11:56 UTC824 views0 reactionsread 11 August 2026

岗位:内账 职级:专员 人数:1人 薪资待遇:10K 转 12K(试用期2个月) 工作时间:9小时;月休4天 性别:不限 年龄:35岁以下 国籍:东南亚国家,华人 地域限制:中国、印尼、斯坦籍、俄罗斯、越南 学历:大专以上 语言需求:中文/英文 流利 岗位要求: 1、财会或经济相关专业或2年以上会计工作经验优先; 2、具有较强的独立学习和工作的能力,工作踏实,认真细心,积极主动; 3、具有良好的职业操守及团队合作精神,较强的沟通、理解和分析能力; 4、公司处于发展阶段,会有加班,接受有会计师事务所经验的。 岗位职责: 1、协助行政后勤审核预算、完成部门预算; 2、协助行政后勤每月请款、冲销、核销、报销; 3、根据部门账目记账做到及时入账、日清月结、按期报帐、账目清楚完整; 4、根据公司规定的成本、费用开支范围和标准,审核原始凭证的合理性和真实性,审核费用是否符合公司规定。

20 Feb 2025, 10:22 UTC799 views1 reactionsread 11 August 2026

综管型人才 专家岗 主管或经理 2人 "招聘渠道:直招/中介/猎头 薪资待遇:3-5w,具体面议 工作时间:10:00-19:00(紧急情况下,需要配合加班) 人选性别:不限 人选年龄:30岁左右 国籍要求:外籍华人 地区限制: 学历要求:不限 语言要求:中英文" "可以是销售型人才、或者互联网企业管理人才,不需要专业对口,要有管理经验、素质高,状态足够好有活力,外向型人选 "1. 协同总监管理,优化后勤行政管理流程,提高人效; 2. 寻找和把控公司场地和宿舍资源合理性; 3. 跟进落实公司合规性要求; 4. 综管成本控制和分析。" "不要有BC行业经验的,英语要特别好的,年龄30岁左右,有过管理经验,最好在大公司呆过 人实在,诚实,能具体去思考和处理问题,沟通和执行能力强,随时响应工作就好" 迪拜/斯里兰卡

1

7 Feb 2025, 13:49 UTC775 views1 reactionsread 11 August 2026

安保 薪资待遇:20000人民币 工作时间:10-7(随时待命) 人选性别:男 人选年龄:35岁以内 国籍要求:中国 工作地点:迪拜 学历要求:无 语言要求:无" 岗位要求: "1.有安保经验; 2.沟通能力强; 3.服从工作安排。" "1.工作纪律检查; 2.处理员工纠纷。"

1

Showing the 12 most recent of 15 posts we hold for @DAZP99. 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 — 590,474 of 1,160,990entries 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 4 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.

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

“婆婆丁” (@DAZP99), 32 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/DAZP99.

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.