biztrac. BETA
COMPANY REGISTER PROFILE
998056209 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

VITAR EIENDOM AS

Org. no. 998056209 Limited company (AS) Meløy Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 12.0m
Operating profit NOK 3.4m
Equity NOK 2.9m
Incorporated 2012
Share capital NOK 2.1m

VITAR EIENDOM AS is registered as a limited company in Meløy, Nordland with organisation number 998056209. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 2.1m, divided into 2080000 shares. The company's stated purpose is: “Drive med eiendom samt det som er i naturlig tilknytning til dette. I tillegg så kan selskapet investere i verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.0m in revenue and NOK 3.4m in operating profit.

Key figures · 2025

Revenue
NOK 12.0m
▲ +58 %
Operating profit
NOK 3.4m
▲ +42 %
Equity
NOK 2.9m
▲ +170 %
Est. value
NOK 8.0m

Financial health · 2025

Liquidity
0.69
Weak
Current assets ÷ current liabilities
Profitability
15.4%
Very good
Return on total assets
Solidity
13.2%
Satisfactory
Equity as a share of total capital

Who owns VITAR EIENDOM AS?

VITAR EIENDOM AS
NOK 12.0m rev. · NOK 3.4m profit

VITAR EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VITAR EIENDOM AS

Who owns VITAR EIENDOM AS?

Kent Ørjan Olsen is the largest registered owner, with 50.0%.

What is the revenue of VITAR EIENDOM AS?

VITAR EIENDOM AS had revenue of NOK 12.0m in 2025.

Who is the general manager of VITAR EIENDOM AS?

Geir Ludvik Olsen is registered as general manager of VITAR EIENDOM AS.

Where is VITAR EIENDOM AS based?

VITAR EIENDOM AS has its business address in Glomfjord.

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

Report a problem

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