BIZTRAC BETA
Sound recording and music publishing activities

NOVA NORTH AS

Org. no. 919853913 Limited company (AS) Drammen Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −32,000
Equity NOK −234,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

NOVA NORTH AS is registered as a limited company in Drammen, Buskerud with organisation number 919853913. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Musikkproduksjon.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −32,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −32,000
Equity
NOK −234,000

Financial health · 2025

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

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

Who owns NOVA NORTH AS?

Johan Henrik Ericsson Christoffersen
NOVA NORTH AS
NOK 0 rev. · NOK −32,000 profit

NOVA NORTH AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NOVA NORTH AS

Who owns NOVA NORTH AS?

Johan Henrik Ericsson Christoffersen is the largest registered owner, with 50.0%.

What is the revenue of NOVA NORTH AS?

NOVA NORTH AS had revenue of NOK 0 in 2025.

Who is the general manager of NOVA NORTH AS?

Tobias Enberg Jensen is registered as general manager of NOVA NORTH AS.

Where is NOVA NORTH AS based?

NOVA NORTH AS has its business address in Solbergelva.

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.