> For the complete documentation index, see [llms.txt](https://docs.os.uk/os-downloads/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.os.uk/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes/addressbase-products-september-2026-epoch-130.md). # AddressBase Products September 2026 – Epoch 130 This release note provides information about the September 2026 (Epoch 130) release of the AddressBase products. These products were released to customers on 17 September 2026. ## Record counts | Product | Full Supply Record Count | Change-Only Update Record Count | | ---------------------- | ------------------------ | ------------------------------- | | OS Open UPRN | 41 676 575 | N/A | | AddressBase | 31 000 728 | 136 574 | | AddressBase Plus | 38 860 895 | 971 258 | | AddressBase Premium | See rows below | See rows below | | Street | 1 532 580 | 17 618 | | Street Descriptor | 1 657 099 | 7 043 | | BLPU | 41 676 575 | 820 912 | | Classification | 45 440 946 | 187 787 | | LPI | 47 073 085 | 188 224 | | Organisation | 1 390 423 | 13 553 | | Delivery Point Address | 31 117 915 | 66 769 | | Application Cross Ref. | 201 683 570 | 772 677 | | Successor | 0 | 0 | **Please note:** * The Full Supply record 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 (COUs) are not available for the OS Open UPRN product. ## Product supply comparison 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. | Product | MGBS Full Count | National AOI Full Count | Difference | | ---------------------- | --------------- | ----------------------- | -------------- | | AddressBase | 31 000 728 | 31 000 727 | 1 | | AddressBase Plus | 38 860 895 | 38 860 869 | 26 | | AddressBase Premium | See rows below | See rows below | See rows below | | Street | 1 532 580 | 1 532 578 | 2 | | Street Descriptor | 1 657 099 | 1 657 097 | 2 | | BLPU | 41 676 575 | 41 676 545 | 30 | | Classification | 45 440 946 | 45 440 916 | 30 | | LPI | 47 073 085 | 47 073 054 | 31 | | Organisation | 1 390 423 | 1 390 421 | 2 | | Delivery Point Address | 1 390 423 | 31 117 915 | 0 | | Application Cross Ref. | 201 683 570 | 201 683 540 | 30 | | Successor | 0 | 0 | 0 | It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in '[Working with COU data](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-getting-started-guide/working-with-cou-data.md)' in the AddressBase Getting Started Guide. ## Changed records 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. ### AddressBase | Change Type | Count | | ------------------------ | ------ | | Inserts | 35 618 | | Updates | 90 708 | | Deletes | 10 248 | | COU Populated Tile Count | 5 529 | ### AddressBase Plus | Change Type | Count | | ------------------------ | ------- | | Inserts | 53 641 | | Updates | 984 181 | | Deletes | 13 436 | | COU Populated Tile Count | 7 513 | ### AddressBase Premium | AddressBase Premium Table | Inserts | Updates | Deletes | | ------------------------- | ------- | ------- | ------- | | Street | 1 139 | 16 434 | 45 | | Street Descriptor | 1 245 | 5 752 | 46 | | BLPU | 49 972 | 768 150 | 2 790 | | Classification | 66 427 | 102 935 | 18 425 | | LPI | 63 291 | 121 433 | 3 500 | | Organisation | 4 747 | 4 532 | 4 274 | | Delivery Point Address | 35 858 | 20 890 | 10 021 | | Application Cross Ref. | 0 | 0 | 0 | ## Source data currency The following information relates to the currency of the source data used in the creation of Epoch 130. | Data Source | Date | | ------------------------------------ | -------------- | | Royal Mail PAF | 12 August 2026 | | National Land and Property Gazetteer | 14 August 2026 | | One Scotland Gazetteer | 26 July 2026 | | VOA Non-Domestic Rates | 10 August 2026 | | VOA Council Tax | 11 August 2026 | | OS MasterMap Topography Layer | 04 August 2026 | | OS MasterMap Highways Network | 05 August 2026 | | Code-Point with Polygons | 01 July 2026 | | Boundary-Line | 01 May 2026 | ## Data issues ### AddressBase Details of live and resolved data issues for AddressBase will be communicated on the [AddressBase Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-known-data-issues.md). This page will provide details of their impacts and updates on the expected time frame for their resolution. ### AddressBase Plus issues Details of live and resolved data issues for AddressBase Plus will be communicated on the [AddressBase Plus Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus/addressbase-plus-known-data-issues.md). This page will provide details of their impacts and updates on the expected time frame for their resolution. ### AddressBase Premium Details of live and resolved data issues for AddressBase Premium will be communicated on the [AddressBase Premium Known Data Issues, Service Disruptions and Planned Maintenance page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium/addressbase-premium-known-data-issues-service-disruptions-and-planned-maintenance.md). This page will provide details of their impacts and updates on the expected time frame for their resolution. ## Improvements in Epoch 130 ### Valuation Office Agency matching The match rates for Council Tax and Non-Domestic Rates for Epoch 130 are detailed as follows based on Valuation Office Agency (VOA) records up to 11 August 2026. The match rate is applicable to the AddressBase Premium product. | Data Source | Records Received | % Matched | | ------------------ | ---------------- | --------- | | Council Tax | 27 510 650 | 99.32% | | Non-Domestic Rates | 2 123 085 | 85.18% | ## Next release The next release of AddressBase products, **Epoch 131**, is scheduled for **29 October 2026**. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.os.uk/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes/addressbase-products-september-2026-epoch-130.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.