BIZTRAC BETA
Civil engineering activities

EIENDOMSANALYSE UTVIKLING AS

Org. no. 925141305 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK −49,000
Incorporated 2020
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−49k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).
  • Nylig endring 2026-08-06 Adresseendring registrert 2026-08-06.

EIENDOMSANALYSE UTVIKLING AS is registered as a limited company in Oslo, Oslo with organisation number 925141305. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 60 shares. The company's stated purpose is: “Å eie eiendom og aksjer i selskaper som driver med eiendomsutvikling og eiendomsinvestering, samt annen virksomhet i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −5,000
Equity
NOK −49,000

Financial health · 2025

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

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

Who owns EIENDOMSANALYSE UTVIKLING AS?

MARIUS KRIEG KLAUSEN
EIENDOMSANALYSE UTVIKLING AS
· NOK −5,000 profit

EIENDOMSANALYSE UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EIENDOMSANALYSE UTVIKLING AS own?

EIENDOMSANALYSE UTVIKLING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EIENDOMSANALYSE UTVIKLING AS

Who owns EIENDOMSANALYSE UTVIKLING AS?

MARIUS KRIEG KLAUSEN is the largest registered owner, with 100.0%.

Where is EIENDOMSANALYSE UTVIKLING AS based?

EIENDOMSANALYSE UTVIKLING AS has its business address in Oslo.

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.