BIZTRAC BETA
Rental and operating of own or leased real estate

OMDAL EIENDOM AS

Org. no. 988072036 Limited company (AS) Lund Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 662,000
Operating profit NOK 325,000
Equity NOK 7.3m
Incorporated 2005
Share capital NOK 882,000

OMDAL EIENDOM AS is registered as a limited company in Lund, Rogaland with organisation number 988072036. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 882,000, divided into 293858 shares. The company's stated purpose is: “Investering og utleie av fast eiendom, samt deltakelse og investeringer i andre virksomheter. ”. The most recent filed accounts, for the 2025 financial year, show NOK 662,000 in revenue and NOK 325,000 in operating profit.

Key figures · 2025

Revenue
NOK 662,000
Operating profit
NOK 325,000
Equity
NOK 7.3m
Est. value
NOK 6.0m

Financial health · 2025

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

Who owns OMDAL EIENDOM AS?

JOSTEIN OMDAL
OMDAL EIENDOM AS
NOK 662,000 rev. · NOK 325,000 profit

OMDAL EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does OMDAL EIENDOM AS own?

OMDAL EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about OMDAL EIENDOM AS

Who owns OMDAL EIENDOM AS?

JOSTEIN OMDAL is the largest registered owner, with 96.6%.

What is the revenue of OMDAL EIENDOM AS?

OMDAL EIENDOM AS had revenue of NOK 662,000 in 2025.

Who is the general manager of OMDAL EIENDOM AS?

Jostein Omdal is registered as general manager of OMDAL EIENDOM AS.

Where is OMDAL EIENDOM AS based?

OMDAL EIENDOM AS has its business address in Ualand.

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.