Identifiers were handed out roughly in order
Accounts created later generally carry higher numbers. Anchor a set of known identifiers to known dates and everything between two anchors can be placed in that window.
Facebook UID Registration Date
Facebook UID registration date batch query. Enter one UID per line.
Query Results
| UID | Registration Date |
|---|---|
| No data yet | |
How the estimate works
Sequential Identifiers Are What Make Dating Possible
The method rests on one property of how the identifiers were issued, and understanding it tells you exactly where the answer is strong and where it is soft.
The page carries the anchor table
A table of one hundred and eighty seven ranges is bundled into the page. Your identifier is compared against those bounds locally, which is why there is nothing to wait for and nothing to meter.
This is not an official Facebook figure. Facebook does not publish account creation dates and offers no endpoint that returns one. Every answer here is interpolation from a community assembled table. Treat the month as a well founded estimate, never as a record you could show someone as proof.
The four possible answers
Reading A Month, A Boundary Label, Or A Blank
The lookup returns one of four things. Two are usable estimates, and two are telling you the table could not place the identifier.
| What you see | What it means | How much to trust it |
|---|---|---|
| A year and month | The identifier fell inside a bounded range with a dated label. | The usable answer. Accurate to the month, not the day. |
| Before 2009 | It landed under the lowest bound in the table. | Reliable as a floor. The account is old, but the table cannot say how old. |
| 2025-01 or later | It landed above the highest bound. | Reliable as a ceiling. Recent, with no upper limit given. |
| Unknown | It fell in a gap between ranges, or in a range with no date attached. | Not a finding. The table has no coverage there. |
Invalid format is about the string. The lookup only accepts digits. Anything carrying an at sign, a slash or a full profile link is rejected before any dating happens, so clean the column down to bare numbers first.
Why buyers ask
What Account Age Does And Does Not Buy You
Aged stock is priced above fresh stock almost everywhere, so a Facebook account age checker is worth pointing at the premium itself. It is worth being precise about which part of that premium the registration date supports.
It confirms the seller description
For aged Facebook account verification this is the whole job. A listing calling itself a 2019 account can be tested against the estimate. A wide mismatch is a concrete thing to raise before payment rather than after.
It does not confirm continuous use
An identifier issued in 2016 might belong to a profile that has been dormant since the week it was created. Age and history are unrelated.
It does not predict survival
An old registration date offers no protection against a restriction. Accounts of every age get actioned, and the date does not change that.
It cannot be faked in the identifier
The number was assigned at creation and cannot be edited afterwards. This is the one attribute in a listing that a seller cannot restyle.
Checking a batch
Testing A Consignment Against Its Stated Year
Running a whole delivery at once turns a claim about vintage into a distribution you can look at.
1
Reduce the file to identifiers
Strip passwords and mailboxes so every line is bare digits. Anything else returns an invalid format result and wastes a row.
2
Run the whole delivery, not a sample
There is no quota and no charge, so there is no reason to sample. A full run is what reveals whether a supposedly uniform batch is actually mixed.
3
Look at the spread, not the average
A batch sold as one vintage should cluster. Two distinct clusters usually means two sources were combined, which is worth knowing regardless of the average.
4
Separate unknowns before you count
Unknown results are gaps in the table rather than bad accounts. Exclude them from any percentage you quote, or the figure understates the batch.
Precision
Why The Answer Stops At The Month
People often ask for a day. The method cannot supply one, and it is better to say why than to imply a precision that is not there.
Anchors are sparse near the edges
Ranges are dense in periods when many identifiers were issued and thin elsewhere. In a thin stretch, a single range can span a long window, and the label names that window rather than a point inside it.
Issuance was never perfectly sequential
Blocks were allocated in ways that make the ordering approximate rather than strict. Two identifiers a few thousand apart can belong to the same month, so a day level claim would be invented rather than derived.