BIZTRAC BETA
Wholesale of watches and jewellery

LIBELULA STUDIO AS

Org. no. 921631170 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK −311,000
Equity NOK −282,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

LIBELULA STUDIO AS is registered as a limited company in Oslo, Oslo with organisation number 921631170. The business is classified under wholesale of watches and jewellery (NACE 46.480). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av smykker, klær og annen beslektet virksomhet, samt annen virksomhet som naturlig faller inn under denne beskrivelsen.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK −311,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK −311,000
Equity
NOK −282,000

Financial health · 2024

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

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

Who owns LIBELULA STUDIO AS?

CAMILLA AUSTAD KNUTSEN
LIBELULA STUDIO AS
NOK 2.1m rev. · NOK −311,000 profit

LIBELULA STUDIO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LIBELULA STUDIO AS

Who owns LIBELULA STUDIO AS?

CAMILLA AUSTAD KNUTSEN is the largest registered owner, with 100.0%.

What is the revenue of LIBELULA STUDIO AS?

LIBELULA STUDIO AS had revenue of NOK 2.1m in 2024.

Where is LIBELULA STUDIO AS based?

LIBELULA STUDIO 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.