Channel
@BWTYNB
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
769subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003712906826 |
|---|---|
| Type | Channel |
| Username | @BWTYNB |
| Created | Between 1 February 2026 and 16 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/BWTYNB |
Job listings — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 97% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @MLXYZZ/2015 Jun 2026, 00:20 UTC | @BWTYNB/44 · this entry16 Jun 2026, 14:47 UTC | 1.00 | 38 hours |
| @MLXYZZ/2515 Jun 2026, 00:23 UTC | @BWTYNB/49 · this entry16 Jun 2026, 14:47 UTC | 1.00 | 38 hours |
| @MLXYZZ/2615 Jun 2026, 00:23 UTC | @BWTYNB/50 · this entry16 Jun 2026, 14:47 UTC | 1.00 | 38 hours |
| @MLXYZZ/2815 Jun 2026, 00:23 UTC | @BWTYNB/52 · this entry16 Jun 2026, 14:47 UTC | 1.00 | 38 hours |
| @MLXYZZ/2915 Jun 2026, 00:23 UTC | @BWTYNB/53 · this entry16 Jun 2026, 14:47 UTC | 1.00 | 38 hours |
| @MLXYZZ/3115 Jun 2026, 00:24 UTC | @BWTYNB/55 · this entry16 Jun 2026, 14:47 UTC | 1.00 | 38 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @MLXYZZ | 18 (8/8 hand-verifiable sample passed) | 1.00 | 38 hours | @MLXYZZ (18–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 18 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 20 comparable posts for this entry, running 16 June 2026 to 16 June 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 2, the earliest publisher we hold is @MLXYZZ. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 8 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 01:49 | 769 | no change |
| 8 Aug 2026, 01:00 | 769 | first reading |
20 posts held, back to 16 June 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 16 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 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.
马来西亚最新6月岗位需求 推广专员 转化专员 招聘专员 招聘组长 风控专员 高级流量拓展经理 活动策划（中级） 高级活动策划 用户维护（女生/马来籍优先） 运营助理 / 业务跟进助理 平台运营组长 客服专员（5人） 数据专员 部门助理（要求台湾籍） 后勤接待专员 数据分析师 谷歌 SEO 运营专员 百度 SEO 推广专员 出入款专员 总经办助理 组织发展专员 审计 / 账务核查专员（推广板块） 审计 / 账务核查专员（职能板块） 薪酬专员 人事专员 仓储管理员 后勤接待专员 入职联系：A8浪子 @ZPlangzi 更多岗位：@MLXZZZ
后勤接待专员（1名） 优先级 ★★★★☆ 薪资待遇💰 ：12K–15K 工作时间 🕒： 面议 办公地点 📍： 吉隆坡 😊😎😘🙂↔️ 负责来访接待安排与现场协调 负责住宿安排与相关后勤保障 处理日常后勤协调事务，保障办公环境运转 提供行政支持，协助各类活动 / 会议的后勤工作 处理临时性后勤需求 😘😗🤓😗 具备接待 / 行政后勤相关经验 形象气质佳，沟通协调能力强 服务意识强、应变能力好 英文可沟通 国籍要求：限外籍，不招中国籍马来籍
后勤接待专员限外籍 职能岗 优先级 ★★★★☆薪资 12K–15K📍 吉隆坡 KL 岗位职责 负责来访接待安排与现场协调 负责住宿安排与相关后勤保障 处理日常后勤协调事务，保障办公环境运转 提供行政支持，协助各类活动 / 会议的后勤工作 处理临时性后勤需求 任职要求 具备接待 / 行政后勤相关经验 形象气质佳，沟通协调能力强 服务意识强、应变能力好 英文可沟通 国籍要求：限外籍，不招中国籍
数据专员 性别：女 国籍：外籍（马来除外） 语言要求：中文流利 工作时间：10小时，月休4 工作地点：吉隆坡KL 薪资待遇：11000RMB 转正：13000RMB *必须内宿，由公司提供宿舍* 😘😗🤓😗 1、熟练使用Excel表格函数，擅长统计整理数据； 2、具有财务或数据分析工作经验者优先考虑； 3、做事情踏实认真，责任心强，品行端正； 4、思维逻辑清晰，沟通表达能力良好，执行力强； 😊😎😘🙂↔️ 1、按要求整理、检查平台整体各项信息数据； 2、按照固定时间发送当前时间点的平台数据
谷歌 SEO 运营专员 Google SEO · 业务岗 优先级 ★★★★★ 薪资 10K–20K + 提成📍 吉隆坡 KL 岗位职责 负责 Google 自然搜索流量的整体运营与增长，制定并执行 SEO 策略 进行关键词研究、布局与优化，提升目标页面搜索排名与曝光 统筹站内 SEO（页面结构、TDK、内链、收录、技术优化）与站外 SEO（外链建设、内容分发） 监控核心词排名、自然流量与转化数据，定期产出分析报告并迭代优化方案 跟踪 Google 算法更新与行业趋势，及时调整运营策略 任职要求 2 年以上谷歌 SEO / 搜索流量运营经验，有独立操盘流量增长案例者优先 熟悉关键词优化逻辑及站内外流量增长打法 熟练使用 GA4、Google Search Console、Ahrefs / Semrush 等工具 具备较强数据分析能力，能从数据定位问题并提出优化方向 英文可读写（可处理英文资料与内容）
出入款专员 职能岗 优先级 ★★★★☆薪资 面议📍 吉隆坡 KL 岗位职责 负责日常出入款（资金收付）的处理、登记与核对 跟进各渠道入款到账与出款审核，确保资金流水准确及时 负责资金对账、异常款项排查与跟进处理 配合财务 / 风控完成相关数据报表与台账维护 为业务量增长提前储备编制，支撑后续资金处理规模扩张 任职要求 具备资金 / 财务 / 出纳 / 支付结算相关经验 工作细致、数字敏感度高，责任心强 熟悉资金对账流程，具备风险意识 能适应业务量增长带来的工作强度 英文可沟通
总经办助理限外籍 职能岗 优先级 ★★★★★薪资 15K–18K📍 吉隆坡 KL🏢 独立单间办公 岗位职责 协助总经办负责人处理日常行政事务与跨部门协调 负责会议组织、纪要撰写与事项跟进 协助推进重点项目，跟踪进度并反馈 负责费用报销审核与流程跟进 完成领导交办的其他临时性事务 任职要求 学历要求：本科及以上（总经办岗位最低要求） 有业务部门助理 / 总经办助理相关经验优先 熟悉项目管理方法与跨部门协调 熟悉费用报销流程 中文流利（可作为工作语言），沟通表达能力强 做事条理清晰、保密意识强 国籍要求：限外籍，不招中国籍
组织发展专员限外籍 职能岗 优先级 ★★★★★薪资 15K–18K📍 吉隆坡 KL🏢 独立单间办公 岗位职责 负责公司组织架构设计与优化，维护编制管理体系 推进各类管理制度、流程与规范的建设与落地 协助开展组织诊断、岗位梳理与编制核定 维护组织与编制相关数据并输出分析 支持组织发展、人才盘点等专项工作 任职要求 学历要求：本科及以上（总经办岗位最低要求） 熟悉组织架构设计与编制管理 熟悉制度建设与流程梳理 具备较强的数据分析能力 逻辑清晰、文档撰写能力强 国籍要求：限外籍，不招中国籍
审计 / 账务核查专员（推广板块）限外籍 职能岗 · 推广板块 优先级 ★★★★★薪资 15K–18K📍 吉隆坡 KL🏢 独立单间办公 岗位职责 负责推广板块（业务 / 流量投放）相关账务核查与数据核对 复核推广费用、渠道结算与资金流水的真实性与一致性 排查推广板块账务异常与风险点 输出推广板块核查报告，提出整改建议 配合风控完成推广板块专项核查 任职要求 学历要求：本科及以上（总经办岗位最低要求） 具备账务核查 / 审计 / 财务相关经验 熟悉推广 / 渠道费用结算逻辑者优先 熟悉数据核对方法，具备较强风险识别能力 工作严谨、原则性强 国籍要求：限外籍，不招中国籍
审计 / 账务核查专员（职能板块）限外籍 职能岗 · 职能板块 优先级 ★★★★★薪资 15K–18K📍 吉隆坡 KL🏢 独立单间办公 岗位职责 负责职能板块（各职能部门）相关账务核查与数据核对 复核职能板块费用、单据与资金流水的真实性与一致性 排查职能板块账务异常与风险点 输出职能板块核查 / 审计报告，提出整改建议 配合风控完成职能板块专项核查 任职要求 学历要求：本科及以上（总经办岗位最低要求） 具备账务核查 / 审计 / 财务相关经验 熟悉数据核对方法，具备较强风险识别能力 工作严谨、原则性强 英文可沟通（可阅读英文单据 / 资料） 国籍要求：限外籍，不招中国籍
薪酬专员限外籍 职能岗 优先级 ★★★★★薪资 12K–15K📍 吉隆坡 KL 岗位职责 负责员工薪资核算与发放，确保准确及时 负责绩效数据统计与汇总 进行薪酬 / 考勤 / 绩效相关数据的复核校验 维护薪酬相关台账与档案 处理薪酬相关咨询与异常问题 任职要求 具备薪资核算 / 绩效统计相关经验 数字敏感、细致严谨，保密意识强 熟练使用 Excel 及薪酬 / 考勤系统 英文可沟通 国籍要求：限外籍，不招中国籍
人事专员限外籍 职能岗 优先级 ★★★★☆薪资 12K–15K📍 吉隆坡 KL 岗位职责 负责员工花名册与人事档案管理 负责入职、离职、转正、调动等手续办理 维护人员基础数据，确保准确完整 协助考勤、社保等日常人事事务 协助人事相关报表统计 任职要求 具备人事专员 / HR 基础模块相关经验 熟悉入离职管理、档案管理流程 细致、有条理，数据维护能力强 英文可沟通 国籍要求：限外籍，不招中国籍
Showing the 12 most recent of 20 posts we hold for @BWTYNB. 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 — 1,009,656 of 1,151,006entries 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 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.
Names
Channels on the register whose handles appear in this channel's posts.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“A8体育 接团队，接散人，接开云离职，” (@BWTYNB), 769 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/BWTYNB.
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.