Post-match intelligence

Your squad's story,
after every match.

VBR turns a VALORANT match into a clear report: what actually happened, who carried the rounds, and what the numbers can — and cannot — tell you. Built for groups that review together.

Sample report UI is shown in Chinese; English report copy ships with W3-i18n.

Sample data Sample VBR match report showing squad stats and round story

More than a scoreboard

Every number is paired with a plain-language reading, so the report is useful to the whole squad — not just the person who reads ADR for fun.

01

Round story

A short, evidence-based narrative of how the match turned: opening contact, mid-round swings, closing rounds.

02

Squad view

All five players in one consistent order, with role context and a low-impact marker that does not rely on nicknames.

03

Share-ready image

Export a 750px long image for Discord or your group chat. The layout is stable, readable and does not expose raw identities.

04

Honest limits

We separate “what the data says” from “why it happened”. No invented causes, no fake trends, no toxicity.

How it works

Server-side processing keeps API keys and raw provider payloads away from the browser.

Enter a Riot ID

We resolve the account and load recent Competitive / Unrated matches. No password, no client injection.

Compute on the server

Normalization, metrics and the round story are produced by our Python pipeline — the same code that powers the desktop app.

Read or share

Read the report in the browser, export the long image, or create a revocable share link with an opaque token.

What a report looks like

Samples use synthetic match data and are clearly labelled. Real match processing arrives with the W3 demo.

Sample report: overtime win
Sample · overtime win — full squad stats, round story and role context.
Sample report: 12:12 draw
Sample · 12:12 draw — draws are reported as draws, not losses.

Open the sample page

Data note: VBR is a post-match analysis tool. It does not run in-game, does not affect gameplay, and does not sell personal data. Match data is fetched server-side; content metadata (agent names, map names, artwork) comes from community mirrors and is checked before publication.