> 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-february-2025-epoch-116.md).

# AddressBase Products February 2025 – Epoch 116

This release note provides information about the February 2025 (Epoch 116) release of the AddressBase products. These products were released to customers on 06 February 2025.

Known issues will now be displayed on the 'Product Known Data Issues' subpages under each product.

## Record counts

<table><thead><tr><th width="253">Product</th><th>Full Supply Record Count</th><th>Change-Only Update Record Count</th></tr></thead><tbody><tr><td>OS Open UPRN</td><td>41,011,955</td><td>N/A</td></tr><tr><td>AddressBase</td><td>30,652,138</td><td>157,150</td></tr><tr><td>AddressBase Plus</td><td>38,252,424</td><td>582,353</td></tr><tr><td>AddressBase Premium</td><td>See rows below</td><td>See rows below</td></tr><tr><td>Street</td><td>1,513,089</td><td>5,202</td></tr><tr><td>Street Descriptor</td><td>1,636,881</td><td>2,918</td></tr><tr><td>BLPU</td><td>41,011,955</td><td>320,110</td></tr><tr><td>Classification</td><td>44,837,171</td><td>154,389</td></tr><tr><td>LPI</td><td>46,230,831</td><td>129,683</td></tr><tr><td>Organisation</td><td>1,407,564</td><td>16,239</td></tr><tr><td>Delivery Point Address</td><td>30,761,334</td><td>69,996</td></tr><tr><td>Application Cross Ref.</td><td>198,758,385</td><td>736,674</td></tr><tr><td>Successor</td><td>0</td><td>0</td></tr></tbody></table>

{% hint style="info" %}

* 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.
* Please note that Change-Only Updates (COUs) are not available for the OS Open UPRN product.
  {% endhint %}

## 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            | 30,652,138      | 30,652,138              | 0              |
| AddressBase Plus       | 38,252,424      | 38,252,403              | 21             |
| AddressBase Premium    | See rows below  | See rows below          | See rows below |
| Street                 | 1,513,089       | 1,513,086               | 3              |
| Street Descriptor      | 1,636,881       | 1,636,878               | 3              |
| BLPU                   | 1,011,955       | 41,011,930              | 25             |
| Classification         | 44,837,171      | 44,837,146              | 25             |
| LPI                    | 6,230,831       | 46,230,805              | 26             |
| Organisation           | 407,564         | 1,407,562               | 2              |
| Delivery Point Address | 30,761,334      | 30,761,334              | 0              |
| Application Cross Ref. | 198,758,385     | 198,758,360             | 25             |
| Successor              | 0               | 0                       | 0              |

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 AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data.md).

## 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                  | 43,892  |
| Updates                  | 103,297 |
| Deletes                  | 9,961   |
| COU Populated Tile Count | 5,743   |

### AddressBase Plus

| Change Type              | Count   |
| ------------------------ | ------- |
| Inserts                  | 48,887  |
| Updates                  | 521,021 |
| Deletes                  | 12,445  |
| COU Populated Tile Count | 6,909   |

### AddressBase Premium

<table><thead><tr><th width="187">AddressBase Premium Table</th><th>Inserts</th><th>Updates</th><th>Deletes</th></tr></thead><tbody><tr><td>Street</td><td>1,633</td><td>3,535</td><td>34</td></tr><tr><td>Street Descriptor</td><td>1,684</td><td>1,194</td><td>40</td></tr><tr><td>BLPU</td><td>42,757</td><td>274,322</td><td>3,031</td></tr><tr><td>Classification</td><td>52,337</td><td>82,401</td><td>19,651</td></tr><tr><td>LPI</td><td>57,853</td><td>67,612</td><td>4,218</td></tr><tr><td>Organisation</td><td>4,337</td><td>4,480</td><td>7,422</td></tr><tr><td>Delivery Point Address</td><td>44,752</td><td>15,200</td><td>10,044</td></tr><tr><td>Application Cross Ref.</td><td>192,512</td><td>509,368</td><td>34,794</td></tr></tbody></table>

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 116:

| Data Source                          | Date             |
| ------------------------------------ | ---------------- |
| Royal Mail PAF                       | 02 January 2025  |
| National Land and Property Gazetteer | 02 January 2025  |
| One Scotland Gazetteer               | 09 December 2024 |
| VOA Non-Domestic Rates               | 23 December 2024 |
| VOA Council Tax                      | 23 December 2024 |
| OS MasterMap Topography Layer        | 28 November 2024 |
| OS MasterMap Highways Network        | 05 December 2024 |
| Code-Point with Polygons             | 02 January 2025  |
| Boundary-Line                        | 02 October 2024  |

## Improvements in Epoch 116

### Valuation Office Agency matching

The match rates for Council Tax and Non-Domestic Rates for Epoch 116 are detailed as follows based on Valuation Office Agency (VOA) records up to **23 December 2024**. The match rate is applicable to the AddressBase Premium product.

| Data Source        | Records Received | % Matched |
| ------------------ | ---------------- | --------- |
| Council Tax        | 27,227,905       | 99.92     |
| Non-Domestic Rates | 2,120,341        | 96.44     |

### Tertiary classifications

Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in **49 241** more tertiary classifications present in **Epoch 116** compared to **Epoch 115**. Indeed, **88.69 %** of these tertiary classification improvements are against residential codes.

## Next release

The next release of AddressBase products, Epoch **117**, is scheduled for **20 March 2025**.


---

# 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-february-2025-epoch-116.md?ask=<question>&goal=<user_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.