BIZTRAC BETA
Photographic activities

LAUVDAL FOTO AS

Org. no. 813422212 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 326,000
Operating profit NOK −147,000
Equity NOK −124,000
Incorporated 2014
Share capital NOK 30,000

Signals

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

LAUVDAL FOTO AS is registered as a limited company in Oslo, Oslo with organisation number 813422212. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Fotografering og tilsvarende virksomhet, samt set-design.”. The most recent filed accounts, for the 2024 financial year, show NOK 326,000 in revenue and NOK −147,000 in operating profit.

Key figures · 2024

Revenue
NOK 326,000
Operating profit
NOK −147,000
Equity
NOK −124,000

Financial health · 2024

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

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

Who owns LAUVDAL FOTO AS?

Siren Bakken Lauvdal
LAUVDAL FOTO AS
NOK 326,000 rev. · NOK −147,000 profit

LAUVDAL FOTO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAUVDAL FOTO AS

Who owns LAUVDAL FOTO AS?

Siren Bakken Lauvdal is the largest registered owner, with 100.0%.

What is the revenue of LAUVDAL FOTO AS?

LAUVDAL FOTO AS had revenue of NOK 326,000 in 2024.

Who is the general manager of LAUVDAL FOTO AS?

Siren Bakken Lauvdal is registered as general manager of LAUVDAL FOTO AS.

Where is LAUVDAL FOTO AS based?

LAUVDAL FOTO 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.