Channel
@pbcomviccycompany
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
77subscribers
-1 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001776844627 |
|---|---|
| Type | Channel |
| Username | @pbcomviccycompany |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 3 times, most recently 18 September 2026 |
| On Telegram | t.me/pbcomviccycompany |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Sept 2026, 10:07 | 77 | -1 |
| 11 Aug 2026, 13:00 | 78 | no change |
| 11 Aug 2026, 12:49 | 78 | first reading |
20 posts held, back to 18 November 2023 — 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 page of 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 13 May 2026. An engagement rate over an empty window would be a number about nothing.
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.
13 reactions across 8 posts, in 6 distinct kinds. The most used accounts for 38.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5 | 38.5% | |
| 🔥 | 2 | 15.4% | |
| 🤩 | 2 | 15.4% | |
| 🥰 | 2 | 15.4% | |
| 👍 | 1 | 7.69% | |
| 👏 | 1 | 7.69% |
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 9 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 13 reactions 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 18 November 2023 to 13 May 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、协助优化平台运营流程，提高整体运营效率及质量。 岗位要求： 1、有质检、审核、运营或相关工作经验； 2、工作细致认真，责任心强，具备较强执行力； 3、具备良好的沟通协调能力及团队协作意识； 4、有客服质检、流程审核或社媒运营经验者优先； 5、有博彩、游戏或互联网平台相关经验者优先。 联系方式TG ：@allysaaa21
【运营专员（风控方向）】 岗位职责： 1、负责平台日常风控运营工作，对接风控部门； 2、复查每日风控报告，跟进异常账号及异常资金情况； 3、针对平台刷子、套利、羊毛党等异常行为进行分析与处理； 4、协助完善平台风控规则及审核机制； 5、监控平台风险数据，降低平台运营风险及损失。 岗位要求： 1、有相关风控经验，熟悉博彩或互联网平台风控逻辑； 2、具备较强的风险意识及数据判断能力； 3、能够独立分析异常用户行为； 4、责任心强，做事细致认真； 5、有博彩平台风控经验者优先。 联系方式TG ：@allysaaa21
【运营专员（数据分析方向）】 岗位职责： 1、负责平台日常运营数据统计与分析，包括活动数据、用户数据、留存数据、充值提现数据等； 2、针对平台运营情况进行数据复盘，发现问题并提出优化建议； 3、跟踪活动效果，分析活动ROI及用户转化情况； 4、配合运营团队制定数据化运营方案，提高平台整体运营效率； 5、定期输出数据分析报告，为运营决策提供支持。 岗位要求： 1、有数据分析相关经验，对数据敏感； 2、熟练使用Excel等数据工具，有较强的数据整理及分析能力； 3、逻辑思维清晰，具备较强的问题发现与解决能力； 4、有博彩、游戏、互联网平台运营经验优先； 5、责任心强，执行力高，具备团队协作能力。 联系方式TG ：@allysaaa21
数据分析 岗位描述: 负责墨西哥站用户行为、营收与市场数据分析，通过数据驱动产品优化、用户增长及市场策略制定。此岗位将与市场、运营及产品团队紧密合作，以提升留存率、转化率及ROI等核心指标 岗位职责/Job Responsibilities: ✅数据监控与分析 -定期输出市场及运营报表，发现异常波动并提供改进建议。 ✅产品与体验优化支持 -根据数据洞察提出产品改进建议（UI流程、功能优化、支付路径等）。 ✅用户行为分析 -分析玩家的注册来源、充值路径、留存与流失特征； -建立用户分群模型（高价值用户、潜在流失用户等），提供精准运营建议。 ✅活动与投放效果评估 -跟踪市场活动及广告投放数据（Facebook、Google、TikTok、联盟渠道等）； -评估ROI与用户质量，为市场团队优化预算分配与投放策略提供数据支持。 ✅跨部门协作与数据支持 -为市场、客服、运营团队提供定制化数据报表与可视化分析； -支持管理层战略…
❤1
用户运营 岗位描述: 负责墨西哥站用户的全生命周期运营工作，通过数据分析、市场洞察和本地化活动策划，提升用户留存、活跃和付费转化率。推动平台在墨西哥市场的用户增长与营收提升。要求对用户行为有一定了解，具备海外运营经验或本地化思维。 岗位职责/Job Responsibilities: ✅用户增长与留存 -规划墨西哥市场的用户增长与留存策略，优化新用户注册、活跃与复存路径； -建立用户分群模型（高价值用户、潜在流失用户等），提供精准运营建议。 ✅活动策划与执行 -根据当地节日与热点（如Cinco de Mayo、Dia de los Muertos等）策划线上活动，提高用户参与度与品牌曝光； -与市场、设计、客服团队协作，推进活动上线、复盘与优化。 ✅用户关系维护 -与社群伙伴协作，负责墨西哥地区玩家社群（WhatsApp、Facebook、Telegram、论坛等）的日常运营与内容输出； -处理用户反馈与投诉，协助客服团…
游戏运营 岗位描述: 负责平台整体游戏内容运营与管理，包括三方游戏供应商接入、前端游戏展示布局、游戏上架规划以及墨西哥本地热门游戏趋势调研分析。通过精细化内容运营与数据监控，提升平台游戏曝光度、点击率、用户留存与营收表现。 岗位职责/Job Responsibilities: ✅对接三方游戏供应商 -跟进新游戏上线、测试、验收及后期性能监控； -建立并维护供应商档案，定期评估其游戏表现与收入贡献； -协助商务部门完成新供应商引入与游戏上架流程。 ✅游戏内容规划上架与布局设计 -负责游戏上架前的测试，负责平台首页、二级页面、分类页的游戏布局与内容优化； -根据数据分析与玩家偏好，动态调整推荐位、banner、主题专区； -定期检查游戏可用性、加载速度与兼容性问题； -跟进游戏下线、维护、版本更新与异常修复； -优化用户浏览与转化路径，提高点击率与停留时长。 ✅本地市场调研与游戏趋势分析 -深入研究墨西哥玩家偏好、热门类型与…
❤1
活动运营 岗位描述: 负责公司线上及线下活动的策划、执行与复盘，确保活动既有效果又安全合规。通过活动提升品牌曝光度、用户参与度与转化率。需具备良好的活动策划能力、项目统筹能力、数据分析思维及跨部门协作能力。 岗位职责/Job Responsibilities: ✅活动策略制定与策划 -根据公司整体运营目标及用户增长策略，制定年度、季度、月度活动规划； -独立策划线上（站内活动、社群活动、直播活动）及线下（如发布会、展会、地推活动）方案。 ✅活动创意与内容输出 -负责活动主题、文案、视觉概念、互动玩法的创意策划； -能根据用户特性和品牌调性输出具有吸引力的活动内容。 ✅活动数据监控与分析 -负责活动数据指标的设定（参与人数、留存率、转化率、ROI等）； -通过数据分析优化活动策略，总结经验形成可复制的活动模型。 ✅用户洞察与需求分析 -定期调研用户偏好、反馈与市场动态； -基于用户画像与生命周期，策划差异化活动方案。 …
Channel name was changed to «亚美尼亚技术公司»
愿您的生活像摇一摇，无忧无虑无烦恼 36小时 on call~~
❤1🥰1
以真心为叶，包裹真诚；以诚心为馅，塞满祝福；以关心为线，捆住健康。祝端午安康！🥰🥰
❤1🥰1
来吧，有岗位需要人啦😘
👏1🤩1
Photo, posted without a caption
🔥1🤩1
Showing the 12 most recent of 20 posts we hold for @pbcomviccycompany. 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.
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.
@pbcomviccycompany 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.
References a handle that is not a live channel — we have no record it ever was one.
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 3 September 2026 — this entry's latest reading, not the date you are reading this.
“亚美尼亚技术公司” (@pbcomviccycompany), 77 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/pbcomviccycompany.
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.