BIZTRAC BETA
Photographic activities

LUMIERE STUDIO AS

Org. no. 932390035 Limited company (AS) Kvitsøy Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 233,000
Operating profit NOK −132,000
Equity NOK −119,000
Incorporated 2023
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−119k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−132k kr).
  • Nylig endring 2026-04-21 Adresseendring registrert 2026-04-21.

LUMIERE STUDIO AS is registered as a limited company in Kvitsøy, Rogaland with organisation number 932390035. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, salg av fotoutstyr. Fotografering. Produktfoto. Redigering. Sosial media.”. The most recent filed accounts, for the 2024 financial year, show NOK 233,000 in revenue and NOK −132,000 in operating profit.

Key figures · 2024

Revenue
NOK 233,000
Operating profit
NOK −132,000
Equity
NOK −119,000

Financial health · 2024

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

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

Who owns LUMIERE STUDIO AS?

BJØRSETH PETTERSEN AS
LUMIERE STUDIO AS
NOK 233,000 rev. · NOK −132,000 profit

LUMIERE STUDIO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LUMIERE STUDIO AS

Who owns LUMIERE STUDIO AS?

BJØRSETH PETTERSEN AS is the largest registered owner, with 60.0%.

What is the revenue of LUMIERE STUDIO AS?

LUMIERE STUDIO AS had revenue of NOK 233,000 in 2024.

Where is LUMIERE STUDIO AS based?

LUMIERE STUDIO AS has its business address in Kvitsø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.