BIZTRAC BETA
Performing arts activities in music

CLOSING EYES AS

Org. no. 929599322 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 14,000
Operating profit NOK −53,000
Equity NOK −217,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−217k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−53k kr).

CLOSING EYES AS is registered as a limited company in Oslo, Oslo with organisation number 929599322. The business is classified under performing arts activities in music (NACE 90.201). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Utøve og produsere musikk som innebærer konsertvirksomhet, turneer, musikk- og videoinnspillinger, promotering av bandet, samt trykk og salg av merchandise.”. The most recent filed accounts, for the 2025 financial year, show NOK 14,000 in revenue and NOK −53,000 in operating profit.

Key figures · 2025

Revenue
NOK 14,000
Operating profit
NOK −53,000
Equity
NOK −217,000

Financial health · 2025

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

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

Who owns CLOSING EYES AS?

EIRIK ASKER PETTERSEN
CLOSING EYES AS
NOK 14,000 rev. · NOK −53,000 profit

CLOSING EYES AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about CLOSING EYES AS

Who owns CLOSING EYES AS?

EIRIK ASKER PETTERSEN is the largest registered owner, with 25.0%.

What is the revenue of CLOSING EYES AS?

CLOSING EYES AS had revenue of NOK 14,000 in 2025.

Where is CLOSING EYES AS based?

CLOSING EYES 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.