Live RenoCost Statistics

The canonical historical dataset behind this page contains one row per unique completed RenoCost calculator session. Sessions are deduplicated by session identifier so that no completed session is counted more than once.

Modern records use a unified session identifier recorded at the point of completion. Eligible legacy detailed records that predate this identifier were matched to their originating session using a reciprocal one-to-one nearest-time match, capped at 600 seconds between the two records. A detailed source can never be assigned to more than one session, and a session can never be assigned more than one competing detailed source. Any match that was uncertain or ambiguous was excluded rather than guessed. Historical fields that cannot be recovered remain NULL — missing values are never inferred or estimated.

Full postcodes are never published and no personally identifiable information is included anywhere in this dataset. Postcode-derived information is only ever used to group estimates into broad UK regions.

Each chart on this page uses only the records that contain the specific fields that chart requires, so the qualifying sample size differs between analyses — the sample size used for each chart is shown alongside it.

Test, incomplete, duplicate and clearly invalid submissions are excluded from public statistics wherever they can be reliably identified. Categories or regions with fewer than 10 qualifying records are combined into "Other" or hidden. Findings based on between 10 and 29 qualifying records are labelled as an emerging trend.

RenoCost users are self-selecting. These findings represent activity recorded through RenoCost and are not a nationally representative survey of UK homeowners — popularity among RenoCost users should not be read as a measure of UK-wide demand. Calculator values are indicative planning estimates only; they are not confirmed homeowner expenditure and not contractor quotations.

Dated methodology note: the reciprocal nearest-time matching described above (600-second cap) was applied once to reconcile legacy pre-unified-identifier records with completed sessions. It is not re-run against new data, which already carries the unified session identifier.