Channel
@feilvbing111
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
26subscribers
+5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003097239094 |
|---|---|
| Type | Channel |
| Username | @feilvbing111 |
| Created | Between 1 August 2025 and 9 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/feilvbing111 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 11:08 | 26 | +2 |
| 22 Aug 2026, 18:54 | 24 | +2 |
| 15 Aug 2026, 17:23 | 22 | +1 |
| 11 Aug 2026, 14:32 | 21 | no change |
| 7 Aug 2026, 10:17 | 21 | first reading |
20 posts held, back to 9 September 2025 — 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.
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 2 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 20 (9 September 2025 – 5 August 2026) |
| Views total | 64 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 14:32 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 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 1 of the 20 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 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 9 September 2025 to 5 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.
菲律宾马尼拉，要外籍行政。 GW： 24H综合专线专员 （3名） XZDY：10k-12k GZSJ： 9小时，月休4（三班倒） XB： 不限 NL： 21-32 GJ： 不要中国籍 YYXQ： 中文 GZDD：PH （MNL） GWXQ： 1、性格秉性要正直，诚实，踏实做事； 2、基础办公软件要会操作 3、英文可基本沟通交流 4、热爱服务行业，自己未来的职业发展规划清晰； 5、做事认真，热情，乐于帮助别人； 6、无不良嗜好及违背公司底线等黑名单历史； GWZZ： 1、在线解决员工遇到的一切问题，耐心细心来完成所分配的工作，与各班次同事做好交接，实时跟进问题并及时解决； 2、各班次聊天记录互相传阅，取其精华，弃其懵柏，学习提升个人话术使用能力； 3、员工领取各类申请表格，文件打印，方可接待，协助员工解决问题； 4、知识和技术要求：WORD和EXCEL非常熟练，打字速度50以上。
❤1
菲律宾马尼拉，要外籍行政。 GW： 24H综合专线专员 （3名） XZDY：10k-12k GZSJ： 9小时，月休4（三班倒） XB： 不限 NL： 21-32 GJ： 不要中国籍 YYXQ： 中文 GZDD：PH （MNL） GWXQ： 1、性格秉性要正直，诚实，踏实做事； 2、基础办公软件要会操作 3、英文可基本沟通交流 4、热爱服务行业，自己未来的职业发展规划清晰； 5、做事认真，热情，乐于帮助别人； 6、无不良嗜好及违背公司底线等黑名单历史； GWZZ： 1、在线解决员工遇到的一切问题，耐心细心来完成所分配的工作，与各班次同事做好交接，实时跟进问题并及时解决； 2、各班次聊天记录互相传阅，取其精华，弃其懵柏，学习提升个人话术使用能力； 3、员工领取各类申请表格，文件打印，方可接待，协助员工解决问题； 4、知识和技术要求：WORD和EXCEL非常熟练，打字速度50以上。 @gc18888
菲律宾2026-07-26最新岗位: 招聘专员 RZ 档案信息组 接机专员 ZJB专员 （GD专员） 维护专员 业务支持 推广专员 平面设计 客户关系发展 品牌部专员 业务拓展 人事行政 客服服务专员 信息管理专员 共享服务专员 薪酬专员 网管IT专员 高级网络工程师 初级系统工程师 初级网络工程师 高级云桌面系统工程师 行政前冶 行政后勤 财务经理或主管 转账及报表专员 换汇报表专员 会计专员 技术总监 测试总监 服务端开发 高级Java开发 运维总监 运维经理 中/高级/资深运维工程师 运维安全工程师 (偏审计合规） 运维安全专家/总监 高级DBA DBA值班 DBA 经理 DBA主管 安全产品经理 运维值班组长 运维值班 产品经理(运维安全平台方向) 测试工程师(安全 / 平台方向) 行政职能 财务专员 DC专员 薪酬组长 资金专员 资产调配专员 资产专员 采购专员 投诉专员 部门助理 Department Assist…
#新增第三国需求 🇹🇭 AG尊龙 泰国外宿居家办公： #岗位名称：市场推广 #年龄限制：18-36岁（超过年龄不予考虑） #工作时间：10小时,月休6天 #工作地点：菲泰国曼谷🇹🇭 #薪酬福利：试用期1,440USD +提成，转正1,800USD +提成 #餐补房补：房补340USD/月，餐补200USD/月 #入职要求：外宿居家办公，须自备电脑设备，入职需要提交护照原件 ⚠️特别注意：比较倾向于在曼谷直接可以现场面试的人选，不接受线上面试。 职位要求/Job Requirements: 1. 需要自己寻找资源、渠道，了解个人推广方法及拥有个人优质代理资源、优质客户的优先 2. 有一年及以上经验推广/招商经验者，不要没经验/小白勿扰 3.善于沟通，情商高，心态积极，具备一定的抗压能力 4.没有相关行业经验、行业小白等勿扰 @gc18888 @gc18888 @gc18888
十二月重点岗位。 岗位 ： 客服维护 性别 ： 不限 年龄 ： 21-33 国籍 ： T ✅只要大陆、台湾、马来、越南 ❎缅甸等其他所有国籍 D ✅大陆、台湾、其它所有国籍 *避开斯坦籍、俄罗斯籍、蒙古籍、新疆籍 菲律宾。斯里兰卡。 ✅大陆、台湾、其它所有国籍 语言要求 ： 中文流利 薪资待遇 ： 试用期两个月，试用期10000+转正绩效提成 工作时间 ： 9小时，月休4（倒班） 工作地点：泰/菲（KJY）/斯里兰卡 岗位需求 ： 1. 中文沟通无障碍，普通话流利，理解能力强；中籍: 要求大专以上学历，外籍：要求本科以上学历 2. 良好的沟通表达能力、情绪管理能力和抗压能力，团队协作能力强； 3. 热爱游戏，能快速了解客户心理和游戏需求； 4. 接受轮休和排班 5. 电脑操作打字熟练，掌握基础操作办公软件； 不接受推广类岗位经验 有维护经验，如电销、电维，客户维护，客服等经验皆可 岗位…
🌈🌈🌈九月菲律宾招聘岗位大全目录： https://t.me/feilvbing111/74 https://t.me/feilvbing111/75 🌈🌈🌈急招岗位： 🌈【职位： 签证组长 急招 】 🌈【职位： 信息管理专员 急招 】
🌈【职位： 签证组长 急招 】 ■ 薪酬待遇：转正后25K+绩效，加全勤 500 ■ 工作时间：9 休 4 ■ 工作地点：菲律宾 ■ 国籍要求：外籍 🌈【岗位要求】 "有丰富的签证、护照管理经验 熟悉菲签证政策，办理流程 完成领导交办任务" 🌈【岗位职责】 "管理员工的签证、护照 办理、处理员工的签证 管理签证组" 咨询对接。 —— @gc18888 返回岗位首页。—— @gongchuangkeji1。
🌈【职位： 信息管理专员 急招 】 ■ 薪酬待遇：10-15K+绩效1K-5K，加全勤 500 ■ 工作时间：9 休 4 ■ 工作地点：菲律宾 ■ 国籍要求：外籍 🌈【岗位要求】 "1、管理护照，收取护照，编辑护照页码，归类签证类型，签证时间 2、帮助员工续签，办理签证。递交材料 3、及时进行各场地人事信息、数据、档案的管理维护，确保信息有效，数据准确、档案健全； 4、协助上级跟进其他工作事项。" 🌈【岗位职责】 "1. 女孩子优先 2. 具备基础办公软件使用能力，熟练使用EXCEL； 3. 态度亲和，有耐心，服从上级安排与工作调配； 4. 中英文沟通无障碍，工作细心有耐心，听从上级工作安排，有签证经验者优先。" 咨询对接。 —— @gc18888 返回岗位首页。—— @gongchuangkeji1。
九月菲律宾招聘岗位大全第二部分： 🌈【职位： "单据专员 " 】 🌈【职位： 运营客服 】 🌈【职位：技术总监 】 🌈【职位："自动化/功能测试工程师 （测试开发）" 】 🌈【职位： 高级产品经理 】 🌈【职位： 技术支持 】 🌈【职位： 运维总监 】 🌈【职位： 高级业务运维工程师 】 🌈【职位：高级网络工程师 】 🌈【职位： 高级DBA运维工程师 】 🌈【职位：高级技术运维工程师 】 🌈【职位：信息安全工程师 】 🌈【职位： 项目经理 】 🌈【职位： 投诉专员 】 🌈【职位：渠道招商人员 】 🌈【职位： 总监助理 】 🌈【职位： 资金专员 】 🌈【职位： 审计专员 】 🌈【职位： 资产调配专员 】 🌈【职位： 资金专员 】 🌈【职位： 财务专员 …
九月菲律宾招聘岗位大全第一部分： 🌈【职位： RZ 账目 】 🌈【职位：接机专员 】 🌈【职位： 数据分析专员 】 🌈【职位：劳动关系专员 女 】 🌈【职位：医生 】 🌈【职位： 护士 】 🌈【职位： 综管专员 】 🌈【职位： 数据分析专员 】 🌈【职位： 部门助理 】 🌈【职位： 运营专员 】 🌈【职位： 红利专员 】 🌈【职位： 敏感信息专员 】 🌈【职位："大数据工程师 外籍大数据工程师" 】 🌈【职位： "DBA工程师 外籍DBA工程师" 】 🌈【职位： 薪酬专员 】 🌈【职位：行政专员 】 🌈【职位： 运维工程师 】 🌈【职位： 高级网络工程师 】 🌈【职位： 运维域名工程师 】 🌈【职位： 桌面运维 】 🌈【职位：安全工程师 】 🌈【职位： 运维…
🌈【职位： 财务专员 】 ■ 薪酬待遇：1390U转1690U ■ 工作时间：9小时 ■ 工作地点：菲律宾 ■ 国籍要求：外籍 🌈【岗位要求】 "1. 按公司财务部要求及部门内部流程，处理部门财务相关工作；有财务相关工作背景佳； 2. 擅长与人沟通，对于跨部门保持乐观、积极的心态，善于与人交流并且确保沟通顺畅、能将部门政策及上级要求传达到位； 3. 熟知资产部各项流程、政策，并确实保证能按部门规定执行工作； 4. 对于财务、数据统计有相关经验，且对于数字有敏锐的洞察力； 5. 细心、负责有上进心； 6. 工作地点: PH (后期依公司政策，可能有需要配合部门调派到第三国) 。" 🌈【岗位职责】 咨询对接。 —— @gc18888 返回岗位首页。—— @gongchuangkeji1。
🌈【职位： 资金专员 】 ■ 薪酬待遇：1800-2000u左右 ■ 工作时间：9小时 ■ 工作地点：菲律宾 ■ 国籍要求：外籍 🌈【岗位要求】 员工具有一定的金融学知识，有金融支付方面的工作经历者优先，为人真诚，性格和善，服从性高，如在菲不可有签证问题，善于沟通交流 🌈【岗位职责】 负责财务部门报表，资金管理，支付等工作，完成上级安排的任务 咨询对接。 —— @gc18888 返回岗位首页。—— @gongchuangkeji1。
Showing the 12 most recent of 20 posts we hold for @feilvbing111. 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 — 551,225 of 1,628,927entries 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“菲律宾岗位🇵🇭” (@feilvbing111), 26 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/feilvbing111.
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.