biztrac. BETA
COMPANY REGISTER PROFILE
919060468 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Performing arts activities in music

MARSIMONSEN AS

Org. no. 919060468 Limited company (AS) Oslo Incorporated 2017 Active
Revenue 2025 NOK 369,000
Operating profit NOK 99,000
Equity NOK 105,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-06-04 Adresseendring registrert 2026-06-04.

MARSIMONSEN AS is registered as a limited company in Oslo, Oslo with organisation number 919060468. The business is classified under performing arts activities in music (NACE 90.201). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Musikk; utøvende kunstnerisk virksomhet, produksjon, konsertarrangør, undervisning etc.”. The most recent filed accounts, for the 2025 financial year, show NOK 369,000 in revenue and NOK 99,000 in operating profit.

Key figures · 2025

Revenue
NOK 369,000
▲ +16 %
Operating profit
NOK 99,000
▲ +233 %
Equity
NOK 105,000
▲ +1766 %
Est. value
NOK 298,000

Financial health · 2025

Liquidity
2.78
Very good
Current assets ÷ current liabilities
Profitability
90.5%
Very good
Return on total assets
Solidity
64.0%
Very good
Equity as a share of total capital

Who owns MARSIMONSEN AS?

MARSIMONSEN AS
NOK 369,000 rev. · NOK 99,000 profit

MARSIMONSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MARSIMONSEN AS

Who owns MARSIMONSEN AS?

Marius Simonsen is the largest registered owner, with 100.0%.

What is the revenue of MARSIMONSEN AS?

MARSIMONSEN AS had revenue of NOK 369,000 in 2025.

Who is the general manager of MARSIMONSEN AS?

Marius Simonsen is registered as general manager of MARSIMONSEN AS.

Where is MARSIMONSEN AS based?

MARSIMONSEN 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.