BIZTRAC BETA
Development of building projects

OLE BRUMMS HAGE AS

Org. no. 930767077 Limited company (AS) Trondheim Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 90.2m
Operating profit NOK 18.6m
Equity NOK 13.0m
Incorporated 2023
Share capital NOK 30,000

OLE BRUMMS HAGE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 930767077. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Bygging og utvikling av bolig- og næringsbygg og det som står i sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 90.2m in revenue and NOK 18.6m in operating profit.

Key figures · 2025

Revenue
NOK 90.2m
Operating profit
NOK 18.6m
Equity
NOK 13.0m
Est. value
NOK 51.2m

Financial health · 2025

Liquidity
0.95
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.3%
Weak
Equity as a share of total capital

Who owns OLE BRUMMS HAGE AS?

LA67 OG OBH UTVIKLING AS
OLE BRUMMS HAGE AS
NOK 90.2m rev. · NOK 18.6m profit

OLE BRUMMS HAGE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OLE BRUMMS HAGE AS own?

OLE BRUMMS HAGE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OLE BRUMMS HAGE AS

Who owns OLE BRUMMS HAGE AS?

LA67 OG OBH UTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of OLE BRUMMS HAGE AS?

OLE BRUMMS HAGE AS had revenue of NOK 90.2m in 2025.

Who is the general manager of OLE BRUMMS HAGE AS?

Christoffer Søbstad is registered as general manager of OLE BRUMMS HAGE AS.

Where is OLE BRUMMS HAGE AS based?

OLE BRUMMS HAGE AS has its business address in Trondheim.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.