BIZTRAC BETA
Motion picture, video and television programme production activities

4 1/2 BLUE MOUNTAINS AS

Org. no. 928921050 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 7,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

4 1/2 BLUE MOUNTAINS AS is registered as a limited company in Oslo, Oslo with organisation number 928921050. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Produksjon av film og tv-serie, prosjektutvikling og all annen virksomhet som derunder naturlig hører hjemme.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 7,000
Est. value
NOK 13,000

Financial health · 2025

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

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

Who owns 4 1/2 BLUE MOUNTAINS AS?

4 1/2 ENTERTAINMENT AS
4 1/2 BLUE MOUNTAINS AS
NOK 0 rev. · NOK −5,000 profit

4 1/2 BLUE MOUNTAINS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about 4 1/2 BLUE MOUNTAINS AS

Who owns 4 1/2 BLUE MOUNTAINS AS?

4 1/2 ENTERTAINMENT AS is the largest registered owner, with 100.0%.

What is the revenue of 4 1/2 BLUE MOUNTAINS AS?

4 1/2 BLUE MOUNTAINS AS had revenue of NOK 0 in 2025.

Where is 4 1/2 BLUE MOUNTAINS AS based?

4 1/2 BLUE MOUNTAINS 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.