BIZTRAC BETA
Uoppgitt

HARMONIKA AS

Org. no. 922413657 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 30,000
Operating profit NOK −25,000
Equity NOK 780.9m
Incorporated 2019
Share capital NOK 50,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−25k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HARMONIKA AS is registered as a limited company in Oslo, Oslo with organisation number 922413657. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 50,000, divided into 1000 shares. The company's stated purpose is: “Investeringsvirksomhet i aksjer, herunder å investere i selskaper som driver slik virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 30,000 in revenue and NOK −25,000 in operating profit.

Key figures · 2025

Revenue
NOK 30,000
Operating profit
NOK −25,000
Equity
NOK 780.9m
Est. value
NOK 413.8m

Financial health · 2025

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

Who owns HARMONIKA AS?

CHRISTIAN FREDRIK NAGELL-ERICHSEN
HARMONIKA AS
NOK 30,000 rev. · NOK −25,000 profit

HARMONIKA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HARMONIKA AS own?

HARMONIKA AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HARMONIKA AS

Who owns HARMONIKA AS?

CHRISTIAN FREDRIK NAGELL-ERICHSEN is the largest registered owner, with 100.0%.

What is the revenue of HARMONIKA AS?

HARMONIKA AS had revenue of NOK 30,000 in 2025.

Where is HARMONIKA AS based?

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