Based on OSM GB data from 2023‑03‑29 20:21:24 Z, there are 2553054 OSM objects tagged with a valid addr:postcode tag, covering 399424 different postcode units (about 23.1% of the total). There are also 638 objects tagged with partial postcodes (i.e. values of the form 'AB10' or 'AB10 9'). Correct formatting of postcodes is checked using the regular expression /^[A-Z][A-Z]?[0-9][0-9A-Z]? [0-9][A-Z][A-Z]$/; partial postcodes are those that instead match /^[A-Z][A-Z]?[0-9][0-9A-Z]? [0-9]?$/. Postcodes are also checked for validity by cross-referencing them with the official Code-Point Open dataset.
The following 1956 erroneous values have been found in addr:postcode tags, affecting 3198 OSM objects. In the lists below, clicking on the postcode value performs an Overpass Turbo search, the number in brackets shows the number of OSM objects when there is more than one, 'J+' loads objects with that postcode* into JOSM with the JOSM Remote Control, and 'NC' searches for the nearest current postcode in Code-Point Open. (* The data behind the JOSM loading and postcode seach is only updated weekly, so may lag behind the other data.)
The value of addr:postcode is correctly formatted, but the postal district (the part before the space) does not match any postcodes found in the official lists. These errors may be typos, or may be the result of a former postal district whose postcodes have been re-numbered.
No errors of this type found.
The value of addr:postcode is correctly formatted and the postal district (the part before the space) exists, but the postal sector (the number after the space) does not match any postcodes found in the official lists. These errors may be typos, or may be the result of a former postal sector whose postcodes have been re-numbered.
No errors of this type found.
The value of addr:postcode is correctly formatted and the postal sector (the part before the space and the number after it) exists, but the postal unit (the final two letters) does not match any postcode found in recent official lists. These values may be errors from typos, errors in sources used by mappers, or may arise for new developments where Code-Point Open has not yet been updated to include the new units. Note that the letters {C,I,K,M,O,V} can never appear in the final two positions of a postcode.
The value of addr:postcode is correctly formatted and the postal sector (the part before the space and the number after it) exists, but the postal unit (the final two letters) matches an old postcode that was previously in use but is no longer present in the current official list. Be careful with just updating these postcodes to a current value. It is reasonably likely that the postcode in OSM has been withdrawn because the entities it belonged to no longer exist (e.g. a Large user like a bank has closed, or some houses have been demolished for redevelopment).
There are multiple correctly-formatted postcodes within the addr:postcode value, correctly seperated by semi-colons, but at least one of the postcodes included does not exist in the current official data.
There are multiple valid postcodes within the addr:postcode value, correctly seperated by semi-colons, but they are from more than one postcode sector. Due to the way this tool works, postcodes with a different sector from the initial one will not be properly counted.
No errors of this type found.
The value of addr:postcode is correctly formatted apart from omitted or superfluous space characters. (No further checks have been done as to the existence of the postcode.)
No errors of this type found.
The value of addr:postcode is correctly formatted apart from the case of one or more letters. (No further checks have been done as to the existence of the postcode.)
No errors of this type found.
The value of addr:postcode is incorrectly formatted, and the problems are more than just a simple spacing or letter-case issue. (Values with the latter two issues are listed in other sections of this report.) Common problems include erroneously transcribing similar-looking letters and numbers, missing or extraneous characters, and holding down shift while typing a number.
The addr:postcode tag contains only the outbound part identifying the postal district.
The addr:postcode tag contains only the outbound part and the initial number of the inbound part, identifying the postal sector.
No errors of this type found.
There are multiple correctly-formatted valid postcodes within the addr:postcode value, correctly seperated by semi-colons. Such values may not be errors, but generally if a building has multiple postcodes, these correspond to different occupants of building. In such cases, it would usually be preferable for each of the occupants to have its own OSM object, and the different postcodes moved to those objects.
NB: The data on this page comes from the GB Taginfo instance, which in turn comes from the Geofabric GB Extract, and so includes Great Britain, the Channel Islands and the Isle of Man (but not Northern Ireland). Guernsey (GY), Jersey (JE), and Isle of Man (IM) postcodes are only checked to ensure they have a valid format and district. This page should update daily at about 10:15 UTC with OSM data from about 20:30 UTC the previous day. But if the data sources have not refreshed, older data will continue to be shown here. When displaying addr:postcode values here, spaces are converted to "␣", and non-ASCII characters to "␦".
Data derived from OpenStreetMap data, © OpenStreetMap Contributors, licensed under Open Data Commons Open Database License (ODbL). OSM data from the Geofabric GB Extract. Data obtained using the GB TagInfo API. Data derived in part using Code-Point Open under the Open Government Licence v3; Contains OS data © Crown copyright and database right 2020; Contains Royal Mail data © Royal Mail copyright and Database right 2016; Contains National Statistics data © Crown copyright and database right 2020.