HoaVi.P 🇻🇳 pinned Deleted message

Channel
HoaVi.P 🇻🇳
@appfrevip
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Handles named that no longer answer · Cite this entry
1,320subscribers
-32 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 | -1002284372182 |
|---|---|
| Type | Channel |
| Username | @appfrevip |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/appfrevip |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 21:46 | 1,320 | -5 |
| 23 Aug 2026, 19:58 | 1,325 | -2 |
| 20 Aug 2026, 12:54 | 1,327 | -4 |
| 17 Aug 2026, 22:03 | 1,331 | -6 |
| 14 Aug 2026, 11:46 | 1,337 | -8 |
| 10 Aug 2026, 18:07 | 1,345 | -5 |
| 8 Aug 2026, 00:24 | 1,350 | -2 |
| 7 Aug 2026, 22:21 | 1,352 | no change |
| 7 Aug 2026, 16:05 | 1,352 | first reading |
Engagement
19 posts held, back to 14 April 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 1 pageof 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 19 posts for this entry, the most recent from 20 July 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 56s
- Average length
- 56s
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.
Reaction mix
721 reactions across 16 posts, in 13 distinct kinds. The most used accounts for 16.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🎉 | 117 | 16.2% | |
| 🔥 | 102 | 14.1% | |
| 🤩 | 88 | 12.2% | |
| 👍 | 65 | 9.02% | |
| 💯 | 65 | 9.02% | |
| 🥰 | 65 | 9.02% | |
| ❤ | 48 | 6.66% | |
| ❤🔥 | 43 | 5.96% | |
| 😍 | 41 | 5.69% | |
| 🤣 | 30 | 4.16% | |
| 🤔 | 21 | 2.91% | |
| 😢 | 18 | 2.50% | |
| 🤮 | 18 | 2.50% |
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 16 of the 19 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 721reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 14 April 2026 to 20 July 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.
Recent posts
HoaVi.P 🇻🇳 pinned Deleted message
We've moved to a new channel. 🔔 All information will now be published on the new channel. ❗️ Please subscribe to stay in touch. ⬇️ ⬇️ ⬇️
Tới giờ lại lên cho anh em. Script 4h: loadstring(game:HttpGet("https://raw.githubusercontent.com/4hq9JdK4pM/mobkeyboard/main/main.txt", true))() 🚀
🔥8🎉7🥰7🤩6
BLOX FRUITS UPDATE Hack mới cho ae đang update hết ae chơi bản này nhé ae ko văng no key unc cao. Anh em chờ tí medium fix update xong là chơi được nha. Link: hoavip.shop 🔗
🎉13🤩12👍10🔥10
Tạm thời các bản hack đang update vì ban wave, nên sẽ không thể inject được nha, khi nào hoàn thành mình sẽ thông báo sớm nhất cho mọi người, những ai treo nuôi pet ib riêng để mình bù thêm script nha.👍
🔥15💯13🎉12👍11
Update Madium V1.3.3 Module: - Fixed few crashes on injection - Fixed getscriptclosure crash - Fixed setfflag issue - Fixed few scripts - Improved closure library - Added Oth Library - Added RakNet Library Link: hoavip.shop 🔗
🔥11❤8🥰8😍8
Thông báo Tôi đã tắt máy chủ C2 của họ. Nếu bạn đã tải xuống phần mềm độc hại (RAT) của họ thì bạn sẽ an toàn, hãy khởi động lại máy tính nếu bạn đã làm vậy vì nó sẽ hoạt động trở lại sau một thời gian. đừng chạy Velocity và hãy gỡ bỏ nó khỏi máy tính của bạn cho đến khi chúng tôi cập nhật mọi thứ.😀 Và sau cái thông báo thì velo đã die rồi anh em 🤡
🤩12❤10💯10🔥9
--- BLOX FRUIT SCRIPT --- 🦋 BUTTERFLY HUB 🦋 TÍNH NĂNG: - AUTO FARM - RAIN FRUIT - SEA EVENT - V4 DRACO (BEST TOP) loadstring(game:HttpGet("https://raw.githubusercontent.com/GoblinKun009/Script/refs/heads/main/ButterflyHub", true))()
🔥17🎉15🤩13🥰12
Bù cho anh em lỗi botnet và vài file bị down, anh em cứ dùng hết mình 😍
🤩12😍11👍8🎉5
--- BLOX FRUIT SCRIPT --- ⭐️ Vxeze Hub Fruit Finder ⭐️ TÍNH NĂNG: - AUTO FARM FRUIT - AUTO FRUIT FINDER (BEST TOP) - NO KEY repeat wait() until game:IsLoaded() and game.Players.LocalPlayer _G.VxezeConfig = { Main = { ["Team"] = "Marines", ["Auto Farm"] = true, ["Choose Mode"] = "Tween Fruit", -- Tween Fruit/Teleport Fruit ["Auto Random Fruit"] = true, …
🥰16🎉15👍14❤🔥11
Cảnh giác đang có link tải bị dính botnet, nạn nhân chính là admin, mọi người cẩn thận, mình sẽ tranh thủ kiểm tra và update lại 😡
🤣30👍9❤🔥8💯8
Showing the 12 most recent of 19 posts we hold for @appfrevip. 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.
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
@appfrevip 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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“HoaVi.P 🇻🇳” (@appfrevip), 1,320 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/appfrevip.
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.