Channel
@ly999991
On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
4,702subscribers
-13 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001858473172 |
|---|---|
| Type | Channel |
| Username | @ly999991 |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/ly999991 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 04:13 | 4,702 | -10 |
| 12 Aug 2026, 14:34 | 4,712 | -2 |
| 9 Aug 2026, 10:01 | 4,714 | -1 |
| 9 Aug 2026, 03:45 | 4,715 | first reading |
22 posts held, back to 29 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 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. It is computed over the 1 of 3 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 22 (29 June 2026 – 11 August 2026) |
| Views total | 2,396 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 05:28 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.
6 reactions across 5 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 100.0% |
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 10 of the 22 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 6reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 29 June 2026 to 11 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.
1. 负责公司日常账务处理，包括收入、成本、费用、应收、应付及银行流水核对，确保财务数据真实、准确、完整。 2. 负责月度、季度及年度结账工作，编制资产负债表、利润表、现金流量表及相关财务管理报表。 3. 负责付款审核、费用报销、资金登记、账户管理，以及财务凭证和相关资料的整理、核对与归档。 4. 跟进客户回款及供应商付款情况，维护应收、应付台账，及时识别逾期款项及潜在资金风险。 5. 定期开展收入、成本、费用、利润及现金流等经营数据分析，为公司经营管理及业务决策提供财务数据支持。 6. 协助制定并持续完善公司财务管理制度、费用标准、审批流程及内部控制机制。 7. 配合完成税务申报、年度审计、财务资料整理，以及与外部会计师、税务顾问等专业机构的沟通对接。 8. 负责或协助处理跨境收付款、多币种结算、汇率差异及海外主体相关财务事项。 9. 对接业务、行政、人力及其他相关部门，及时核对业务数据，识别并推动解决日常财务问题。 10. …
❤1
# 高级海外运营（Senior Overseas Operations Specialist） 工作地点： 全球远程（Remote） 工作性质： 全职 ## 岗位职责 * 负责公司海外市场的整体运营工作，制定并执行运营计划，推动业务持续增长。 * 负责海外媒体平台、内容平台、社区平台及其他渠道的日常运营与维护，提升用户活跃度及品牌影响力。 * 根据不同平台及渠道特点，制定内容发布及运营策略，持续优化运营效果。 * 挖掘并拓展海外流量渠道及合作资源，探索新的用户增长机会。 * 负责海外 KOL、Affiliate（联盟合作）、合作伙伴等资源的开发、沟通及维护。 * 跟踪行业动态及竞争产品，分析市场趋势，结合业务发展不断优化运营策略。 * 监控运营数据，分析用户行为、渠道表现及转化效果，并持续优化运营方案。 * 收集用户反馈，与产品、设计、技术等团队保持紧密协作，推动产品持续优化。 * 参与运营活动策划及执行，提高用户获取、留…
📩 投递：@lingying998
Messages in this channel will no longer be automatically deleted
Messages in this channel will be automatically deleted after 1 day
Channel name was changed to «远程工作！»
Channel photo removed
🟠 急缺岗位合集（7-15） P0（紧急）： • AI应用架构师 • SEO助理 • 中高级产品运营 • 产品经理 • 女性向产品中高级运营 • 中级运营（AI短剧制作方向） • 测试工程师（直播/视频方向）🆕 • 中高级产品经理（女性向播放器方向）🆕 P1（中）： • 品牌内容经理 • AI内容编辑（成人） P2（低）： • AI内容编辑 📩 投递：@lingying998
❤1
🟠【急缺岗位合集 · 7-13】—— 47 个 HC · 火热招募中 1️⃣ 高级产品经理 ×2 2️⃣ 高级 UI 设计师 ×1 3️⃣ 中高级运营 ×1 4️⃣ 中级运营专员 ×8 5️⃣ 中级运营专员（SEO 方向）×1 6️⃣ 初级运营专员 ×2 7️⃣ 初级编辑 ×16 8️⃣ 初级资料员 ×5 9️⃣ 资料员 ×8 🔟 AI 应用开发工程师 ×2 1️⃣1️⃣ AI 影像制作师 ×1 💰 面议 · 远程 📩 投递：@lingying998 #招聘 #急缺 #运营 #产品 #UI #AI #编辑
❤1
🔴 【AI 业务分析专员】数据组 · 高优 · 1人 💰 12K-15K/月 🌍 必须人在国外 + 长期远程（国内不考虑） 核心要求： • 2y+ 数据/经营/商业/财务/运营分析经验 • Excel 熟练（透视/函数/多表汇总） • AI 工具实战：ChatGPT / Claude / Kimi / DeepSeek / 豆包 / 通义 / 文心 • 数据敏感 + 业务理解 + 跨时区协作 加分项： • 互联网/游戏/广告/电商/项目制业务背景 • 收入成本 / 充值 / 渠道 / 利润 / 转化漏斗分析 • AI 实战提效案例（Excel 辅助 / 报告撰写 / 模板沉淀） • SOP 搭建 / 团队带教 / 内部培训 岗位职责： • 业务数据整理、统计、分析与输出 • 经营 / 项目 / 成本 / 渠道 / 产品分析 • AI 辅助异常排查 + 团队提效 • 流程优化 + 提示词模板沉淀 + 培训带教 ⚠️ 不接…
🔥 急招·安全运维工程师 (游戏项目) 要找:红方 + SRE 全栈型 ✅ 攻防 / SRC + 游戏项目独立运维 ✅ 云治理 (阿里/AWS/腾讯) + Web 安全基本功 ✅ Shell/Python 自动化脚本 ❌ 别只会扫 / 纯渗透 / 不扛 SRE 🛡 加分:攻防演练 / 推动修洞 / 抗线上 / 风控防刷 📍 远程 / 💰 面议 · 急到岗 📩 投递: @lingying998 #招聘 #安全运维 #红方 #SRE #游戏
🟠 急缺岗位合集(7-07) P0(紧急): • LoRA训练师 🆕 • 中级客服专员 • 中高级网站运营 • 数据挖掘工程师 • 中级运营专员 • 高级产品经理 P1(中): • 中高级产品运营 • 中高级seo运营(策略向) • 国内新媒体运营 📩 投递: @lingying998
Showing the 12 most recent of 22 posts we hold for @ly999991. 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.
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 3 seed channels' Telegram-generated recommendation lists 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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“远程工作！” (@ly999991), 4,702 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/ly999991.
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.