上班吃着水果赚着钱,享受😎

Channel
🔥集团|直聘🔥
@kuluze88
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
6subscribers
-1 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 | -1001740898413 |
|---|---|
| Type | Channel |
| Username | @kuluze88 |
| Created | Between 1 October 2021 and 27 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/kuluze88 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 08:08 | 6 | -1 |
| 12 Aug 2026, 18:17 | 7 | no change |
| 7 Aug 2026, 10:30 | 7 | first reading |
Engagement
17 posts held, back to 27 October 2021 — 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 17 posts for this entry, the most recent from 23 June 2023. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 24s
- Average length
- 24s
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.
Recent posts
叶叶层叠,好运不绝; 米米紧粘,幸福绵绵; 线线缠绕,快乐拥抱; 水水相融,情意浓浓; 粽粽连结,祝福不歇! 集团㊗️您端午节安康,幸运伴赢🏆
❤️❤️❤️ 冬至到了,天气寒冷,我以关心为灶,以健康为锅,以真情为火,以好运为皮,以温暖为馅,以祝福为水,专门为你做一份“幸福如意”饺子汤,㊗️你冬至快乐,阖家温暖幸福!
❤️❤️面试前的注意事项❤️❤️ 1️⃣ 提前做好面试计划和准备工作 2️⃣ 选择合适的环境,检查网络,避免周围嘈杂,确保通话质量 3️⃣ 注意形象 4️⃣ 保持冷静和自信 5️⃣ 回答问题尽量语速均匀,避免和面试官抢话,吐字清晰,语言流利,既显得有礼貌,又可以展示你对公司、职位的兴趣和热情 6️⃣ 对问题给出积极的答案,展现出积极地工作态度 ☘️ 也许你没有相关岗位经验,但是你可以展示你一定是最合适的。你要把握住面试中的每一分每一秒运用每一个回答告诉面试官,你一定可以胜任这个职位。💪💪💪 ☘️ 如果有相关岗位的经验,就要自信地把一个专业度和匹配度表达出来,有一定的谈薪技巧,以寻求更高的薪资。🎉🎉🎉
客服联系方式: @kuluze1
⚽️热门在招岗位,点击蓝色字体即可跳转岗位简章🏀 招聘专员 招聘组长-主管 推广专员 电销专员 体育主播 人事助理 维护专员 培训专员 IOS开发工程师 SEM 产品经理 Android开发工程师 白帽SEO 黑帽SEO 渗透劫持 PHP工程师 自媒体运营 部门助理 总监助理 数据分析师 转化专员 java工程师 后勤专员 行政专员 客服专员 视频编辑 财务助理 Linux运维 推广组长 …
🌈【集团菲柬迪岗位简介】温馨提示:点击蓝色字体即可跳转 公司简介 福利待遇 办公环境 宿舍环境 入职流程 伙食菜单 水果饮料 隔离环境 客服联系
直聘联系方式: @kuluze1
酒店隔离环境,每日提供工作餐,零食,矿泉水
岗位:运营主管 薪资待遇:面议 1.针对客服、运营经验者优先; 2.至少1年以上管理经验; 3.熟悉BC类产品的各个玩法规则及话术使用; 4、有manila地区工作经验优先; 5、熟悉Excel、PPT、Word等办公软件(要非常熟悉EXCEL操作); 6、为人踏实肯干,认真负责,抗压力强。 岗位职责: 1、负责平台日常运营工作,负责平台数据实时统计与实时反馈,负责处理线上运营业务等。 2、负责完成团队的管理; 3、负责根据上级的要求制定工作计划; 4、监督各组工作的完成。
岗位:代理电销组长 薪资待遇:15000RMB-25000RMB 工作时间:10小时,月休4 岗位需求: 1.有销售或BC行业经验; 2.带代理资源者优先; 3. 思路清晰,逻辑清楚,口齿清楚; 4. 有BC行业管理经验; 岗位职责: 1、 执行电话销售任务,通过大量的拨打电话,开发玩家成为公司的代理 2、维护促使代理邀请身边的玩家,或者通过其他渠道邀请玩家到公司网站游戏; 3. 管理电销组员工,收集每日组员数据并上报; 4. 解决客户的各种疑问并达成合作意向; 5. 维护已开发客户关系,提高客户满意度。
岗位:代理发展组长 薪资待遇:15000RMB-25000RMB 工作时间:10小时,月休4 岗位需求: 1.有销售或BC行业经验; 2. 带代理资源者优先; 3. 思路清晰,逻辑清楚,口齿清楚; 4. 有BC行业管理经验; 岗位职责: 1、负责日常网站代理招募,开发新渠道开发新代理; 2. 负责日常网站代理的维护工作; 3.收集、反馈网站代理的意见,协助他们处理问题; 4.制定代理优惠活动,帮助代理进行推广; 5.管理发展组成员,进行工作任务的分配;
Showing the 12 most recent of 17 posts we hold for @kuluze88. 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,399,126 of 1,481,306entries 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@kuluze88 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 13 August 2026 – 13 August 2026
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“🔥集团|直聘🔥” (@kuluze88), 6 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/kuluze88.
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.