BIZTRAC BETA
Construction of residential and non-residential buildings

OMN BYGG AS

Org. no. 935108160 Limited company (AS) Ålesund Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −25,000
Equity NOK −4,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−4k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−25k kr).

OMN BYGG AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 935108160. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Oppføring og rehabilitering av bygninger og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”.

Key figures · 2025

Operating profit
NOK −25,000
Equity
NOK −4,000

Financial health · 2025

Liquidity
3.31
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-51.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns OMN BYGG AS?

KRN HOLDING AS
OMN BYGG AS
· NOK −25,000 profit

OMN BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OMN BYGG AS

Who owns OMN BYGG AS?

KRN HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of OMN BYGG AS?

Ole Marius Fiskerstrand Ness is registered as general manager of OMN BYGG AS.

Where is OMN BYGG AS based?

OMN BYGG AS has its business address in Ålesund.

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.