The owner of this channel has been inactive for the last 18 months. If they remain inactive for the next 8 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

Channel
VӨLORIOUS, 7321.
@OFCVOLORIOUS
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
392subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001226296904 |
|---|---|
| Type | Channel |
| Username | @OFCVOLORIOUS |
| Description | ❛𝐃on't play with us, 𝐖e will beat you at the game, 𝐄very fucking time.❜ 𝐎ur 𝐏rojects @OFFICIALEUXOR. 𝐏lease contact us if you need anything: ➳☠ 𝐁ot Ofc : @Volorious_Bot ➳☠ 𝐁ot Mpps : @VxrMppsBot & @VxrMpps ( Open ) ➳☠ 𝐂h Poster : @VoluxorPost. |
| Created | Between 1 April 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/OFCVOLORIOUS |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 00:03 | 392 | no change |
| 6 Aug 2026, 23:48 | 392 | first reading |
Engagement
17 posts held, back to 26 July 2024 — 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 17 posts for this entry, the most recent from 25 April 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 246
- Videos
- 92
- Links
- 117
Lifetime counters from Telegram’s own channel header, read 7 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
5 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 40.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 40.0% | |
| 👏 | 2 | 40.0% | |
| 🥰 | 1 | 20.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 4 of the 17 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 5reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 26 July 2024 to 25 April 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
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 29 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 18 months. If they remain inactive for the next 7 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
VӨLORIOUS, 7321. pinned «Selamat Malam. Terima kasih banyak untuk seluruh pihak yang selama 4 tahun ini selalu berusaha ada. Baik untuk @OfcVolorious ataupun @Officialeuxor serta @TheVoluxor. Mohon maaf untuk segala kesalahan yang pernah di perbuat. Mohon maaf untuk segala ketidaknyamanan…»
Sticker, posted without a caption
File, posted without a caption
https://t.me/CitposVxr Semua kenangan ada disini juga. Untuk yang mau lihat atau sekedar scrolling gimana Vxr. Vxr dulu dan sekarang tetap rumah. Sekali lagi, terima kasih untuk semua kenangan baiknya dari kalian yaa, Voluxor. Gak akan pernah di lupain kok.
Masih boleh kontakan bareng yang lain, boleh chat @VolxrBot atau langsung ke gua, Vegar di @OverDruugs. Gua masih tetap Vegar yang dulu. Tetap Shavegar Alzheino. Selamat Malam, dan See You When I See You, Voluxor.
Gua Vegar, selaku Founder dari rumah ini, meminta maaf untuk siapapun yang pernah gua sakitin baik itu dari ketikan ataupun perilaku gua selama 4 tahun ini. Maaf kalau vxr masih belum bisa jadi rumah yang baik untuk kalian selama 4 tahun kemarin. Makasih untuk banyak kenangan yang udah kita jalanin bareng. Makasih untuk banyak suka dan duka yang udah pernah kita lewatin bareng. Untuk Scorp10ns, Zeron, Richard, Varez…
❤2
07 Maret 2021 - 07 Februari 2025 — Volorious dan Leuxor, Selesai.
Selamat Malam. Terima kasih banyak untuk seluruh pihak yang selama 4 tahun ini selalu berusaha ada. Baik untuk @OfcVolorious ataupun @Officialeuxor serta @TheVoluxor. Mohon maaf untuk segala kesalahan yang pernah di perbuat. Mohon maaf untuk segala ketidaknyamanan yang pernah ada, dan mohon maaf untuk segala hal kurang baik yang pernah di alami selama menjadi bagian dari vrs, lxr, ataupun vxr. Kali ini bukan prank. …
VӨLORIOUS, 7321. pinned a photo
Showing the 12 most recent of 17 posts we hold for @OFCVOLORIOUS. 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
Citation-graph rank — 399,375 of 1,176,251entries 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Mentions
Named by 20 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.
@OFFICIALEUXOR · 3404 postsRequirements VXR
@arsipvxr · 162 posts𝐌𝐎𝐎𝐍𝐑𝐎𝐖 𝐒𝐂𝐇𝐎𝐎𝐋 || BUBAR
@MOONROWSCHOOL · 862 posts𝗢𝗙𝗖 𝗕𝗘𝗝𝗔𝗗
@ofcbejad · 1,0742 posts𝗔𝗡𝗚𝗕𝗘𝗝𝗔𝗡 𝗔𝗥𝗘𝗔 𝗕𝗨𝗕𝗔𝗥
@ANGBEJAN · 2521 postKawan Hiltmer
@arsphiltmer · 51 post126. 𝗕𝗥𝗨𝗦𝗘𝗫 #VAKUM
@BRUSEXOFC · 6331 postSHITP0ST VOLUXOR
@CitposVxr · 731 post2D's ASSASSINS. 🔪
@FictionRP · 201 postKAWAN AQUATIC
@KAWANAQUATIC · 61 postPARTNERSHIP SPOOKYLAND
@listmppspooky · 71 post𝐏𝐒 𝐃𝟎𝐌𝐈𝐍Λ𝐓𝟎𝐑Σ 𝐌𝟎𝐍𝐃𝐈Λ𝐋Σ
@MPPS_DTMEOFC · 71 postOFC JAEROSETOWN
@ofcjaerosetown · 1871 post𝗣𝗥Ⓞ𝗣𝗘𝗥𝗧𝗬 𝗕𝗘𝗚𝗔𝗟
@OFCVOLEUR86 · 4851 postPARTNERSHIP VIP
@partnershipvip · 81 postPS KTH VILLAGE
@pskthvillage · 51 post𝗦𝗛𝗜𝗧𝗣𝗢𝗦𝗧 𝟵𝟬
@SHITPOSTWH90 · 2231 postKeep Volorious
@Volorious_Ofc · 51 postVOLUXOR POST
@VoluxorPost · 1811 postPS YOUTH
@youthmpps · 61 post
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.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“VӨLORIOUS, 7321.” (@OFCVOLORIOUS), 392 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/OFCVOLORIOUS.
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.