BIZTRAC BETA
Photographic activities

VIRVU AS

Org. no. 933781666 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 25,000
Operating profit NOK −29,000
Equity NOK −3,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−3k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−29k kr).

VIRVU AS is registered as a limited company in Oslo, Oslo with organisation number 933781666. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Virksomhet innen fotografering, skanning, filming av private og kommersielle eiendommer, samt alt annet som står i forbindelse med de forannevnte virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 25,000 in revenue and NOK −29,000 in operating profit.

Key figures · 2024

Revenue
NOK 25,000
Operating profit
NOK −29,000
Equity
NOK −3,000

Financial health · 2024

Liquidity
0.89
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-12.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VIRVU AS?

Henrik Malnes Stenslet
VIRVU AS
NOK 25,000 rev. · NOK −29,000 profit

VIRVU AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about VIRVU AS

Who owns VIRVU AS?

Henrik Malnes Stenslet is the largest registered owner, with 46.7%.

What is the revenue of VIRVU AS?

VIRVU AS had revenue of NOK 25,000 in 2024.

Who is the general manager of VIRVU AS?

Henrik Malnes Stenslet is registered as general manager of VIRVU AS.

Where is VIRVU AS based?

VIRVU 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.