About 27 minutes. Measured on production on 11 October 2026: the 80 feasibility runs that finished and were charged in the previous 30 days took a median of 27.2 minutes each.
That is the time from the moment the run starts to the moment its result is delivered.
The measurement
| Measure | Feasibility runs |
|---|---|
| Finished and charged runs in the 30 days to 11 October 2026 | 80 |
| Median time, start to delivery | 27.2 minutes |
| The middle half of runs | 20.8 to 56.2 minutes |
| One run in ten took longer than | 74.5 minutes |
One query against production, run on 11 October 2026 at 10:12 UTC. It counts every feasibility run started in the 30 days before it that finished and was charged with credits, ours and our clients' alike. The time runs from the start of the run to the delivery of its result; where a run carries no delivery time, the time of its charge is used (15 of the 80). Runs that were stopped or failed are not in it.
Why the spread is wide
The middle half of runs spans about half an hour, and one run in ten takes well over an hour. We have not measured what drives the difference, so we name no cause. Plan for the long end of the table, not the short one.
What comes back
A study of one site. The rules that apply to the parcel, read one by one, with the limit that binds; a scheme tested inside that limit; and what the land value depends on, fact by fact, with a source on every figure.
What it does not mean
- It is not a promise for your site. The table is what happened, not a service level.
- A fast study is not a decision. Whether to seek a variance, which scheme to take forward and what to offer for the land stay with you.
- The output is a draft for a licensed professional on your team to review and sign.
How to see it on your own site
Ask for a demo and name one site you know well: request a demo