BIZTRAC BETA
Uoppgitt

VIDI VICI INVEST AS

Org. no. 924969067 Limited company (AS) Sarpsborg Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −36,000
Equity NOK 1.6m
Incorporated 2020
Share capital NOK 30,000

Signals

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

VIDI VICI INVEST AS is registered as a limited company in Sarpsborg, Østfold with organisation number 924969067. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i aksjer og andeler i andre selskaper, investering i fast eiendom og annen næringsvirksomhet og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −36,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −36,000
Equity
NOK 1.6m
Est. value
NOK 10.5m

Financial health · 2024

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

Who owns VIDI VICI INVEST AS?

MIKAEL KINGSRØD JOHANSEN
VIDI VICI INVEST AS
NOK 0 rev. · NOK −36,000 profit

VIDI VICI INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VIDI VICI INVEST AS own?

VIDI VICI INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VIDI VICI INVEST AS

Who owns VIDI VICI INVEST AS?

MIKAEL KINGSRØD JOHANSEN is the largest registered owner, with 100.0%.

What is the revenue of VIDI VICI INVEST AS?

VIDI VICI INVEST AS had revenue of NOK 0 in 2024.

Where is VIDI VICI INVEST AS based?

VIDI VICI INVEST AS has its business address in Hafslundsøy.

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.