BIZTRAC BETA
Building of military ships and vessels

UMOE MANDAL EIENDOM AS

Org. no. 997515749 Limited company (AS) Lindesnes Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 9.4m
Operating profit NOK 4.3m
Equity NOK 2.2m
Incorporated 2011
Share capital NOK 500,000

UMOE MANDAL EIENDOM AS is registered as a limited company in Lindesnes, Agder with organisation number 997515749. The business is classified under building of military ships and vessels (NACE 30.130). The company was incorporated in 2011. Registered share capital is NOK 500,000, divided into 1000 shares. The company's stated purpose is: “Drive utvikling og utleie av fast eiendom, samt all annen virksomhet som er relatert til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.4m in revenue and NOK 4.3m in operating profit.

Key figures · 2024

Revenue
NOK 9.4m
Operating profit
NOK 4.3m
Equity
NOK 2.2m
Est. value
NOK 13.0m

Financial health · 2025

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

Who owns UMOE MANDAL EIENDOM AS?

UMOE MANDAL AS
UMOE MANDAL EIENDOM AS
NOK 9.4m rev. · NOK 4.3m profit

UMOE MANDAL EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

UMOE MANDAL EIENDOM AS er morselskap for 17 datterselskaper:

Frequently asked questions about UMOE MANDAL EIENDOM AS

Who owns UMOE MANDAL EIENDOM AS?

UMOE MANDAL AS is the largest registered owner, with 100.0%.

What is the revenue of UMOE MANDAL EIENDOM AS?

UMOE MANDAL EIENDOM AS had revenue of NOK 9.4m in 2024.

Who is the general manager of UMOE MANDAL EIENDOM AS?

Tom Fidjeland is registered as general manager of UMOE MANDAL EIENDOM AS.

Where is UMOE MANDAL EIENDOM AS based?

UMOE MANDAL EIENDOM AS has its business address in Mandal.

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.