WHEREAMI.EARTH

Indoors this can take a moment

Ask someone where they are

Send a link to whoever you are trying to find. They tap once, and where they are comes back to you.

Make a link

They need no app and no account

Get WHEREAMI.EARTH free

Reads your address aloud, and keeps working with no connection.

Get it onGoogle Play
Download on theApp StoreComing soon

Android 9+ · No account

What county am I in?

Where the answer comes from

Nothing on your phone broadcasts a county. It comes from the same reverse geocode as your address: we hand a mapping service your coordinates, and it returns the nearest administrative area it has a record for. That is all it does. It is not asserting that the county it found is the one you are standing in — it cannot, because it knows where its records are, not where you are.

In practice this rarely matters, for a reason that does not hold for a street address or a postcode: counties are large. Stand in a yard, on a path, or at a set-back entrance and the nearest known building can genuinely be across the road, in a different postcode. The nearest known county essentially never is, because a county spans kilometres in every direction rather than metres.

Why the accuracy figure barely matters here

Everywhere else in this app, the accuracy radius on your fix decides how much we are willing to say — a fix good to a few hundred metres has earned the street and nothing narrower, and a wide one drops the postcode entirely rather than guess a block. A county is not gated the same way, and that is a deliberate difference, not an oversight.

The coarsest fix this app will still describe as a location — a rough, network-estimated area — covers a few kilometres. Almost every county anywhere is wider than that. So a fix too vague to earn a street name has still, in the overwhelming majority of places, earned its county with room to spare. The one place this breaks down is a fix taken within a few kilometres of a county line, where a wide-enough error radius could genuinely straddle two of them — and there, honestly, is no cleaner answer than the nearest record, which is what this page gives you.

When there is no answer

Sometimes the field above is blank even though your position is good. Two different things produce that, and neither is a bug.

The lookup can fail — a network fault, same as any other request this app makes. And some coordinates genuinely have no county to return: open water, land with no local administrative layer, or a mapping gap in the underlying data. A blank answer there is not a wrong one withheld; it is the honest shape of "we asked, and there is nothing on record."

Either way, the page does not guess. A county it cannot support with an actual record is not printed as one anyway just because a page about counties ought to have one.

If you want the argument for why an app should tell you when it does not know, rather than a clean, confident-looking placeholder, we wrote it down.