此频道 包括 客服号 @ttuu53 被盗 ,请联系新客服 @gmvip123 ,我们的充值方式没有改变 请不要相信旧客服号,请记住新客服号,或者通过网站获取新的联系方式 每一个客户请记住,每一次充值前先看一下网站上面留的联系方式,我们的收款地址不会改变 新的服务更新频道 https://t.me/gmfensi_net

Channel
gmfensi.net更新频道
@likoooyu
On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
1,420subscribers
-11 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001650140691 |
|---|---|
| Type | Channel |
| Username | @likoooyu |
| Created | Between 1 December 2021 and 11 May 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/likoooyu |
Topic
Marketing & affiliate — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 17 September 2026 and assigned it the closest of 31 fixed categories, at 88% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Oct 2026, 14:31 | 1,420 | -1 |
| 27 Sept 2026, 04:20 | 1,421 | -2 |
| 18 Sept 2026, 06:18 | 1,423 | -1 |
| 14 Sept 2026, 11:39 | 1,424 | -1 |
| 5 Sept 2026, 15:21 | 1,425 | -1 |
| 1 Sept 2026, 17:53 | 1,426 | -2 |
| 17 Aug 2026, 20:49 | 1,428 | -2 |
| 11 Aug 2026, 12:23 | 1,430 | -1 |
| 7 Aug 2026, 22:03 | 1,431 | no change |
| 7 Aug 2026, 21:52 | 1,431 | first reading |
Engagement
20 posts held, back to 11 May 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 6 January 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
Twitter服务更新: 服务ID:5322 推文浏览量 100M/天
Tiktok服务更新: 服务ID:5286 Tiktok PK BATTLE POİNTS |即时
ID4709 Twitter 粉丝 快速 无售后 40k/天 ID5285 Twitter 粉丝 快速 无售后 🔥{运行良好} ID4145 Twitter 粉丝 快速 无售后 🔥{运行良好} ID4224 Twitter粉丝30天♻️售后保证 | 阅读服务说明 恢复使用
Instagram服务更新: 服务ID:4428 Instagram 关注 [不掉落] 即时 365天补充按钮 ♻️
ID4147 Twitter 粉丝 |英文资料 |最大 100K 🔥🔥 ID5110 Twitter - 粉丝[中日韩语言装饰]|⚡️1k-5k/天|无售后 ID4287 Twitter粉丝30天♻️售后保证 | 阅读服务说明 恢复使用
ID4390 telegram中文成员 恢复使用
Whatsapp 频道成员 服务ID5284 开始:0–12小时 速度:1k/天 掉落:少掉 补充:无补充 链接:频道链接 注意: ⓵ 链接失效或者修改用户名=订单完成 ⓶ 订单完成速度可以随着服务器负载而上升/下降 ⓷ 在系统中完成订单之前,同一链接请勿在任何地方下第二个订单
全局搜索规则修改后,靠增加普通成员很难出现在搜索,高级会员成员是增加搜索最有效的方式
Facebook服务更新: 服务ID:4631 Facebook 个人资料关注者 {1k-2k/天} [不掉落] 售后30天 服务ID:4012 Facebook 任何类型的页面仅关注 |高速 低掉落 |30天补充装|🔥🚀 服务ID:5084 Facebook- 个人资料粉丝 |质量机器人 |低掉落 |30 天补充 |🔥
Twitter服务更新: 服务ID:5251 Twitter 粉丝0-10分钟开始 | 超快 |无售后 服务ID:5252 Twitter 粉丝0-30分钟开始 | 超快 |无售后 服务ID:5253 Twitter-粉丝0-30分钟开始 | 超快 |15天自动补充 ♻️
Twitter服务更新: 服务ID:4145 Twitter 粉丝 快速 无售后 🔥{运行良好}
Showing the 12 most recent of 20 posts we hold for @likoooyu. 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.
Mentions
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.
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
@likoooyu 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, 8 August 2026 – 8 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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“gmfensi.net更新频道” (@likoooyu), 1,420 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/likoooyu.
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.