Two people type "past results for Melate, Revancha and Revanchita" on the same day and want things with nothing in common. One has a ticket in a wallet and needs one specific draw, with its number, unambiguously. The other wants to build a table out of two years of history to see whether anything stands out. Both will land on the same pages, and each will find something different missing. A lottery archive is not one object: it is three, and hardly anyone says which one they are handing you.
Start with what this page will not do. There is no winning combination here and no list of numbers from any draw, because this page is not about a particular draw, and six numbers with no draw attached are no use to anybody: they cannot be verified, cannot be dated and cannot be argued about. The results of an identified draw belong in the record published by Pronósticos para la Asistencia Pública, the operator, or in a tool that states clearly which draw it means. What I can give you is a map of the archive, which is the part nobody explains and the part that decides whether the page you opened is any use to you.
Before the map: it is not one archive, it is three series
Melate, Revancha and Revanchita share the night and share the number field — six from 1 to 56 — but they are three different draws with three different results and three different histories. That has a treacherous visual consequence: all three fit neatly into a three-column table, and a three-column table quietly suggests that the three series run in parallel and at the same length from the beginning.
There is no guarantee that they do, and it is the first question worth putting to any archive: how far back does each of the three go, and how current is it? An empty cell in the old rows can mean two very different things — that the game was not drawn that night, or that the game did not yet exist — and the table does not distinguish. If you have never been entirely clear on how the three relate, the difference between Revancha and Revanchita sorts that out before you go anywhere near the history.
Zone 1: the recent past
This is the past that is still somebody's present: the last handful of draws, the range where live tickets sit in drawers and wallets. It is the only zone of the archive with a personal, urgent, dated use.
What this zone demands is absolute accuracy and, above all, identity: every row has to say which draw it is, not merely which day. A row carrying only a date forces a mental translation from date to draw, and that translation is exactly where a hurried person's errors creep in. The other demand is freshness, and it is the one that fails most: a results page almost never warns you that it is stale. Updated and abandoned look identical.
This is also where the awkward question about long-stored tickets shows up. Let me be explicit about what I am not going to do: I am not going to tell you how long you have. A limit does exist, each draw's convocatoria sets it, and we are not going to invent one here. Confirm it directly with the operator or at an authorised point of sale, and if you want to see how the question is framed, it is in how long you have to collect a Melate prize. What I can tell you is that zone 1 of the archive is the part that serves that lookup, and that you need your ticket's draw number to use it properly.
Zone 2: the middle distance
Months, a year, two. This is the statistics zone, and by far the most visited: frequency tables live here, along with rollover runs and counts of odds and evens. Nobody here is holding a ticket; everybody here is looking for a pattern.
What this zone demands is not row-by-row precision — one stray error will not move a count across a thousand draws — but that the window be declared. A count that does not say how many draws it covers cannot be compared with another count, which is why two frequent-number pages hardly ever agree without either of them lying. Piling all three games into a single tally is a further enormous decision that no table announces: it produces a combined object that describes none of the three individually.
And the trap of zone 2, which has to be named even though it is told better elsewhere: what you see here describes what happened and does not tilt what comes next. Every draw is independent of the last and no number is due; if that intuition pulls at you, the gambler's fallacy gives it the room it deserves. Looking at the middle distance is legitimate and even enjoyable. Extracting a prediction from it is not.
Zone 3: the far end of the series
The old part of the archive is no use for checking tickets and no use for building a workable table, which is why almost nobody opens it. It is good for something else, and it is the only zone where the object of study is not the numbers: it is the game.
A long archive is the one place where you can see that the game you play today is not exactly the one the oldest rows describe. The draws sharing the night change, add-on games appear, presentation formats modernise. None of that is announced inside the table; it is inferred from where the columns start and stop. Which is why I say the question "how far back does each series go?" is more informative than any of the numbers in it: it answers how old each game is and, in passing, how comparable they are to one another.
It is also the zone where the archive stops being a tool and becomes a document. If that is the side that interests you, the Melate archive and the history of the institution that runs it tell what the rows alone do not.
How to tell which zone a page was built for
There are four tells, and they read in ten seconds without looking at a single result.
- Does every row carry a draw number? If it carries only a date, the page was built for browsing, not for verifying. Fine in zone 2, limping in zone 1.
- Does it say when it was updated? With no update stamp, the only way to know whether it is alive is to compare it against another source — precisely what you came here to avoid.
- Does it declare its window? "The 100 most recent draws" and "all available history" produce different tables and neither is wrong. The one that does not say is the one you cannot use.
- Can you jump to a date, or only step backwards from today? This is the most revealing. An archive that only walks backwards one page at a time is a zone-1 tool in a historical costume: perfect for the last few draws, useless the moment you want something from three years ago.
None of these tells says anything about data quality. They say what the page was designed for, which is a different question and, in practice, a more useful one. A flawless table built for browsing will frustrate you if what you are holding is a ticket; a flawless results mask will not help you study two years of history.
What it costs to stand in the wrong zone
That sounds abstract until you see the three concrete ways it goes wrong, and all three are common.
Using a statistics page to verify a ticket. The most frequent case and the most expensive. Zone-2 tables are built to count, not to identify: they present aggregated results, sometimes with no draw number per row, sometimes with the adicional folded into the same column. Comparing a ticket against a table like that can hand you a match that does not mean what you think, or let you walk straight past one that does. The right tool for a ticket is the one that starts by asking which draw it is from.
Using a zone-1 tool to study history. The symptom is always the same: somebody steps back twenty or thirty draws, which is as far as the page comfortably goes, and spots a pattern. In a sample of thirty draws there is always a pattern; it would be remarkable if there were not. The conclusion did not come from the data, it came from the size of the window the page allowed — and that is a property of the page's design, not of the game.
Comparing the three columns all the way down. If the series are not the same length, any cumulative count for Revanchita will come out smaller than Melate's, and that difference says nothing about the games: it says how many draws each one has behind it. It is an age comparison dressed as a behaviour comparison, and normalising by the number of draws makes it disappear.
The four things people want when they type this
Worth saying plainly, because naming your own intent saves half an hour of navigation.
Verifying a stored ticket. Zone 1. You need the draw number printed on the ticket and a source that uses that same number. Everything else is surplus.
Building a frequency table. Zone 2. You need a declared window, you need to know whether the adicional counts as an appearance, and you need to know whether the three games are merged or kept apart.
Settling an argument about one specific night. Zone 1 or 3, depending how far back it sits. Here the only thing that matters is traceability: that the source lets you reach the exact draw rather than "that week".
Pure curiosity. What came out on the day you were born, what happened the year you started playing. Zone 3, and the most honest use of all, because it asks nothing of the archive beyond the pleasure of looking. If a line you like comes out of that, let it be because you like it and not because the archive recommended it; on that particular temptation there is more in playing birthday dates.
What an archive cannot do for you
A results archive is a record of what happened, so its honesty is measured by what it admits it does not know. It does not know whether you played that night — only your ticket says that — it does not know how many times you have taken part, and it holds no information whatsoever about the next draw. All three are asked of it constantly and all three are beyond it.
What it does, and does very well, is let anybody verify what is claimed about a past draw. That is a valuable and uncommon property: nearly everything surrounding a lottery is a statement about the future, uncheckable until it is too late. Past results are the one part of the game you can hold up against a source today and find right or wrong. That is worth using them for.
Frequently asked questions
Where do I look up past results for Melate, Revancha and Revanchita?
In the record published by Pronósticos para la Asistencia Pública, and in tools that cite each draw's number. What matters is not the source so much as that every row names its draw and states how current it is.
Do the three games share one history?
Not necessarily. They share the night and the number field, but they are three independent series. It is worth asking each archive how far back each one goes before comparing columns.
Are past results any use for predicting the next draw?
No. Every draw is independent of all the ones before it. The archive describes the past precisely and contains no information about what is coming.
Can I check a very old ticket against the archive?
You can look up the result, yes: the record is published. What the archive does not settle is what can be done afterwards with an old ticket, and that is worth confirming directly with the operator.
In short
"Past results" is not one thing. It is last Thursday's draw, it is the middle distance where the statistics live, and it is the far end of the series where the interesting subject stops being the numbers and becomes the game. Each zone asks something different of the page serving it — draw identity, a declared window, the reach of the series — and most pages serve exactly one of them well without saying so. Knowing which zone you are standing in turns a frustrating search into a thirty-second lookup.
And if looking at the archive leaves you wanting to play the next one, let the line be considered: you can generate balanced combinations with MelateBot AI Picks.
This content is informational and for entertainment purposes. MelateBot is not affiliated with Pronósticos para la Asistencia Pública. Melate is a game of chance: no method predicts, guarantees or increases the probability of obtaining the winning numbers. Please play responsibly.