biztrac. BETA
COMPANY REGISTER PROFILE
935394937 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other support activities to arts and performing arts

LYNGSTAD & ØVSTEHAGE AS

Org. no. 935394937 Limited company (AS) Oslo Incorporated 2025 Active
Revenue 2025 NOK 15,000
Operating profit NOK −27,000
Equity NOK −3,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−3k kr).

LYNGSTAD & ØVSTEHAGE AS is registered as a limited company in Oslo, Oslo with organisation number 935394937. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Musikkstudio, DJ, låtskriving, booking, miks/master.”. The most recent filed accounts, for the 2025 financial year, show NOK 15,000 in revenue and NOK −27,000 in operating profit.

Key figures · 2025

Revenue
NOK 15,000
Operating profit
NOK −27,000
Equity
NOK −3,000

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
–
Not available
Equity as a share of total capital

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

Who owns LYNGSTAD & ØVSTEHAGE AS?

LYNGSTAD & ØVSTEHAGE AS
NOK 15,000 rev. · NOK −27,000 profit

LYNGSTAD & ØVSTEHAGE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LYNGSTAD & ØVSTEHAGE AS

Who owns LYNGSTAD & ØVSTEHAGE AS?

Alma Emelie Lyngstad is the largest registered owner, with 50.0%.

What is the revenue of LYNGSTAD & ØVSTEHAGE AS?

LYNGSTAD & ØVSTEHAGE AS had revenue of NOK 15,000 in 2025.

Where is LYNGSTAD & ØVSTEHAGE AS based?

LYNGSTAD & ØVSTEHAGE 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.