BIZTRAC BETA
Other education activities

BIRKELUNDEN STUDIO AS

Org. no. 935575788 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 575,000
Operating profit NOK −7,000
Equity NOK 86,000
Incorporated 2025
Share capital NOK 100,000

Signals

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

BIRKELUNDEN STUDIO AS is registered as a limited company in Oslo, Oslo with organisation number 935575788. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2025. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Rådgivning, produksjon og kurs innen media og yoga.”. The most recent filed accounts, for the 2025 financial year, show NOK 575,000 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 575,000
Operating profit
NOK −7,000
Equity
NOK 86,000
Est. value
NOK 548,000

Financial health · 2025

Liquidity
1.40
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.5%
Weak
Equity as a share of total capital

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

Who owns BIRKELUNDEN STUDIO AS?

LISBETH JØRGENSEN
BIRKELUNDEN STUDIO AS
NOK 575,000 rev. · NOK −7,000 profit

BIRKELUNDEN STUDIO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BIRKELUNDEN STUDIO AS

Who owns BIRKELUNDEN STUDIO AS?

LISBETH JØRGENSEN is the largest registered owner, with 100.0%.

What is the revenue of BIRKELUNDEN STUDIO AS?

BIRKELUNDEN STUDIO AS had revenue of NOK 575,000 in 2025.

Who is the general manager of BIRKELUNDEN STUDIO AS?

Lisbeth Jørgensen is registered as general manager of BIRKELUNDEN STUDIO AS.

Where is BIRKELUNDEN STUDIO AS based?

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