BIZTRAC BETA
Other captive investment companies

VENI VIDI VIIL AS

Org. no. 932910519 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −44,000
Equity NOK 2.0m
Incorporated 2024
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−44k kr).

VENI VIDI VIIL AS is registered as a limited company in Oslo, Oslo with organisation number 932910519. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2024. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Finansielle investeringer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −44,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −44,000
Equity
NOK 2.0m
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns VENI VIDI VIIL AS?

MARKUS OLA HOLTE GRANHEIM
VENI VIDI VIIL AS
NOK 0 rev. · NOK −44,000 profit

VENI VIDI VIIL AS has 3 registered shareholders:

All shareholders and roles →

Which companies does VENI VIDI VIIL AS own?

VENI VIDI VIIL AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about VENI VIDI VIIL AS

Who owns VENI VIDI VIIL AS?

MARKUS OLA HOLTE GRANHEIM is the largest registered owner, with 45.0%.

What is the revenue of VENI VIDI VIIL AS?

VENI VIDI VIIL AS had revenue of NOK 0 in 2025.

Who is the general manager of VENI VIDI VIIL AS?

Jenny Viil Holte Granheim is registered as general manager of VENI VIDI VIIL AS.

Where is VENI VIDI VIIL AS based?

VENI VIDI VIIL 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.