BIZTRAC BETA
Performing arts activities in music

FRODE MIKAELSEN AS

Org. no. 915019765 Limited company (AS) Bodø Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −69,000
Equity NOK 511,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

FRODE MIKAELSEN AS is registered as a limited company in Bodø, Nordland with organisation number 915019765. The business is classified under performing arts activities in music (NACE 90.201). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulenttjenester og undervisning i økonomiske/administrative fag med dertil tilhørende virksomhet, samt underholdingstjenester innen musikk og foredrag.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −69,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK −69,000
Equity
NOK 511,000
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns FRODE MIKAELSEN AS?

FRODE MIKAELSEN
FRODE MIKAELSEN AS
NOK 1.1m rev. · NOK −69,000 profit

FRODE MIKAELSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRODE MIKAELSEN AS

Who owns FRODE MIKAELSEN AS?

FRODE MIKAELSEN is the largest registered owner, with 100.0%.

What is the revenue of FRODE MIKAELSEN AS?

FRODE MIKAELSEN AS had revenue of NOK 1.1m in 2025.

Who is the general manager of FRODE MIKAELSEN AS?

Frode Mikaelsen is registered as general manager of FRODE MIKAELSEN AS.

Where is FRODE MIKAELSEN AS based?

FRODE MIKAELSEN AS has its business address in Bodø.

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.