Vavada Aviator round history as evidence and accounting

What is in the record

Collapsed, one entry per finished round: the figure the curve stopped at, usually tinted by size. Expanded, most builds add two columns that matter far more than the multipliers do — a round identifier, and your own stake and exit for every round you were in.

Those two columns are the content of this page. The multipliers describe the game; the identifier and your own entries describe you, and they are the only record of either that exists outside the operator's own systems in a form you can read.

One limit to know in advance: the strip is short. It holds recent rounds rather than a session, so anything you expect to need later should be noted while it is still on screen.

When a round goes wrong, this is the whole of your evidence

The failure worth preparing for is a connection that drops with a stake live. What the server had already accepted stands, including a confirmed exit and an automatic target that had already fired; what it never received did not happen. The problem is that from your side those two look identical afterwards, and a reader with nothing but a recollection has no case to make.

The round identifier is what changes that. It is the reference an operator can look a round up by, and a query carrying one is a question about a specific record rather than a description of a bad feeling. Note it before closing the tab.

Be clear about what to ask for, though. Support can usually confirm what the server accepted and when; it will not generally reverse a round because a request never arrived, since from the server's point of view nothing went wrong. That sounds like a smaller answer than you wanted and it is the useful one: it tells you whether the exit was accepted, which decides whether anything is owed at all.

Counting what a session cost, properly

The balance is the wrong instrument. It compresses several hundred decisions into one number and tells you nothing about which of them was expensive. The figure to count is turnover — the total you staked, which is the number the cost of this game is a share of.

An example you can run against your own evening. At ₹20.00 a round for 300 rounds, turnover is ₹6000.00, and at the quoted payout share the expected cost of that session is about ₹180.00. The actual result will land some way either side of it, often a long way, but the expected figure is the one to compare a session against — and it is a figure neither the balance nor the strip shows you directly.

Your own entries in the record are also the fastest way to notice what this format does well, which is to fit a great many decisions into very little time. Short rounds plus a repeating amount compress a loss into a far shorter stretch than any table game, and the record is where that shows up well before the balance makes it obvious. If reading it that way is uncomfortable, the three Indian support lines at the foot of this page are free and answer in several languages.

And the thing it cannot do

The record is not a forecast, and on this site that is not an opinion to be weighed: it follows from where the multiplier comes from, which is worked out with numbers on its own page. In one line — the ending of a round is fixed and sealed before stakes close, so a list of endings that have already happened has no bearing on the next one.

That is also the complete answer to every product built on top of the strip. Anything reading this record from outside the client is reading the same thing you are, which is free and already on the screen.