Channel
@kebukeyi26
On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
2,588subscribers
+19 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001872100502 |
|---|---|
| Type | Channel |
| Username | @kebukeyi26 |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/kebukeyi26 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 02:17 | 2,588 | +5 |
| 11 Aug 2026, 04:33 | 2,583 | +10 |
| 8 Aug 2026, 06:55 | 2,573 | +4 |
| 7 Aug 2026, 07:16 | 2,569 | first reading |
19 posts held, back to 24 July 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 2 pagesof 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 7 August 2026 |
|---|---|
| Posts held | 19 (24 July 2026 – 7 August 2026) |
| Views total | 11,809 |
| Reactions total | 183 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 16:23 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.
183 reactions across 19 posts, in 11 distinct kinds. The most used accounts for 35.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 65 | 35.5% | |
| 👍 | 53 | 29.0% | |
| 🔥 | 30 | 16.4% | |
| 🤩 | 17 | 9.29% | |
| ❤🔥 | 4 | 2.19% | |
| 👌 | 4 | 2.19% | |
| 😁 | 3 | 1.64% | |
| 🙏 | 3 | 1.64% | |
| 🥰 | 2 | 1.09% | |
| 🕊 | 1 | 0.546% | |
| 😭 | 1 | 0.546% |
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 19 of the 19 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 183reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 24 July 2026 to 7 August 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.
#前端 #web #远程 #长期远程 2️⃣0️⃣2️⃣6️⃣ 🇨🇭🇸🇾🤨🤨 ♈️长期远程♈️长期远程♈️ 🇵🇳（远程办公//不限制地区）🥰🟢 ➡️ ➡️ 急招1名：远程前端工程师 😆 薪资范围：25-30K 左右（具体面谈） 😆 上班时间：8休4（09:30-18:30）午休1小时 😆 试用期间：1-3个月（能力好可提前转正） 😆 办公地点：远程办公//不限制地区 🥰 一、核心职责： • 负责收银台充值/提现核心链路的开发与维护，保障下单、金额、汇率、优惠计算的绝对正确。 • 处理会话生命周期与各类异常（会话过期、令牌失效、解密失败、网络超时）的健壮兜底。 • 维护实时通道（SignalR 重连协商、SSE 订单状态推送）的稳定性。 • 持续优化移动端体验与多机型/多 WebView 兼容性。 • 深度使用 AI 编码工具完成日常开发、重构与测试，并沉淀团队可复用的 AI 工作流（rules / ski…
❤4👍3🔥2🤩1
#运维 #越南 #居家 #远程 2️⃣0️⃣2️⃣6️⃣ 🇨🇭🇸🇾🤨🤨 ♈️越南办公♈️远程居家♈️不压护照♈️ 🇵🇳（远程办公//不压护照//要求人在越南）🥰🟢 🙂🙂 急招一名： 运维工程师 🥰 温馨提示：+ 要求人选在越南，不接收其它地方办公 + 学历要求：大专学历以上 + 年龄要求：38岁以内 ❤️🩹 工作地点：越南居家（远程） ❤️🩹 薪资待遇 : 25K-45K + 绩效 (具体面谈) ❤️🩹 工作时间 : 9休4 单休（需值夜班） ❤️🩹 试用期间：2个月 🇵🇪 岗位职责： 1. 负责公司核心业务系统的部署、监控、维护和优化,确保系统 7x24 小时高可用;通过运维监控工具(如 Zabbix、Nagios、Prometheus 等)对服务器、网络、数据库、应用进行全天候…
❤3👍3❤🔥1🔥1🤩1
#前端 #web #远程 #长期远程 2️⃣0️⃣2️⃣6️⃣ 🇨🇭🇸🇾🤨🤨 ♈️长期远程♈️长期远程♈️ 🇵🇳（远程办公/不限制地区）🥰🟢 🙂🙂 急招1名-远程前端工程师 😆 办公地点：远程办公//不限制地区 😆 薪资范围：20K-30K（具体面谈） 😆 上班时间：9休4 单休 😆 公司项目：游戏项目 😉😉 任职要求： 👉1.5年以上的前端/WEB开发经验 👉2. 熟悉 TypeScript, HTML5、CSS/CSS3、JavaScnipt 物件导向，熟ES5/6/7语法 👉3.熟悉 Vue3 + Vite，掌握 Vue3 生态系，了解并使用Pinia、Vue Router、SPA、SSR 架构 👉4.使用过Node.js、NPM和Webpack且有一定程度的了解 👉5.具备 npm、yarn、pnpm,nvm 操作经验 👉6.具备串接后端 API及 WebSocket经验 👉…
❤4👍4🔥2🤩1
#日本 #横滨 #产品 #运维 #测试 #JAVA #前端 #Cocos 2️⃣0️⃣2️⃣6️⃣ 🇨🇭🇸🇾🤨🤨 ♈️日本/横滨♈️公司包吃/住♈️签证全包♈️ 🇵🇳（公司包食宿//包签证//单人宿舍）🥰🟢 🔥🔥 招聘以下岗位： ➡️ 1.Rust工程师（1名） ➡️ 2.Cocos/前端工程师（2名） ➡️ 3.高级产品经理（1名） ➡️ 4.高级测试工程师（2名） ➡️ 5.运维工程师（3名） ➡️ 6.数据分析（1名） ❤️🩹 **基本要求：所有日本岗位🧮需具有全日制统招本科学历。 ❤️🩹 **签证：日本岗位统一办理日本技术人文签证，公司缴纳雇佣保险+劳灾保险+社会健康保险+厚生年金，有兴趣的欢迎咨询。 🇵🇪 工作地点：日本/横滨 🇵🇪 薪资待遇 : 30K-50K + 绩效 (具体面谈) 🇵🇪 工作时间 : 8休4 单休 🇵🇪 试用期间：2个月 🇵🇪 运营项目：真人娱乐游戏 🧧🧧 福利待遇…
❤4👍3🔥2😭1
#运维 #马来 #吉隆坡 2️⃣0️⃣2️⃣6️⃣ 🇨🇭🇸🇾🤨🤨 ♈️不压护照♈️不压护照♈️ 🇵🇳（宿舍办公/公司包吃住/不禁足）🥰🟢 🙂🙂 急招一名： 运维工程师 🇵🇪 工作地点：马来/吉隆坡 宿舍办公 🇵🇪 薪资待遇 : 30K-45K + 绩效 (具体面谈) 🇵🇪 工作时间 : 9休4 单休 🇵🇪 试用期间：2个月 ✅ 【岗位职责】： 1、负责统筹监控运维工具的自监控告警、故障出来定位工作 2、负责整理监控相关问题，反馈技术研发人员处理，并跟进问题解决过程，形成闭环记录 3、负责统筹监控运维工具的私有化部署工作，负责资源、监控纳管和接入工作 4、负责监控运维工具的异常检测、根因分析、故障自愈、告警收敛等策略的研究与落地 5、负责监控体系的架构优化和智能化监控的建设，提升监控和告警的精确度 6、参与运维工具设计与实施，参与系统架构的可运维性设计 🤔 【任职要求】： 1、大学本科及以上学历，并取得相应学位，…
👍3❤2👌1🔥1🤩1😁1
#产品 #远程 #长期远程 2️⃣0️⃣2️⃣6️⃣ 🇨🇭🇸🇾🤨🤨 ♈️长期远程♈️长期远程♈️ 🇵🇳（远程办公//不限制地区//接受国内远程）🥰🟢 ➡️ 急招2名：资深包网-产品经理（包网项目） ** 1.简历都要附上原型文档（axure, figma(纯AI生成的不行)） ** 2.没有文档的简历直接pass ** 3.学历 : 本科以上 ** 4.熟悉以下业务模块优先： +支付系统（多通道、多币种） +活动与促销系统（Bonus Engine） +渠道与代理分佣体系 +理解海外市场（东南亚/拉美/欧洲等）优先安排面試 😜 工资范围：25K左右（具体面谈） 😜 上班时间：9休4 单休 😜 运营项目：综合包网项目 😜 办公地区：远程办公 //不限制地区 🥰 工作职责： 1. 负责整体产品规划与迭代，包括前台用户端（Web / H5 / App）及后台运营系统 2. 根据业务目标（注册、转化、留存、A…
❤3👍3❤🔥1🔥1🤩1
#测试 #远程 #长期远程 2️⃣0️⃣2️⃣6️⃣ 🇨🇭🇸🇾🤨🤨 ♈️长期远程♈️长期远程♈️ 🇵🇳（远程办公/不限制地区/薪资面谈）🥰🟢 ➡️➡️ 急招2名-测试工程师 【远程】 😆 薪资范围：15K-20K（具体面谈） 😆 试用期间：1-3个月 😆 上班时间：8休4 单休 😆 办公地点：远程办公/不限制地区 😆 运营项目：包网游戏 😉 工作内容: 1. 依产品/专案设计之功能项目，拟定 Test Plan 和设计 Test Case 2. 和相关人员沟通，确认设计、功能需求和规格 3. 进行API测试、功能测试、使用者体验、UI测试、APP测试(ios/Android) 4. 问题回馈、问题追踪，协助各端人员确认 Issue 并加以验证 5. 分析测试结果且清楚回报，协助开发团队解决问题，并持续追踪回归测试 6. 跨部门沟通/合作 确保产品或专案之设计&需求的功能项目正确 😉 加分条件: 1.具备自动化测试工具使…
❤4👍4🔥2🤩1
#GOLANG #远程 #长期远程 2️⃣0️⃣2️⃣6️⃣ 🇨🇭🇸🇾🤨🤨 ♈️远程办公/不限制地区♈️接受国内远程♈️ 🥰🟢长期远程技术🟢长期远程技术🟢🥰 💖💖 急招3名 - GOLANG游戏服务器（纯远程） ❤️🩹 ❤️🩹 急招2名 - GOLANG数据后台 （纯远程） 🇷🇺 ➡️ 注意： + 面试通过后需要提供个人资料，不愿意提供个人资料请勿联系 + 年龄要求：35岁以内（虑到身体素质，年龄是硬性要求） + 学历要求：本科学历以上 📍 办公地点：远程办公/不限制地区 ⭕️ 上班时间：9休4 单休 💵 薪资范围：20K-30K RMB (具体面谈) 💻 每月绩效：海外包网 🔥🔥🔥🔥🔥🔥👌👌 ➖➖➖➖➖➖➖ ⭐️ 热线咨询（24/7 在线）： 👍 👍纸飞机✈️ : @hryuyu26 📢 招
❤3👍3🔥2🤩1
#UI #设计师 #远程#长期远程 2️⃣0️⃣2️⃣6️⃣ 🇨🇭🇸🇾🤨🤨 ♈️长期远程♈️长期远程♈️ 🇵🇳（远程办公//不限制地区//接受国内远程）🥰🟢 ➡️➡️ 急招2名-UI设计师（SLOT/老虎机方向） 🥰🔥 温馨提示：必须要有SLOT/老虎机游戏经验 😆 薪资范围：18K-25K（具体面谈） 😆 试用期间：2个月 😆 上班时间：9休4 单休 😆 办公地点：远程办公/不限制地区 😆 运营项目：SLOT/老虎机 😉 岗位职责： 1.Slot全案UI设计： 负责老虎机项目的整体视觉风格定调，包括游戏主界面、符号（Symbols）、转盘（Reels）、弹窗、结算界面及奖励关卡（Bonus Game / Feature）等全套 UI 设计。 2. 视觉与动效规划： 配合动效设计师或引擎美术，规划 UI 动效、按键反馈及获奖反馈等视觉包装，提升游戏的动感与“爽快感”。 3.设计规范与组件化： 制定规范的 UI 设计…
❤3👍3👌1🔥1🤩1
#测试 #马来 #吉隆坡 #远程 2️⃣0️⃣2️⃣6️⃣ 🇨🇭🇸🇾🤨🤨 ♈️到岗/远程都可♈️到岗/远程都可♈️ 🇵🇳（马来/吉隆坡 或 纯远程 都可以接受）🥰🟢 ➡️➡️ 急招2名： 中高级测试工程师（功能/接口自动化） 🇷🇺 【注意】：（要会自动化测试的，博彩经验。不会自动化的不要） ❤️🩹 工作地点：马来/吉隆坡 或 远程办公 【均可】 ❤️🩹 上班时间：9休4 单休 ❤️🩹 试用期间：1-2个月 ❤️🩹 薪资范围：20K-35K 左右（具体面谈） ❤️🩹 运营项目：包网游戏 🐳 主要职责： • 参与产品需求评审，识别需求风险及测试重点； • 根据需求编写测试方案、测试用例及测试数据； • 负责 Web、H5、后台管理系统等产品功能测试； • 独立完成功能测试、回归测试、兼容性测试及上线验证； • 跟踪 Bug 生命周期，推动问题及时修复； • 输出测试报告，评估版本质量； • …
❤3👍3🔥2🤩1
#运维 #远程 #第三国远程 2️⃣0️⃣2️⃣6️⃣ 🇨🇭🇸🇾🤨🤨 ♈️长期远程♈️长期远程♈️ 🇵🇳（第三国远程//提供房补+餐补//不接受国内远程）🥰🟢 ➡️➡️ 急招1名：高级运维工程师（第三国远程） 🌟 薪资范围：25-35K（具体面谈） 🌟 上班时间：10休6 大小周 🌟 办公场地：远程办公/第三国办公 🌟 运营项目：海外市场 😊 岗位职责： 1.具备操作系统、数据库、网络、服务器硬件等IT基础运维能力； 2.熟练使用Shell/Python 编程语言； .熟悉了解cdn维护和安全规则配置 3.熟悉Docker/k8s容器平台及相关的底层技术和原理者； 4.熟练掌握各种中间件的部署和使用（比如LVS/Nginx/Haproxy/MySQL/DNS/Redis/Kafka/kibana/etcd /Prometheus/Grafana/zookeeper等)； 5.5年以上的云平台运维经验或者IDC运维经验…
❤4👍2❤🔥1👌1🔥1🤩1
#Golang #远程 #长期远程 2️⃣0️⃣2️⃣6️⃣ 🇨🇭🇸🇾🤨🤨 ♈️♈️远程办公♈️不限制地区♈️♈️ 🇵🇳（远程办公//提供房补+餐补//接受国内远程）🥰🟢 ➡️ ➡️ 急招2名远程 - GOLANG工程师（纯远程） 🥰 学历要求：本科学历以上 🥰 年龄要求：40岁以下 🥰 要求：要会 AI编程 vibe coding，能独立处理项目业务 💵 薪资待遇：30K-45K（具体面谈） ⭕️ 试用期：1-3个月 💻 上班时间：10休6 大小周 ✨ 公司项目：海外游戏项目 📍工作地点：远程办公//不限制地区 🤔🤔 职位描述： 1. 三年以上golang开发经验，熟练使用go mod，在sync、sqlx、grpc、fasthttp、gin等关键组件有较深的使用经验 2. 熟悉Linux操作系统及shell脚本语法, 熟悉docker部署技术原理; 3. 熟悉Redis缓存技术 4. 熟悉关系型数据库Mysql、t…
❤3👍2🙏2🔥1🤩1😁1
Showing the 12 most recent of 19 posts we hold for @kebukeyi26. 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,212,006 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.
Named by 2 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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“💋 技术招聘 - YY直招 💋” (@kebukeyi26), 2,588 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/kebukeyi26.
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.