BIZTRAC BETA
COMPANY REGISTER PROFILE
976182820 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

ØVLAND EIENDOM AS

Org. no. 976182820 Limited company (AS) Lillesand Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK 580,000
Equity NOK 5.5m
Incorporated 1996
Share capital NOK 3.5m

ØVLAND EIENDOM AS is registered as a limited company in Lillesand, Agder with organisation number 976182820. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1996. Registered share capital is NOK 3.5m, divided into 1760 shares. The company's stated purpose is: “Eie og forvalte fast eiendom, levere håndverktjenester, samt annet som står i forbindelse med dette. Selskapet kan videre investere i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 580,000 in operating profit.

Former names: ØVLAND KJØTT AS

Key figures · 2025

Revenue
NOK 2.5m
▼ −2 %
Operating profit
NOK 580,000
▲ +18 %
Equity
NOK 5.5m
▼ −1 %
Est. value
NOK 4.8m

Financial health · 2025

Liquidity
0.78
Weak
Current assets ÷ current liabilities
Profitability
4.1%
Weak
Return on total assets
Solidity
38.1%
Good
Equity as a share of total capital

Who owns ØVLAND EIENDOM AS?

ØVLAND EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ØVLAND EIENDOM AS

Who owns ØVLAND EIENDOM AS?

NILS ØVLAND is the largest registered owner, with 50.0%.

What is the revenue of ØVLAND EIENDOM AS?

ØVLAND EIENDOM AS had revenue of NOK 2.5m in 2025.

Who is the general manager of ØVLAND EIENDOM AS?

Johannes Øvland is registered as general manager of ØVLAND EIENDOM AS.

Where is ØVLAND EIENDOM AS based?

ØVLAND EIENDOM AS has its business address in Lillesand.

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

Report a problem

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