BIZTRAC BETA
Development of building projects

VIVO EIENDOM AS

Org. no. 931804944 Limited company (AS) Hamar Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −51,000
Equity NOK 522,000
Incorporated 2023
Share capital NOK 500,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−51k kr).

VIVO EIENDOM AS is registered as a limited company in Hamar, Innlandet with organisation number 931804944. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2023. Registered share capital is NOK 500,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen byggeprosjekter, og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −51,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −51,000
Equity
NOK 522,000
Est. value
NOK 477,000

Financial health · 2024

Liquidity
-375.18
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.3%
Very good
Equity as a share of total capital

Who owns VIVO EIENDOM AS?

VIVO GROUP HOLDING AS
VIVO EIENDOM AS
NOK 0 rev. · NOK −51,000 profit

VIVO EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIVO EIENDOM AS

Who owns VIVO EIENDOM AS?

VIVO GROUP HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of VIVO EIENDOM AS?

VIVO EIENDOM AS had revenue of NOK 0 in 2024.

Who is the general manager of VIVO EIENDOM AS?

Susanne Øverland is registered as general manager of VIVO EIENDOM AS.

Where is VIVO EIENDOM AS based?

VIVO EIENDOM AS has its business address in Ridabu.

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.