Transaction volume
The count of registered sales in an area and period, read straight from HM Land Registry Price Paid, not from a matched sample.
Transaction volume, as the data uses it
"How many homes sold in SE22 last year" is a registry question, so MarketCode answers it from the registry: every registered sale, monthly, from 1995, for a postcode district, postcode area or county. The market cube's own count is a UPRN-matched sample that runs well short of the registry. So the platform reads counts from one place and prices from the other, and says which.
Volume is market size, not liquidity. The busiest districts are the largest ones. For "where do homes sell fastest", use turnover. And check the provisional date before the trend: registration lag leaves the trailing months incomplete.
Also called: sales volume, number of sales, transaction count.
Tools that return it
MCP tools your assistant can call. Most have a REST endpoint at the same price.
market_volume_series· See current pricing
Monthly transaction VOLUME for a postcode district, postcode area or county — every registered sale, 1995 to present, oldest month first.market_volume_ranking· See current pricing
market
Where it comes from
- HM Land Registry: Price Paid Data · England and Wales · Open Government Licence v3
Every published market figure follows the windows, sample floors and registration lags on the methodology page.
Where it matters on the map
Use cases whose layers and filters put it in front of you.
Related terms
- Turnover rate
- Sales in a period as a share of the dwellings that could have sold. It measures liquidity; the raw count of sales measures market size.
- Registration lag
- The weeks to months between a sale completing and HM Land Registry registering it. It leaves the latest months of any sold-price series incomplete.