Developer · London
Omenport Developments.
A developer bringing schemes forward across London. Has 4 applications in 1 borough, at a 3 approved · 1 refused approval rate, 2005–06.[1] Where they build, and how, is below.
Developer1 borough3 approved · 1 refused approval
Where they build — by borough · tap to focus
FewerMore applications
At a glanceEach metric links to the investigation behind it
All investigations →4
Applications
London 2005–06
Full / major planning
Mostly submits
2 applications of this type — no proposal states a residential unit count
0
Refusals overturned
no refusal has been overturned at appeal
Why is Omenport Developments listed as a developer?It is recorded as the applicant bringing forward 4 applications.
Record component
Applications
Approval rate
Basis
Omenport Developments
4
—
Organisation name or verified alias recorded as the applicant
Omenport Developments
4
—
Organisation name or verified alias recorded as the applicant
Possible matches that cannot be tied to this checked identity are excluded rather than guessed.
Something not right?
Worked on an application here but didn't submit it? Team credits — architects and project teams shown on schemes they worked on — are coming. Claim your profile and we'll tell you when it's live.
Approval rate over time — improving or slippingtheir London-wide rate by year
What they build — by scheme type
Click a slice to reshade the London map by that type.
Their planning record — policies in play
The policies most in play across this developer's schemes — how often each appears, and how often a scheme citing it wins consent.
Policies are coded from each officer report and decision notice — this table publishes when decision-notice ingestion lands. No policy record is shown until it's real.
Case officers — win rate when this developer submits
How often each named case officer grants consent on this developer's schemes. Pairing patterns from the public register — not endorsements.
The officer↔developer pairing isn't joined in the data layer yet — this table publishes when it is. Each borough's officers are already ranked in Track Records.
Applications by borough
Outcomes secured — S106 by borough
S106 outcomes per unit aren't traced per developer yet — the borough-by-borough table publishes when the section 106 agreements and committee reports are ingested against this developer's consents.
Recent applications
Address
Borough
Type
Outcome
Date
Islington
Full Planning Application
Refused
2006-07-24
Islington
Listed Building
Approved
2006-07-24
Islington
Full Planning Application
Approved
2005-08-08
Islington
Listed Building
Approved
2005-08-08
Islington
Full Planning Application
Refused
2006-07-24
Islington
Listed Building
Approved
2006-07-24
Islington
Full Planning Application
Approved
2005-08-08
Show all 4 rows
Islington
Listed Building
Approved
2005-08-08
Consultants they instruct— subscriber data
At a glance
DeveloperOmenport Developments
Coverage1 London borough
Applications4 (2005–06)
Units sought—
Approval rate3 approved · 1 refused
London rank#9880 of 14,955
Who decides here
Related investigations
Sources & method
- [1]Applications, approval rate, borough breakdown and units — the planning applications across London on which this company is the named applicant, from borough planning registers. Individual householders are excluded. Units = residential units conservatively parsed from each proposal (sought, not delivered); not every scheme states a count. · methodology
- [2]Agents — the named planning agent on each of this developer’s applications, joined to the London consultant record. · methodology
Methodology is published in full so every number is traceable to its primary source.