Telegram RegisterThe public register of Telegram
Telegram profile photo for SH!TPOST

Channel

SH!TPOST

@OFCVASILIO18

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

1subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001952366075
TypeChannel
Username@OFCVASILIO18
Created5 September 2023measured — dated from the channel’s first post
First recorded15 August 2026
Last confirmed live16 August 2026
Measurements held2
On Telegramt.me/OFCVASILIO18

Growth

17 August 2026 — 1 subscribers15 August 2026 — 1 subscribers7 August 202615 August 2026
2 measurements spanning 8 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 04:161no change
7 Aug 2026, 04:181first reading

Engagement

6 posts held, back to 5 September 2023the 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 6 posts for this entry, the most recent from 23 October 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Videos
3
Links
1

Lifetime counters from Telegram’s own channel header, read 15 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.

Video runtime
44s
Average length
15s

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.

Recent posts

23 Oct 2023, 11:37 UTC58 viewsread 15 August 2026
Video

ㅤㅤㅤㅤ ♞ 𝐑𝟗𝟓 𝐎𝐅𝐅𝐈𝐂𝐈𝐀𝐋 𝐂𝐎𝐋𝐋𝐀𝐁𝐎𝐑𝐀𝐓𝐈𝐎𝐍 ♞ㅤㅤㅤㅤ Solidarity is Number One ♡ ❍ ⌲ •• ≡ ━━━━━━━━━━━━━━━━━━━━━━ ➮ 𝗦𝗣𝗘𝗖𝗜𝗔𝗟 𝗧𝗔𝗚 : @THEOCARSCOM @noreight @ENIGMATICTONE @M10MAN @OFCBARUDAKTOXIC @OFCVASILIO18 @CIRCLEJENNIE view all 99.999 comment 15 minutes ago ━━━━━━━━━━━━━━━━━━━━━━ ⌂ ⌕ ⊞ ♡

23 Oct 2023, 11:37 UTC49 viewsread 15 August 2026
Video

📸 📸 ✈️ 💬 ⬆️ Liked by @THEOCARSCOM and 20.356.890 others Orndnance Cars Comunity —————————————————————————————— Les bâtisseurs de la communauté Ordnance Cars : Passion, Talent, Excellence. Merci pour votre dévouement à l'univers de l'automobile. 𝐒pecial 𝐓ag: @pansoer @MARKHYUCKCITY62 @CRYSTANSQ @OVERKILLOFC @OFCGAXTOR @OfcKings_Star @THEVOLUER @M10MAN @OFCBLOKM31 @OFCT

23 Oct 2023, 11:36 UTC104 viewsread 15 August 2026
Video

VASILIØ WITH 10 MEMBERS❤️‍🔥 Spesial Tag : @OGCOK7. @jaIagn. @Taehyunkgh. @iKiimTaehyung. @Taegyhung. @vanfe. @vanGohkim. @nyebatgarp. @ruodel. @pTaehyungy

Showing the 6 most recent of 6 posts we hold for @OFCVASILIO18. 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 — 1,418,168 of 1,548,671entries 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.

Mentions

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.

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 15 August 2026 — this entry's latest reading, not the date you are reading this.

“SH!TPOST” (@OFCVASILIO18), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/OFCVASILIO18.

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.