BIZTRAC BETA
Rental and operating of own or leased real estate

VITAE EIENDOM AS

Org. no. 925044016 Limited company (AS) Skien Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 656,000
Operating profit NOK 261,000
Equity NOK 1.3m
Incorporated 2020
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VITAE EIENDOM AS is registered as a limited company in Skien, Telemark with organisation number 925044016. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie, drift og utleie av fast eiendom, eie aksjer i andre selskap, investere i aksjer og andre verdipapirer, samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 656,000 in revenue and NOK 261,000 in operating profit.

Key figures · 2025

Revenue
NOK 656,000
Operating profit
NOK 261,000
Equity
NOK 1.3m
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
0.38
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.2%
Good
Equity as a share of total capital

Who owns VITAE EIENDOM AS?

PARAGON EIENDOM AS
VITAE EIENDOM AS
NOK 656,000 rev. · NOK 261,000 profit

VITAE EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VITAE EIENDOM AS

Who owns VITAE EIENDOM AS?

PARAGON EIENDOM AS is the largest registered owner, with 67.0%.

What is the revenue of VITAE EIENDOM AS?

VITAE EIENDOM AS had revenue of NOK 656,000 in 2025.

Where is VITAE EIENDOM AS based?

VITAE EIENDOM AS has its business address in Skien.

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.