BIZTRAC BETA
Rental and operating of own or leased real estate

JUVA EIENDOM AS

Org. no. 948058529 Limited company (AS) Oslo Incorporated 1987 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 1.0m
Equity NOK 8.7m
Incorporated 1987
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-03-25 Aksjekapital registrert 2026-03-25.

JUVA EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 948058529. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1987. Registered share capital is NOK 30,000, divided into 38 shares. The company's stated purpose is: “Selskapets formål er å eie, utvikle og leie ut næringseiendom, samt hva hermed står i naturlig forbindelse, herunder deltakelse i andre selskaper med tilsvarende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 1.0m in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 1.0m
Equity
NOK 8.7m
Est. value
NOK 9.0m

Financial health · 2025

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

Who owns JUVA EIENDOM AS?

VANESSA CELINE OLSEN
JUVA EIENDOM AS
NOK 2.0m rev. · NOK 1.0m profit

JUVA EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about JUVA EIENDOM AS

Who owns JUVA EIENDOM AS?

VANESSA CELINE OLSEN is the largest registered owner, with 38.0%.

What is the revenue of JUVA EIENDOM AS?

JUVA EIENDOM AS had revenue of NOK 2.0m in 2025.

Who is the general manager of JUVA EIENDOM AS?

Galina Anatoljevna Olsen is registered as general manager of JUVA EIENDOM AS.

Where is JUVA EIENDOM AS based?

JUVA EIENDOM AS has its business address in Oslo.

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.