Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
This release note provides information about the September 2024 release of the AddressBase products. These products were released to customers on 26 September 2024.
Product | Full Supply Record Count[1] | Change-Only Update Record Count[2] |
---|---|---|
There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.
The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.
If you are unsure of your supply type, please check this with your OS Relationship Manager.
If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an MGBS supply,and also how many tiles are affected if you take your supply as Changed Chunks.
The following information relates to the currency of the source data used in the creation of Epoch 113:
Affected output formats: CSV and GML
There are 6 504 Unique Property Reference Numbers (UPRNs) which reference a Parent UPRN that cannot be found in the product. This is because the Parent UPRN is either provisional or historic and is not matched to the Royal Mail Postcode Address File (PAF) or Valuation Office Agency (VOA) record, meaning that it is not included in the AddressBase Plus product as per the existing background logic rules.
There are 227 records with a sao_start_no or sao_text that have no Parent UPRN in the product. This is because the Parent UPRN is a historical record which is included as part of the logic for record inclusion in the AddressBase Plus products.
The match rates for Council Tax and Non-Domestic Rates for Epoch 113 are detailed as follows based on Valuation Office Agency (VOA) records up to 19 August 2024. The match rate is applicable to the AddressBase Premium product.
Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in 37 159 more tertiary classifications present in Epoch 113 compared to Epoch 112. Indeed, 88.71% of these tertiary classification improvements are against residential codes.
The following graph shows the number of Postcode Address File (PAF) matched records in AddressBase by epoch:
The next release of AddressBase products, Epoch 114, is scheduled for 07 November 2024.
These counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.
Change-Only Updates are not available for the OS Open UPRN product.
Product | MGBS Full Count | National AOI Full Count | Difference |
---|---|---|---|
Change Type | Count |
---|---|
Change Type | Count |
---|---|
AddressBase Premium Table | Inserts | Updates | Deletes |
---|---|---|---|
Data Source | Date |
---|---|
Data Source | Records Received | % Matched |
---|---|---|
OS OpenUPRN
40 909 714
N/A
AddressBase
30 552 484
137 772
AddressBase Plus
38 156 204
677 294
AddressBase Premium
See rows below
See rows below
Street
1 509 895
5 780
Street Descriptor
1 633 461
2 501
BLPU
40 909 714
355 256
Classification
44 758 076
125 856
LPI
46 089 180
182 176
Organisation
1 422 866
14 505
Delivery Point Address
30 659 580
54 376
Application Cross Ref.
198 307 242
735 178
Successor
0
0
AddressBase
30 552 484
30 552 484
0
AddressBase Plus
38 156 204
38 156 184
20
AddressBase Premium
See rows below
See rows below
See rows below
Street
1 509 895
1 509 892
3
Street Descriptor
1 633 461
1 633 458
3
BLPU
40 909 714
40 909 690
24
Classification
44 758 076
44 758 052
24
LPI
46 089 180
46 089 155
25
Organisation
1 422 866
1 422 864
2
Delivery Point Address
30 659 580
30 659 580
0
Application Cross Ref.
198 307 242
198 307 218
24
Successor
0
0
0
Inserts
32 275
Updates
96 919
Deletes
8 578
COU Populated Tile Count
5 003
Inserts
43 451
Updates
621 151
Deletes
12 692
COU Populated Tile Count
7 088
Street
1 264
4 501
15
Street Descriptor
1 484
999
18
BLPU
39 273
312 858
3 125
Classification
47 617
59 927
18 312
LPI
51 254
127 306
3 616
Organisation
5 675
4 479
4 351
Delivery Point Address
32 839
13 224
8 313
Application Cross Ref.
183 150
520 267
31 761
Royal Mail PAF
22 August 2024
National Land and Property Gazetteer
22 August 2024
One Scotland Gazetteer
05 August 2024
VOA Non-Domestic Rates
19 August 2024
VOA Council Tax
19 August 2024
OS MasterMap Topography Layer
13 August 2024
OS MasterMap Highways Network
06 August 2024
Code-Point with Polygons
01 July 2024
Boundary-Line
24 June 2024
Council tax
27 145 616
99.92
Non-domestic rates
2 122 260
96.47
Release notes for the AddressBase products
This release note provides information about the September 2024 (Epoch 113) release of AddressBase products.
This release note provides information about the August 2024 (Epoch 112) release of AddressBase products.
This release note provides information about the June 2024 (Epoch 111) release of AddressBase products.
This release note provides information about the May 2024 (Epoch 110) release of AddressBase products.
This release note provides information about the April 2024 (Epoch 109) release of AddressBase products.
The following AddressBase core principles pages provide an overview of the 'family' of AddressBase products. They cover core elements of design for AddressBase products, including data formats, coordinate reference systems, currency, precision, and data sources, amongst other topics.
These pages should be used in conjunction with the detailed technical specifications found under the top-level product guide page for each individual product.
A critical step in the creation of an address is undertaken within each Local Authority by the dedicated Street Name and Numbering (SNN) custodian and the Scottish Local Street Gazetteer (LSG) custodians, who allocates the official street name and building information.
The SNN/LSG custodian has a statutory obligation to provide SNN/LSG information for all addresses within their administrative area. Once the SNN/LSG custodian has fulfilled their statutory obligation for initial capture, the LLPG/OSG custodian will maintain the address for the life of the address record.
The official street name and building information for new properties captured by the SNN/LSG custodians is provided to Royal Mail who then allocate a postcode to the address.
The AddressBase classification scheme provides varying levels of classification for addressable objects which are captured and maintained by the Local Authorities and Ordnance Survey. This allows searches to be limited on residential or commercial addresses or be more specific to find all the flats or all fast-food outlets. The varying levels of classification are as follows:
Primary Level Classification R: Residential C: Commercial
Secondary Level Classification RD: Residential Dwelling CH: Hotel/Motel/ Boarding/ Guest House
Tertiary Level Classification RD02: Detached House CH01: Boarding/Guest House/ Bed And Breakfast/Youth Hostel
Quaternary Level CH01YH: Youth Hostel
The level of classification varies across all addressable objects and across the different products.
There are only certain classification codes that extend to the quaternary classification level as shown above. A full list of the classification codes can be found on our Product Support page.
A code list is a controlled set of allowable labels or codes represented as an alphanumeric attribute. The pages in this section show the code lists used within the OS Emergency Services Gazetteer (ESG). Some of the code lists apply to attributes of multiple feature types, whereas others will only apply to attributes of one feature type.
Updates are continuously made to the central spatial address data hub, which is managed by GeoPlace. These are used to produce the AddressBase Core product, which is supplied on a weekly basis. An extract is taken for the creation of AddressBase, AddressBase Plus and AddressBase Premium on a 6-weekly basis.
Quality control procedures are undertaken at all stages of production to ensure that the data is as accurate and complete as possible and conforms to the specification. These quality control checks include automated data testing against the product specification and visual checks by operators.
Coordinates for all addressable objects with each AddressBase product are published with geometry given to a precision of up to 2 decimal places for British National Grid coordinates, and up to 7 decimal places for ETRS89 coordinates.
Through collaborative working between Ordnance Survey, GeoPlace, the Local Government Agency and Improvement Service, a single definitive spatial address database for Great Britain has been created and maintained since September 2011 for England and Wales, and April 2012 for Scotland.
This initiative supports the UK Location Strategy concept of a 'core reference geography', including the key principles of the European Union INSPIRE directive, that data should only be collected once and kept where it can be maintained most effectively.
The creation of AddressBase products brings together the best parts of:
The National Land and Property Gazetteer (NLPG) provides the most up-to-date addresses including street names and numbers from each Local Authority’s LLPG in England and Wales. This data also provides a Unique Property Reference Number (UPRN) for each address encompassing residential, commercial and public infrastructure such as fire stations.
One Scotland Address Gazetteer (OSG) provides the most up-to-date addresses including street names and numbers from each Scottish Local Authority’s CAG. This data also provides a Unique Property Reference Number (UPRN) for each address encompassing residential, commercial and public infrastructure such as fire stations.
Ordnance Survey provides a wide range of additional addresses including Objects Without a Postal Address (OWPAs) such as Telephone Exchanges, a wider spatial context by including references for both the OS MasterMap Topography Layer and OS MasterMap Highways Networks Layer which the address feature is related to and additional classification information.
PAF contains approximately 30 million Royal Mail addresses that are identified as receiving post in Great Britain. Addresses from the NLPG and OSG are matched to the PAF addresses to provide the Unique Delivery Point Reference Number (UDPRN) into product and supplement the Local Authority address with information such as organisation name, postal town and postcode.
The Valuation Office Agency (VOA) gives the government the valuations and property advice needed to support taxation and benefits within England and Wales. Addresses from the NLPG are matched to the VOA address to provide the Unique Address Reference Number (UARN), VOA Special Category and Primary Description classification codes in product.
GeoPlace is a limited liability partnership jointly owned by the Local Government Association and Ordnance Survey and is the centre of excellence for spatial address and street information in Great Britain. GeoPlace brings together local government's address and streets gazetteers with information from Ordnance Survey, Improvement Service, Royal Mail’s PAF dataset and VOA addresses into a central spatial address data hub. The database hub is updated by GeoPlace based upon the receipt of data from all the contributing data sources.
GeoPlace manage this hub and provide address and street information to be utilised in the AddressBase products.
At present, there are 314 local authorities in England and Wales, inputting updates to their Local Land and Property Gazetteers (LLPG). These changes are submitted to the GeoPlace Hub daily, weekly or monthly as part of their update schedule.
On receipt of these updates, they are checked to ensure that they have been produced in accordance with the NLPG Data Entry Conventions and they are in compliance with the national standard for the representation of address information – BS 7666 Parts 1 and 2.
There are currently 32 local authorities in Scotland which update their local address gazetteers on a daily, weekly or monthly as part of their update schedule to the OSG. The Improvement Service check each
update to ensure compliance with the national standard for addressing (BS7666.2006) and the Scottish Gazetteer Conventions 1-3.
One of the key strengths of AddressBase products is the collection and verification of data at the local level. A real benefit is the capture of addresses at the earliest point in their lifecycle, and then this address being maintained by the local authority.
To do this the Local Custodians will utilise the wealth of information at their disposal until the address is demolished (when it becomes a historical record).
Local Custodians will use information such as:
Building and Development control
Planning and Land Charges
Waste Collection
Electoral Roll
LLPG custodians (England and Wales) are allocated sequential batches of UPRNs by GeoPlace, which are assigned by the LLPG custodian at the creation of a new address.
The OSG (Scotland) custodians are allocated sequential batches of UPRNs by the Improvement Service, which are assigned by the OSG custodian at the creation of a new address.
This release note provides information about the August 2024 release of the AddressBase products. These products were released to customers on 15th August 2024.
Product | Full Supply Record Count[1] | Change-Only Update Record Count[2] |
---|---|---|
There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.
The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.
If you are unsure of your supply type, please check this with your OS Relationship Manager.
If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an MGBS supply,and also how many tiles are affected if you take your supply as Changed Chunks.
The following information relates to the currency of the source data used in the creation of Epoch 112:
Affected output formats: CSV and GML
There are 5 675 Unique Property Reference Numbers (UPRNs) which reference a Parent UPRN which cannot be found in the product. This is because the Parent UPRN is either provisional or historic and is not matched to the Royal Mail Postcode Address File (PAF) or Valuation Office Agency (VOA) record, meaning that it is not included in the AddressBase Plus product as per the existing background logic rules.
There are 220 records with a sao_start_no or sao_text that have no Parent UPRN in the product. This is because the Parent UPRN is a historical record which is included as part of the logic for record inclusion in the AddressBase Plus product.
The match rates for Council Tax and Non-Domestic Rates for Epoch 112 are detailed as follows based on Valuation Office Agency (VOA) records up to 8th July 2024. The match rate is applicable to the AddressBase Premium product.
Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in 48 610 more tertiary classifications present in Epoch 112 compared to Epoch 111. Indeed, 88.72% of these tertiary classification improvements are against residential codes.
The following graph shows the number of Postcode Address File (PAF) matched records in AddressBase by epoch:
The next release of AddressBase products, Epoch 113, is scheduled for 26th September 2024.
These counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.
Change-Only Updates are not available for the OS Open UPRN product.
This release note provides information about the April 2024 release of the AddressBase products. These products were released to customers on 05 April 2024.
Product | Full Supply Record Count[1] | Change-Only Update Record Count[2] |
---|---|---|
There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.
The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.
If you are unsure of your supply type, please check this with your OS Relationship Manager.
If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an MGBS supply,and also how many tiles are affected if you take your supply as Changed Chunks.
The following information relates to the currency of the source data used in the creation of Epoch 109:
Affected output formats: CSV and GML
There are 5 021 Unique Property Reference Numbers (UPRNs) which reference a Parent UPRN which cannot be found in the product. This is because the Parent UPRN is either provisional or historic and is not matched to the Royal Mail Postcode Address File (PAF) or Valuation Office Agency (VOA) record, meaning that it is not included in the AddressBase Plus product as per the existing background logic rules.
There are 254 records with a sao_start_no or sao_text that have no Parent UPRN in the product. This is because the Parent UPRN is a historical record which is included as part of the logic for record inclusion in the AddressBase Plus product.
The match rates for Council Tax and Non-Domestic Rates for Epoch 109 are detailed as follows based on Valuation Office Agency (VOA) records up to 26 February 2024. The match rate is applicable to the AddressBase Premium product.
Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in 47 161 more tertiary classifications present in Epoch 109 compared to Epoch 108. Indeed, 88.77% of these tertiary classification improvements are against residential codes.
The following graph shows the number of Postcode Address File (PAF) matched records in AddressBase by epoch:
Notification of Epoch 109’s Improvement in Historic BLPU State Code Completeness and Large Release Size
This release includes an enhancement in the clarity and consistency of life cycle representation within product.
A conformance improvement has been delivered for BLPU State attribute for records where the BLPU Logical Status was 8 (historic) and BLPU State was null, for increased completeness BLPU State Code has been populated with value 4 (no longer existing) and date stamped for the change applied.
The BLPU state identifies the current life cycle stage of a property (or object) and is additional to the mandatory LOGICAL_ STATUS field.
The BLPU code is an optional attribute for Local Authority Custodians to complete and therefore this attribute may be NULL in product.
An improvement to the completeness of the BLPU State Code was identified as a quality enhancement for life cycle information as values for BLPU state code 4 can be accurately inferred from a Logical Status of 8. This enhancement allows the data to be interpreted more easily by removing conflict between addresses with a historic logical status and no BLPU state.
All nations within GB and the Islands product regions will benefit from this improvement, as such it impacts approximately 1.2 million records for a full supply.
This quality improvement means a larger than usual supply of COUs.
The next release of AddressBase products, Epoch 110, is scheduled for 16th May 2024.
These counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.
Change-Only Updates are not available for the OS Open UPRN product.
AddressBase, AddressBase Plus, AddressBase Premium and AddressBase Islands are updated every six weeks. This six week period of time is known as an epoch.
Our AddressBase products are currently available as a full supply or Change-Only Update (COU) for each epoch.
Future dates are provided as an indication only and are subject to change. Data cut dates are estimates; these are given to provide an indication of the last point at which changes will reach the epoch.
As we approach the publication date and prepare to release a new epoch, any new requests placed for data will be paused to ensure data integrity. These requests will be processed as soon as this pause is lifted.
The AddressBase product family is made up of four products:
AddressBase products are created by bringing together different address sources:
Local Authority Gazetteers for England, Wales and Scotland
Royal Mail PAF data
References to Valuation Office Agency (VOA) data
Additional addresses and coordinates from Ordnance Survey
This information is managed by GeoPlace under a joint venture partnership between Local Government Association and Ordnance Survey (OS). Scottish Local Authority address information is supplied to GeoPlace under licence between Ordnance Survey and the Improvement Service supported by the Scottish Government.
Ordnance Survey is responsible for customer management, sales, marketing and distribution of the AddressBase products.
This comparison table highlights the similarities and differences between the AddressBase products
AddressBase | AddressBase Core | AddressBase Plus | AddressBase Premium | |
---|---|---|---|---|
The four AddressBase products have been designed to meet distinct customer requirements. The source data is collated, verified and quality assured by GeoPlace.
AddressBase Premium provides the most detailed view of an address and its life cycle for England, Wales and Scotland. It has approximately 40 million addresses as it records an address from creation through to retirement. All address records are provided with a Unique Property Reference Number (UPRN).
There are over 100 million cross-references which include references to VOA data and products such as OS MasterMap Topography Layer and OS Highways Layer are also included.
The product contains Local Authority, Ordnance Survey and Royal Mail addresses. This includes alternative addresses for current records where available, indicating variations on the official addresses and/or addresses in different languages (Welsh or Gaelic); as well as including provisional addresses (proposed planning developments), and historic information (demolished properties) where available. Other addresses known as Objects Without a Postal Address (OWPAs) are also included in AddressBase Premium, these include places of worship, community centres and utilities.
AddressBase Core is a new addition to the addressing portfolio, which was released in July 2020.
AddressBase Core takes many of the important elements from the other AddressBase products, such as coordinates, classification and cross-references to connect address information to other products via key identifiers.
AddressBase Core's primary source of addressing information is Local Authority data from the National Land and Property Gazetteer (NLPG) and One Scotland Gazetteer (OSG). They have the legal responsibility to capture and maintain address data for Great Britain, so you are assured of its authenticity and legal nature.
Address information is provided in an easy-to-use format alongside a single line attribute which concatenates all the address elements into what you would expect to see on an envelope. It is updated weekly and is offered in an easier to digest format to make the product as easy to access and use as possible.
Customers have asked for easy file formats, so CSV and GeoPackage are available for this product, with headers included – removing the need for any post-processing. Simply load, or drag and drop into a GIS package to start analysing.
AddressBase Plus contains current properties using addresses sourced from Local Authorities, Ordnance Survey and Royal Mail for England, Wales and Scotland. The product currently contains approximately 37 million records.
The product contains all current addresses validated from Local Custodians and non-postal addresses such as ponds, electricity sub-stations and telephone boxes are also included.
The product enables the end-user to locate an address or property on a map using either X, Y coordinates supplied on a British National Grid or Latitude and Longitude coordinates provided on an ETRS89 projection, and display the Local Authority address elements or the Royal Mail address elements where matched.
AddressBase provides a current view of all Royal Mail PAF addresses that have been matched to the NLPG and OSG . The product provides Royal Mail attribution as well as enhancing PAF with X and Y coordinates on the British National Grid and ETRS89 coordinate reference system and providing the classification of an address to a primary level (see the classification scheme page for further details on classification levels). It also provides a primary level classification.
This product will provide you with a single view of an address, allow you to locate this address on a map to give you a geographic view and carry out primary analysis on the function of the address to determine, for example, residential from commercial properties.
This release note provides information about the June 2024 release of the AddressBase products. These products were released to customers on 27th June 2024.
Product | Full Supply Record Count[1] | Change-Only Update Record Count[2] |
---|---|---|
There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.
The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.
If you are unsure of your supply type, please check this with your OS Relationship Manager.
If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an MGBS supply,and also how many tiles are affected if you take your supply as Changed Chunks.
The following information relates to the currency of the source data used in the creation of Epoch 111:
Affected output formats: CSV and GML
There are 6 189 Unique Property Reference Numbers (UPRNs) which reference a Parent UPRN which cannot be found in the product. This is because the Parent UPRN is either provisional or historic and is not matched to the Royal Mail Postcode Address File (PAF) or Valuation Office Agency (VOA) record, meaning that it is not included in the AddressBase Plus product as per the existing background logic rules.
There are 254 records with a sao_start_no or sao_text that have no Parent UPRN in the product. This is because the Parent UPRN is a historical record which is included as part of the logic for record inclusion in the AddressBase Plus product.
The match rates for Council Tax and Non-Domestic Rates for Epoch 111 are detailed as follows based on Valuation Office Agency (VOA) records up to 20th May 2024. The match rate is applicable to the AddressBase Premium product.
Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in 40 932 more tertiary classifications present in Epoch 111 compared to Epoch 110. Indeed, 88.74% of these tertiary classification improvements are against residential codes.
The following graph shows the number of Postcode Address File (PAF) matched records in AddressBase by epoch:
The next release of AddressBase products, Epoch 112, is scheduled for 15th August 2024.
These counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.
Change-Only Updates are not available for the OS Open UPRN product.
This release note provides information about the May 2024 release of the AddressBase products. These products were released to customers on 16 May 2024.
Product | Full Supply Record Count[1] | Change-Only Update Record Count[2] |
---|
There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.
The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.
If you are unsure of your supply type, please check this with your OS Relationship Manager.
If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an MGBS supply,and also how many tiles are affected if you take your supply as Changed Chunks.
The following information relates to the currency of the source data used in the creation of Epoch 110:
Affected output formats: CSV and GML
There are 5 420 Unique Property Reference Numbers (UPRNs) which reference a Parent UPRN which cannot be found in the product. This is because the Parent UPRN is either provisional or historic and is not matched to the Royal Mail Postcode Address File (PAF) or Valuation Office Agency (VOA) record, meaning that it is not included in the AddressBase Plus product as per the existing background logic rules.
There are 240 records with a sao_start_no or sao_text that have no Parent UPRN in the product. This is because the Parent UPRN is a historical record which is included as part of the logic for record inclusion in the AddressBase Plus product.
The match rates for Council Tax and Non-Domestic Rates for Epoch 110 are detailed as follows based on Valuation Office Agency (VOA) records up to 08 April 2024. The match rate is applicable to the AddressBase Premium product.
Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in 38 568 more tertiary classifications present in Epoch 110 compared to Epoch 109. Indeed, 88.75% of these tertiary classification improvements are against residential codes.
The following graph shows the number of Postcode Address File (PAF) matched records in AddressBase by epoch:
The next release of AddressBase products, Epoch 111, is scheduled for 27th June 2024.
These counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.
Change-Only Updates are not available for the OS Open UPRN product.
All four of the AddressBase products are available as Comma-Separated Value (CSV) files. AddressBase, AddressBase Plus and AddressBase Premium are also available as Geography Markup Language (GML). AddressBase Core is also available as a GeoPackage.
Comma-separated value (CSV) files are a delimited text file that use commas or other characters to separate individual elements of a feature. It is used to store data, often in the form of a table. These tables can be freely loaded into databases and programs allowing for the easy loading and updating of data holdings.
The supply of AddressBase products in the CSV format means:
There will be one record per line in each file.
Fields will be separated by commas.
Character strings will be encapsulated with double quotation marks.
No comma will be placed at the end of each row in the file.
Records will be terminated by Carriage Return/Line Feed.
For AddressBase Core the first line of the CSV file will be the Header row. Other AddressBase products have a separate Header file that is available on the product support page and can be combined with the data to give a structure tabular view. Instructions to do this are provided in the relevant Getting Started Guides on the Product Support pages.
The Geography Markup Language (GML) Encoding standard is an Extensible Markup Language (XML) grammar for expressing geographical features. XML schemas are used to define and validate the format and content of GML. The XML specifications that GML is based on are available from the World Wide Web Consortium (W3C) website: More information can be found in the Open Geospatial Consortium (OGC) document, Geography Markup Language v3.2.1.
The GML 3.2 specification provides a set of schemas that define the GML feature constructs and geometric types. These are designed to be used as a basis for building application-specific schemas, which define the data content.
More information on the XML schemas can be found in the product technical specification.
GeoPackage (GPKG) is an open, standards-based data format as defined by the Open Geospatial Consortium (OGC). It is designed to be a lightweight format that can contain large amounts of varied and complex data in a single, easy-to-distribute and ready-to-use file. Please be advised that older versions of GIS software may need updating before being able to display and interact with GeoPackage files.
GeoPackage offers the following benefits:
The single file is easy to transfer and offers the end-user a rich experience.
Attribute names are not limited in length making it user-friendly.
No file size limit so lots of data can be easily accommodated.
Supports raster, vector and database formats making it a highly versatile solution.
It is an OGC Standard.
In most cases, it is a Plug and Play format.
AddressBase products incorporate a web-based ordering system that allows customers to order initial data supply and updates, obtain price estimates and view details of their data holdings on demand.
AddressBase Core is provided as a single file which will contain all records regardless of format and supply option: full supply or COU.
The AddressBase, AddressBase Plus and AddressBase Premium products have been split into chunks of smaller data. The primary supply mechanism is referred to as non-geographic chunks. This is the main mechanism for the delivery of data.
Public Sector Geospatial Agreement (PSGA) customers are able to order all AddressBase products via geographic chunks (5km tiles). Address records are provided in individual files, which represent each 5km tile ordered.
Non-geographic chunking is a way of dividing up data into chunks that are supplied in separate volumes that have a fixed maximum number of records, as opposed to a given geographic National Grid area. For this reason, it is possible for features from various geographic locations to appear in one volume and for adjacent features to appear in different volumes.
Non-geographic chunk volumes are designed to be loaded into spatial databases, but can be used in a file format as long as all chunks are translated or imported into the system at the same time.
CSV files can supply a maximum of one million complete address records within one volume, when this limit is reached, a new volume will be started.
For the GML supply a maximum of 200 000 features will be provided in one volume before the next one is started.
For data that is supplied in 5km-by-5km chunks, the file name will reference the 1km tile in the south-west corner of the 5km tile.
Based on your area of interest (AOI), for example the boundary of your local authority, a 5km-by-5km grid covering the area of interest is generated.
All features within each 5km grid that intersects the AOI are added to a geographic chunk file. Geographic chunking is performed using the standard Ordnance Survey National Grid.
AddressBase products provide address data for England, Wales and Scotland.
A national set of AddressBase, known as a Managed GB Set (MGBS) service is a way of processing identical orders faster, which improves delivery times. All records within England, Wales and Scotland will be provided. If you are signed up to an MGBS service you will benefit from:
Data arriving faster and in a more predictable manner.
Seeing the same version of features as other organisations.
Easier data management – no need to manage your order beyond signing up.
For PSGA customers, MGBS will be supplied as geographic or non-geographic chunks. For non-PSGA users, MGBS will be supplied as non-geographic chunks.
Customers may provide their own area of interest (AOI) in any standard GIS format.
You can supply us with a polygon or you can digitise a polygon within our online ordering service.
Customers are able to take a full supply for all AddressBase products. An easier way to manage the addressing data which each product release is to take change-only updates (COU)
A Full Supply is a resupply of all addressable features in each product each time it is released. This may require you to delete to current holding and replace this with the newly supplied product on each product refresh.
AddressBase Core in GeoPackage format is only available as a Full Supply each week.
Change-only update (COU) is a supply of features which have been created, changed or deleted in a customer’s area of interest since their last supply.
Any feature which has not undergone one of the above changes since a customer’s last supply will not be supplied as part of a COU.
COU will be supplied on a weekly basis for AddressBase Core CSV or a six-weekly basis for AddressBase, AddressBase Plus and AddressBase Premium.
A Geographic chunked COU is not supplied as per the Non-Geographic chunked COU outlined above. For a specified 5km tile, all features within the tile will be supplied should any of the individual features change.
This means the user will need to remove all features that previously existed in the provided tile(s) and insert the entire new tile(s) in its place.
This enumeration is used in association with the attribute ChangeType/CHANGE_TYPE. This enumeration identifies the type of change that has been made to a feature.
Value | Description |
---|
This code list is used in association with the attribute country/COUNTRY found on the BLPU table. The code list describes within which country the address feature falls within.
Value | Description |
---|
This enumeration is used in association with the attribute blpuState/BLPU_STATE. This enumeration describes the physical nature of the address record.
Value | Description |
---|
The Unique Property Reference Number (UPRN) is the persistent identifier providing consistency across the AddressBase products range.
Each address record has a UPRN, which provides a reference key to join related address records across different datasets.
Throughout its life cycle, information on the address of a property can change. This may be due to a change of name, change of use, or the eventual demolition of the property. All these changes are reflected against the same UPRN meaning that users are aware that it is the same physical property.
Please be aware that the UPRN is not the Primary Key for all tables within the and supply. Please see the relational models in and for more information.
AddressBase products has two coordinate reference systems (CRS) present within the data:
British National Grid (BNG)
European Terrestrial Reference System 89 (ETRS89)
BNG uses the OSGB36 geodetic datum and a single Transverse Mercator projection for the whole of Great Britain. Positions on this projection are described using Easting and Northing coordinates in units of metres. The BNG is a horizontal spatial reference system only; it does not specify a vertical (height) reference system.
ETRS89 is the EU-recommended frame of reference for European data and is represented as Latitude and Longitude values. ETRS89 is a horizontal spatial reference system only; it does not specify a vertical (height) reference system.
View our .
There are many Date columns within the AddressBase product. Where a type format of Date has been used in the above attribute tables, the data will be defined in the following format.
Value | Type | Notes |
---|
This code list is used in association with the attribute addressbasePostalCode/ADDRESSBASE_POSTAL_CODE found on the BLPU table. The code list describes the record as postal or not as defined by Addressbase logic.
Value | Description |
---|
Product | MGBS Full Count | National AOI Full Count | Difference |
---|---|---|---|
Change Type | Count |
---|---|
Change Type | Count |
---|---|
AddressBase Premium Table | Inserts | Updates | Deletes |
---|---|---|---|
Data Source | Date |
---|---|
Product | MGBS Full Count | National AOI Full Count | Difference |
---|---|---|---|
Change Type | Count |
---|---|
Change Type | Count |
---|---|
AddressBase Premium Table | Inserts | Updates | Deletes |
---|---|---|---|
Product | MGBS Full Count | National AOI Full Count | Difference |
---|---|---|---|
Change Type | Count |
---|---|
Change Type | Count |
---|---|
AddressBase Premium Table | Inserts | Updates | Deletes |
---|---|---|---|
Data Source | Date |
---|---|
Data Source | Records Received | % Matched |
---|---|---|
Product | MGBS Full Count | National AOI Full Count | Difference |
---|
Change Type | Count |
---|
Change Type | Count |
---|
AddressBase Premium Table | Inserts | Updates | Deletes |
---|
Data Source | Date |
---|
AddressBase products can be ordered via DVD or Secure File Transfer Protocol (SFTP).
OS OpenUPRN
40 873 566
N/A
AddressBase
30 528 787
164 532
AddressBase Plus
38 125 445
864 998
AddressBase Premium
See rows below
See rows below
Street
1 508 646
7531
Street Descriptor
1 631 995
5970
BLPU
40 873 566
462 545
Classification
44 728 771
175 302
LPI
46 041 542
231 655
Organisation
1 421 542
25 452
Delivery Point Address
30 635 054
74 237
Application Cross Ref.
198 155 853
843 499
Successor
0
0
AddressBase
30 528 787
30 528 787
0
AddressBase Plus
38 125 445
38 125 425
20
AddressBase Premium
See rows below
See rows below
See rows below
Street
1 508 646
1 508 643
3
Street Descriptor
1 631 995
1 631 992
3
BLPU
40 873 566
40 873 542
24
Classification
44 728 771
44 728 747
24
LPI
46 041 542
46 041 517
25
Organisation
1 421 542
1 421 540
2
Delivery Point Address
30 635 054
30 635 054
0
Application Cross Ref.
198 155 853
198 155 829
24
Successor
0
0
0
Inserts
46 546
Updates
107 529
Deletes
10 457
COU Populated Tile Count
5 390
Inserts
58 383
Updates
791 040
Deletes
15 575
COU Populated Tile Count
7 931
Street
1 527
5 822
182
Street Descriptor
1 751
4 032
187
BLPU
51 831
406 735
3 979
Classification
64 820
89 524
20 958
LPI
67 711
159 116
4 828
Organisation
9 398
6 111
9 943
Delivery Point Address
46 773
17 519
9 945
Application Cross Ref.
237 145
560 552
45 802
Royal Mail PAF
11 July 2024
National Land and Property Gazetteer
11 July 2024
One Scotland Gazetteer
17 June 2024
VOA Non-Domestic Rates
08 July 2024
VOA Council Tax
08 July 2024
OS MasterMap Topography Layer
25 June 2024
OS MasterMap Highways Network
04 July 2024
Code-Point with Polygons
01 July 2024
Boundary-Line
24 June 2024
Data Source
Records Received
% Matched
Council Tax
27 116 559
99.92
Non-Domestic Rates
2 123 229
96.47
OS OpenUPRN
40 744 085
N/A
AddressBase
30 440 058
141 664
AddressBase Plus
38 013 634
641 116
AddressBase Premium
See rows below
See rows below
Street
1 504 346
5 403
Street Descriptor
1 627 151
2 603
BLPU
40 744 085
1 651 993
Classification
44 612 110
167 219
LPI
45 869 982
152 914
Organisation
1 415 880
17 270
Delivery Point Address
30 544 920
69 763
Application Cross Ref.
197 640 540
614 650
Successor
0
0
AddressBase
30 440 058
30 440 058
0
AddressBase Plus
38 013 634
38 013 615
19
AddressBase Premium
See rows below
See rows below
See rows below
Street
1 504 346
1 504 345
1
Street Descriptor
1 627 151
1 627 150
1
BLPU
40 744 085
40 744 062
23
Classification
44 612 110
44 612 087
23
LPI
45 869 982
45 869 958
24
Organisation
1 415 880
1 415 878
2
Delivery Point Address
30 544 920
30 544 920
0
Application Cross Ref.
197 640 540
197 640 517
23
Successor
0
0
0
Inserts
38 002
Updates
91 196
Deletes
12 466
COU Populated Tile Count
5 410
Inserts
55 152
Updates
571 494
Deletes
14 470
COU Populated Tile Count
7 157
Street
1 560
3 826
17
Street Descriptor
1 603
982
18
BLPU
54 407
1 594 091
3 495
Classification
68 978
75 921
22 320
LPI
67 818
80 668
4 428
Organisation
7 066
5 090
5 114
Delivery Point Address
38 799
18 094
12 870
Application Cross Ref.
225 972
348 380
40 298
Data Source
Date
Royal Mail PAF
01 March 2024
National Land and Property Gazetteer
01 March 2024
One Scotland Gazetteer
12 February 2024
VOA Non-Domestic Rates
26 February 2024
VOA Council Tax
26 February 2024
OS MasterMap Topography Layer
20 February 2024
OS MasterMap Highways Network
06 February 2024
Code-Point with Polygons
04 January 2024
Boundary-Line
03 October 2023
Data Source
Records Received
% Matched
Council Tax
27 033 727
99.95
Non-Domestic Rates
2 120 769
96.58
UPRN
Local Authority current address
PAF Address – Royal Mail addresses
PAF UDPRN – Royal Mail’s delivery reference system
Single line address
Simple classification
Advanced classification
Cross-reference with third party datasets
Alternate addresses
Lifecycle data
OS OpenUPRN
40 825 714
N/A
AddressBase
30 492 698
123 335
AddressBase Plus
38 082 637
2 269 935
AddressBase Premium
See rows below
See rows below
Street
1 507 301
5 983
Street Descriptor
1 630 431
3 057
BLPU
40 825 714
345 400
Classification
44 684 909
124 243
LPI
45 978 659
140 285
Organisation
1 422 087
17 612
Delivery Point Address
30 598 226
59 126
Application Cross Ref.
197 964 510
4 430 729
Successor
0
0
AddressBase
30 492 698
30 492 698
0
AddressBase Plus
38 082 637
38 082 617
20
AddressBase Premium
See rows below
See rows below
See rows below
Street
1 507 301
1 507 299
2
Street Descriptor
1 630 431
1 630 429
2
BLPU
40 825 714
40 825 690
24
Classification
44 684 909
44 684 885
24
LPI
45 978 659
45 978 634
25
Organisation
1 422 087
1 422 085
2
Delivery Point Address
30 598 226
30 598 226
0
Application Cross Ref.
197 964 510
197 964 486
24
Successor
0
0
0
Inserts
33 506
Updates
80 002
Deletes
9 827
COU Populated Tile Count
5 140
Inserts
45 949
Updates
2 210 934
Deletes
13 052
COU Populated Tile Count
7 162
Street
1 515
4 445
23
Street Descriptor
1 715
1 318
24
BLPU
45 313
296 305
3 782
Classification
54 659
51 341
18 243
LPI
60 087
75 180
5 018
Organisation
7 895
4 900
4 817
Delivery Point Address
33 606
16 076
9 444
Application Cross Ref.
2 114 566
373 554
1 942 609
Royal Mail PAF
23 May 2024
National Land and Property Gazetteer
23 May 2024
One Scotland Gazetteer
06 May 2024
VOA Non-Domestic Rates
20 May 2024
VOA Council Tax
20 May 2024
OS MasterMap Topography Layer
14 May 2024
OS MasterMap Highways Network
07 May 2024
Code-Point with Polygons
04 January 2024
Boundary-Line
01 May 2023
Council Tax
27 084 483
99.94
Non-Domestic Rates
2 123 193
96.48
OS OpenUPRN | 40 784 183 | N/A |
AddressBase | 30 469 019 | 134 626 |
AddressBase Plus | 38 049 740 | 578 629 |
AddressBase Premium | See rows below | See rows below |
Street | 1 505 809 | 7 967 |
Street Descriptor | 1 628 740 | 2 522 |
BLPU | 40 784 183 | 324 106 |
Classification | 44 648 493 | 127 133 |
LPI | 45 923 590 | 137 049 |
Organisation | 1 419 009 | 16 669 |
Delivery Point Address | 30 574 064 | 69 329 |
Application Cross Ref. | 197 792 553 | 716 937 |
Successor | 0 | 0 |
AddressBase | 30 469 019 | 30 469 019 | 0 |
AddressBase Plus | 38 049 740 | 38 049 721 | 19 |
AddressBase Premium | See rows below | See rows below | See rows below |
Street | 1 505 809 | 1 505 808 | 1 |
Street Descriptor | 1 628 740 | 1 628 739 | 1 |
BLPU | 40 784 183 | 40 784 160 | 23 |
Classification | 44 648 493 | 44 648 470 | 23 |
LPI | 45 923 590 | 45 923 566 | 24 |
Organisation | 1 419 009 | 1 419 007 | 2 |
Delivery Point Address | 30 574 064 | 30 574 064 | 0 |
Application Cross Ref. | 197 792 553 | 197 792 530 | 23 |
Successor | 0 | 0 | 0 |
Inserts | 40 382 |
Updates | 82 823 |
Deletes | 11 421 |
COU Populated Tile Count | 5 315 |
Inserts | 49 477 |
Updates | 515 781 |
Deletes | 13 371 |
COU Populated Tile Count | 7 232 |
Street | 1 489 | 6 452 | 26 |
Street Descriptor | 1 615 | 881 | 26 |
BLPU | 43 791 | 276 622 | 3 693 |
Classification | 57 868 | 47 780 | 21 485 |
LPI | 57 875 | 74 907 | 4 267 |
Organisation | 7 721 | 4 356 | 4 592 |
Delivery Point Address | 40 777 | 16 919 | 11 633 |
Application Cross Ref. | 197 994 | 472 962 | 45 981 |
Royal Mail PAF | 11 April 2024 |
National Land and Property Gazetteer | 11 April 2024 |
One Scotland Gazetteer | 25 March 2024 |
VOA Non-Domestic Rates | 08 April 2024 |
VOA Council Tax | 08 April 2024 |
OS MasterMap Topography Layer | 03 April 2024 |
OS MasterMap Highways Network | 06 March 2024 |
Code-Point with Polygons | 04 January 2024 |
Boundary-Line | 03 October 2023 |
Data Source | Records Received | % Matched |
Council Tax | 27 058 858 | 99.92 |
Non-Domestic Rates | 2 123 768 | 96.44 |
I | Insert |
U | Update |
D | Delete |
E | This record is within England |
W | This record is within Wales |
S | This record is within Scotland |
N | This record is within Northern Ireland |
L | This record is within the Channel Islands |
M | This record is within the Isle of Man |
J | This record is not assigned to a country as it falls outside of the land boundaries used. |
1 | under construction |
2 | In use |
3 | Unoccupied /vacant/derelict |
4 | No longer existing |
6 | Planning permission granted |
2024-10-24 | Date | Date columns will follow the structure: CCYY-MM-DD |
D | A record which is linked to PAF |
N | Not a postal address |
C | A record which is postal and has a parent record which is linked to PAF |
L | A record which is identified as postal based on Local Authority information |
This enumeration is used in association with the logicalStatus/LOGICAL_STATUS attribute found in the BLPU and LPI table. This enumeration provides a value to show the lifecycle stage of the address record.
Value | Description |
---|---|
BLPU records will not have a logical status value of 3, whereas LPI records can have all of the values expressed above.
This enumeration is used in association with the attribute fileType/FILE_TYPE found in the Header record. This enumeration allows the identification of either a change-only update (COU) supply or a full supply.
Value | Description |
---|---|
This enumeration is used in association with the officialFlag/OFFICIAL_FLAG attribute. This enumeration is an indicator of whether an address record corresponds to an entry in the official Street Name and Numbering register.
Value | Description |
---|---|
This enumeration is used in association with the postcodeType/POSTCODE_TYPE attribute. This enumeration identifies the code used by Royal Mail to describe the user as a small or large user. This is defined for postal services based on the number of letters delivered to that user.
Value | Description |
---|---|
This enumeration is used in association with the recordType/RECORD_TYPE attribute found in the Street table. This enumeration identifies the record type of the street record.
Value | Description |
---|---|
This enumeration is used in association with the stateCode/STATE_CODE attribute. This enumeration describes the physical nature of the address record.
Value | Description |
---|---|
This enumeration is used in association with the streetClassification/STREET_CLASSIFICATION attribute found in the Street table. The enumeration provides a value denoting the primary classification of the street record.
Value | Description |
---|---|
This enumeration is used in association with the LANGUAGE attribute found in the Street Descriptor and LPI tables; and also the Metadata table for CSV supply. This enumeration identifies the language of the address displayed.
This is not required for the GML supply as the Language is specified in the GML tag ‘xml:lang’.
Value | Description |
---|---|
This enumeration is used in association with the rpc/RPC attribute. This enumeration identifies the accuracy value of the coordinates allocated to the address.
Value | Description | Implementation notes |
---|---|---|
There are columns within the AddressBase product which provide a Time value. Where this is declared, the data will be provided in the following format.
Value | Type | Notes |
---|---|---|
This enumeration is used in association with the state/STATE attribute found in the street table. This enumeration identifies at which point the street record is within its lifecycle.
Value | Description |
---|
This enumeration is used in association with the usrnMatchIndicator/USRN_MATCH_INDICATOR attribute found in the LPI table. This enumeration identifies how the USRN has been allocated to an address record.
Value | Description |
---|
This enumeration is used in association with the streetSurface/STREET_SURFACE attribute found in the Street table. This enumeration identifies the surface finish of the street.
Value | Description |
---|
It is important that COUs are processed with Deletes first, then Inserts and Updates; this is to ensure that updates are applied in the correct order. Guidance on this can be found in the Working with COU data page in the .
It is important that COUs are processed with Deletes first, then Inserts and Updates; this is to ensure that updates are applied in the correct order. Guidance on this can be found in the Working with COU data page in the .
It is important that COUs are processed with Deletes first, then Inserts and Updates; this is to ensure that updates are applied in the correct order. Guidance on this can be found in the Working with COU data page in the .
It is important that COUs are processed with Deletes first, then Inserts and Updates; this is to ensure that updates are applied in the correct order. Guidance on this can be found in the Working with COU data page in the .
It is important that COUs are processed with Deletes first, then Inserts and Updates; this is to ensure that updates are applied in the correct order. Guidance on this can be found in the Working with COU data page in the .
1
Approved
3
Alternative
6
Provisional
8
Historical
F
Signifies the supply is a full supply
C
Signifies the supply is a COU file
N
Unofficial Address
Y
Official Address
S
A small user, for example, a residential property
L
A large user, for example, a large commercial company
1
Official designated Street Name
2
Street Description
3
Numbered Street
4
Unofficial Street Description
9
Description used for LLPG Access
1
Under construction
2
In use
3
Unoccupied / vacant / derelict
4
No longer existing
6
Planning permission granted
4
Pedestrian way or footpath
6
Cycletrack or cycleway
8
All vehicles
9
Restricted byway
10
Bridleway
ENG
English
CYM
Welsh
GAE
Gaelic (Scottish)
BIL
Bilingual
1
Central Internal Position
The address seed is contained within an OS MasterMap Topography Layer building and within 2.5m of its calculated centre.
Or
The seed is in the best possible position based on the nature of the premises, for example, Development Land, House Boat, Wind Farm.
2
General Internal Position
The address seed is contained within an OS MasterMap Topography Layer building but is more than 2.5m away from its calculated centre.
Or
The seed is in an internal position based on the nature of the premises, for example, Development Land, House Boat.
3
Transitional Position
The address seed has been changed from provisional to live in the last six months. It has been captured to a high level of positional accuracy, but the OS MasterMap Topography Layer feature is not yet captured.
Please note the address seed will only be moved pending any imminent mapping updates.
4
Street Location
The address seed is plotted in accordance with the declared street start or end coordinates.
Please note this is the highest accuracy possible for Street Records.
5
Postcode Unit Position
The address seed has been captured to Postcode Unit level. It will be updated when more information becomes available.
9
Low accuracy – marked for priority review
This address seed has been captured to a lower level of accuracy and will be updated as a priority over the coming releases.
14:11:15
Time
Time will follow the structure of HH:MM:SS based on a 24-hour clock.
1 | Under construction |
2 | Open |
4 | Permanently closed (STREET_END_DATE must be entered) |
1 | Matched manually to the nearest accessible Street. |
2 | Matched spatially to the nearest USRN. Not necessarily the access street. |
1 | Metalled |
2 | UnMetalled |
3 | Mixed |
114 | 07 November 2024 | 03 October 2024 |
115 | 19 December 2024 | 14 November 2024 |
116 | 06 February 2025 | 03 Januaary 2025 |
117 | 20 March 2025 | 14 February 2025 |
118 | 01 May 2025 | 28 March 2025 |