Channel
@vipb99999
On this record: Previous handles · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
4,755subscribers
-7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002523241053 |
|---|---|
| Type | Channel |
| Username | @vipb99999 |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/vipb99999 |
@vipb99999 was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 08:42 | 4,755 | -6 |
| 8 Aug 2026, 04:22 | 4,761 | -1 |
| 7 Aug 2026, 18:02 | 4,762 | first reading |
14 posts held, back to 28 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 5 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 | 14 (28 June 2026 – 7 August 2026) |
| Views total | 10,440 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 17:35 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.
Measured directly from 3 videos 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.
#新型骗局 盘口模式会在各个频道或者其他社交软件使用不同飞机招收：#色盘操作员，找工作对接车队搬砖等，以周结，提成等吸引大家联系咨询。 1:各种飞机发布不直接对接，联系后会先告知联系另外一个人，然后交代具体对接，比如规则，待遇等。说第二天拉群，第三天开始 2:第二天开始拉群，一个车队群，一个盘口群，铺垫群里都是干什么的怎么隔离转发，还有谁是财务什么关系谁是老板等 3:第三天开始，每天他们的运行时间是15:00到21:00，实际盘口工作时间都是15点到半夜15点。因为晚上是骗人招人发布最佳时机，为第二天做准备 4:正式开始后，前几天都很正常，但是第四天或者什么时候在发工资之前，财务就在表演被人把转走了发不了工资和提成，运作不了，群停止运作，让搬砖人失业主动咨询情况。 5:然后侧面吸引我们搬砖人投资几千运作，想的一笔一回没有问题，一旦上压预存达到他们心中金额各种理由开始杀 6:没有意向得就开始引导一起合资等等进行，骗一…
Signed 涉及金额来往请语音呼我 FB
#恒大投稿：大家都管我叫盘总。其实，我不姓盘。在这个地方，有盘口的人，都叫盘总。意思是，我手里管着几百个人的生计，和几千个人的家破人亡。 刚来的时候，他们都说，干完这一票就洗手。后来钱来得太快，洗手盆就再也没装过水。人都脏透了，洗手有什么用？ 风又刮起来了。热带的风，总带着股雨水的腥味。我把烟头扔下去，火星在黑夜里亮了一下，然后彻底灭了。我知道，我也快灭了。 关注许家印频道➡️
Signed 涉及金额来往请语音呼我 FB
#群友爆料：从三月份合作到五月份六月初开始催账一直到七月份没得到结账，到现在群退了记录互删了。前面讲故事找理由拖着后来没办法拖了直接摆明不结账了3520u共计。 图中（高进）为他们老板集团负责人。其他的都是小马仔负责拿号上号，途中听他们老板说中途电脑中毒病不知是真还是假退出了群聊， 到现在一直没得到结账据小道消息他们盘踞在妙瓦底恒生园区拖欠物业费水电费，一个月FB只有几千u业绩完全不够支撑开销。不结账的话后续继续爆料。。。。。。 🤣 缅甸大事件： @VTTTT 投稿： @sssi8
Signed 涉及金额来往请语音呼我 FB
（1）刚刚购买的账号第1天不推荐加人，必须养好IP才能去加好友。加好友也不能太快，不要加的太多，否则账号用不了多长时间。 （2）如果要加5个人，每加1个人，就需要点1个赞，加1个群组 【看个短视频、看直播、浏览帖子、分享帖子、首页点击游戏/招聘求职/天气等模拟真实人工操作，这几个分类任意选择2到3个浏览即可】。 （3）加了下一个人之后，接着反复操作【看个短视频 、流量帖子、 分享帖子、 首页点击 、游戏、 招聘求职 、天气等等模拟真实人工操作，这几个分类随意选择2到3个浏览】直到加完5个好友为止，循环操作几次可以加几十个人。 （4）在登录账号的设备未活跃之前不要加过多好友，每天在20到30个左右即可。后续账号活跃可以逐步加量。必须养号1-2天左右时间再使用做业务！登录后不要进行以下操作：修改密码、修改资料、换绑邮箱。必须等待3天之后才可修改。纯挂机什么都不操作并不算养号，正确养号方式是：有日常行为操作，比如浏览帖子、点赞等。 （…
Signed 涉及金额来往请语音呼我 FB
供应商品：📢 所有账号都是源头直出！没有中间商倒腾差价，纯纯底价冲量🔥 🔥 自选号现货热销，及选及发！ 🗳FB号：热门地区：美国、中国台湾、中国香港、马来西亚、韩国 大量上新 优势：原生养号IP，高权重易养号，适合精准引流不易封号 📷INS号 ：INS粉丝号、INS帖子号、热门国家、随机国家、风景、美食号等自选老号 ❌推特号：香港、新加坡、日本、台湾、泰国、法国、英国、随机国家等自选老号 FB售后：48小时内密错找回 168小时内出现锁号联系客服进行辅助解锁（未成功解锁不做补号处理） 推特/INS：24小时内密错找回 😅最新库存已更新 提货联系 ☔️恒大-许家印 @vip88k88 🕒在线时间：12:00 - 次日 04:00（全天候响应库存查询 / 选号需求 商品介绍：Fb IG 推特X账号 价格： 白菜价 联系人： @VIP8888888888888888888888888888a 产品频道：https:…
Signed 涉及金额来往请语音呼我 FB
登录微软邮箱（Hotmail、outlook）接码，个别人会反馈说收不到验证码，其实是没有找到。请分别点击Focused（重点）和Other（其他）进去看看。这是两个不同的邮件分类，接收到的邮件不在这个分类中，就在另一个分类中。偶尔还可能出现在垃圾邮件这个文件夹中（比较少见）。
Signed 涉及金额来往请语音呼我 FB
facebook服务器被攻击，全球用户都无法登录。 【时间】：2026年07月19日15：50
Signed 涉及金额来往请语音呼我 FB
Fb又又又又又罢工了。等待维护中📢
Signed 涉及金额来往请语音呼我 FB
个号最新跳电话认证 WS 解决方法 auth.meta.com 个号打开这个网址 Fb登录 如果出现提出抗议你就点抗议，上传大头照。有的不需要上传。点到最后刷新就出邮箱接码。绕过WhatsApp 手机验证 了
Signed 涉及金额来往请语音呼我 FB
#缅甸新闻：星链服务即将受限 缅甸用户仅剩约30天使用期 服务商消息显示，缅甸目前广泛使用的星链卫星网络，从7月17日起预计只能再使用约30天，使用期限可能在8月16日结束。 根据星链最新政策，设备在注册国家或地区以外连续使用30天后，账户必须切换到当前所在的国家或地区。 由于缅甸目前尚未正式批准星链服务，大量在其他国家注册、但长期放在缅甸使用的设备，下个月可能会被限制或直接停用。 服务商透露，目前暂时没有可以继续长期使用的替代方案。后续资费还可能改为按流量计算，每1吉字节约需9000缅币。 按照新规定，用户还需要使用护照完成旅行登记。如果没有完成相关登记，账户可能会被限制，设备也可能被锁定。 实皆省、掸邦等长期断网或网络不稳定的地区，一直有不少居民和商户依靠星链保持网络连接。 此外，缅甸边境部分诈骗团伙也开始大量使用星链设备，这一情况也让相关政策进一步收紧。
Signed 涉及金额来往请语音呼我 FB
#网友投稿：钱是挣不完的，身体才是自己的。我现在上班已经进入圣人模式了，每天主打一个随缘办公。 早上先泡杯咖啡，点根烟，吃两包榔子，跟同事从国际局势吹到隔壁组谁昨晚又去会所，客户消息？让它先飞一会儿。领导路过我工位，我还顺手给他递根烟，气场这一块拿捏得死死的。 主管从来不管我摸鱼。为什么？因为我业绩牛逼。我就是组里的六边形战士，别人靠加班，我靠天赋。真把我惹急了，我直接把工牌往桌上一拍："你今天敢说我一句，我明天就让同行多个销冠。"整个办公室瞬间安静，连空调都不敢出风，CPU当场干冒烟。 同事私底下都喊我园区战神，老板见了都得跟我握手，开会让我站C位，月底奖金都是按麻袋发，公司没我，明天直接宣布停服维护。 …… 好了，先暂停一下。 刚刚是我大脑为了保护我，自动开启了《幻想模式》。 现实是我这个月到现在一单没开，后台比我的钱包还干净，主管已经站我后面看了五分钟，我愣是没敢回头。 刚准备再摸会儿鱼，肩膀突然被拍了一下。 …
Signed 涉及金额来往请语音呼我 FB
FB账号售前说明： 所有FB，建议不要挑选太过活跃的号，容易被找回，造成损失。越活越的号找回概率越大。个人建议选择半年内没有动态的号，找回几率大大降低。 售后时间只有24小时，超过24小时后，我们只能尽全力帮助您找回，不能保证一定能找回。 自选的所有账号因为本来就是盗来的真人号，不要纠结会不会被盗走，机率肯定是有的，风险自担。 要想完全不被盗走的话，建议使用白号即可。 ———————————————————————— FB账号登录方法： 1.务必使用对应地区的IP（能最大程度减少锁号几率），必须使用mbasic.facebook.com 或者 手机APP 或者 cookie登录，而不是www.facebook.com，否则账户将被验证 2.获取双重验证码，将整串密钥复制粘贴到 2fa.vip 去提取验证码，验证码有效期为30秒钟 3.登录成功后至少等待两分钟，然后在新页面打开 www.facebook.com即…
Signed 涉及金额来往请语音呼我 FB
Showing the 12 most recent of 14 posts we hold for @vipb99999. 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 — 599,554 of 1,151,006entries 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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“恒大-许家印 FB / ins / line / TikTok” (@vipb99999), 4,755 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/vipb99999.
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.