Telegram RegisterThe public register of Telegram

Channel

๐•๐„๐ƒ๐‘๐€๐™

@VEDRAZOFC

On this record: Growth ยท Engagement ยท What this channel posts ยท Posts ยท Citations ยท Cite this entry

90subscribers

+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-1001425100920
TypeChannel
Username@VEDRAZOFC
Descriptionselesai @OFCVEDRAZ
Created26 April 2021 โ€” measured โ€” dated from the channelโ€™s first post
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
On Telegramt.me/VEDRAZOFC

Growth

907 August 2026 โ€” 90 subscribers9 August 2026 โ€” 90 subscribers7 August 20269 August 2026
2 measurements spanning 3 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โ€. The vertical axis spans 89โ€“91 and does not start at zero.
Measurement log โ€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 14:4590no change
7 Aug 2026, 00:1990first reading

Engagement

12 posts held, back to 26 April 2021 โ€” 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 12 posts for this entry, the most recent from 26 August 2022. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
1
Videos
1

Lifetime counters from Telegramโ€™s own channel header, read 9 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
20s
Average length
20s

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.

Recent posts

26 Aug 2022, 19:15 UTCviews โ€”

The account of the user that owns this channel has been inactive for the last 5 months. If it remains inactive in the next 10 days, that account will self-destruct and this channel may no longer have an owner.

19 Nov 2021, 10:56 UTCโ‰ˆ1,350 viewsread 9 August 2026
Forwarded from @OFCVEDRAZ

เฝผ่ฐทห– ๐Ÿ‡ต๐Ÿ‡ฌ โช VEDRAZ โซ ๐Ÿ‡ต๐Ÿ‡ฌ ห–่ฐท เฝผ ใ€ ๅนธใ›ใชๅฎถๆ—ใฏๆ—ฉใๆฅใ‚‹ๅคฉๅ›ฝใงใ™ ใ€‘ 15 November 2021 saya perwakilan dari fown @OFCVEDRAZ tepat pada 19 November ingin mengucapkan happy mensive yang ke 6 sekaligus ingin menyatakan bahwa tepat pada hari ini : Nama : ร˜FC VEDRAZ Username : @OFCVEDRAZ Tema/Konsep : Bushi/Jepang Since : 19 Mei 2021 Telah resmi BUBAR/RATA dikarenakan suatu hal yang tidak dapat kami jelaskan. Saya ucapkan terimakasih โ€ฆ

19 Nov 2021, 10:56 UTCโ‰ˆ1,300 viewsread 9 August 2026
Forwarded from @OFCVEDRAZ

saya selaku Founder Vedraz melocked semua hal yang berhubungan dengan vedraz dari nama hingga semua yang ada di dalam channel ini. untuk admin maupun member yang masih memakai atribut Vedraz harap di lepas semua. tolong kerjasamanya, terimakasih.

14 Oct 2021, 15:42 UTCโ‰ˆ1,480 viewsread 9 August 2026
Forwarded from @OFCVEDRAZPhoto

VEDRAZ โ€• โฒ #STRUKTURVEDRAZ โณ

19 May 2021, 09:13 UTCโ‰ˆ4,000 viewsread 9 August 2026
Video

โ”โ”โ”โ”โ”โ”โ”โ”โ” โชๆญฆๅฃซโซ โ”โ”โ”โ”โ”โ”โ”โ”โ” ใ€Œ ๐•๐„๐ƒ๐‘๐€๐™ ๐–๐„ ๐€๐‘๐„ ๐ƒ๐‘๐€๐™๐„๐‘ โ๐๐š๐ญ๐š๐ง๐  . ๐ญ๐ž๐ซ๐ฃ๐š๐ง๐  . ๐ฆ๐ž๐ง๐š๐ง๐ โž ใ€

Showing the 12 most recent of 12 posts we hold for @VEDRAZOFC. 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.

Forward network

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

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 9 August 2026 โ€” this entry's latest reading, not the date you are reading this.

โ€œ๐•๐„๐ƒ๐‘๐€๐™โ€ (@VEDRAZOFC), 90 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/VEDRAZOFC.

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.