BIZTRAC BETA
Uoppgitt

ANALYSYS MASON INVESTMENT 3 AS

Org. no. 933453111 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −32,000
Equity NOK −559,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

ANALYSYS MASON INVESTMENT 3 AS is registered as a limited company in Oslo, Oslo with organisation number 933453111. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringer i aksjer og andre eierandeler i andre selskaper og foretak samt all virksomhet som hermed står i forbindelse samt hva hermed står i forbindelse herunder å delta i andre selskaper med lignende virksomhet.”.

Key figures · 2025

Operating profit
NOK −32,000
Equity
NOK −559,000

Financial health · 2024

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

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

Who owns ANALYSYS MASON INVESTMENT 3 AS?

BLUENOTE AS
ANALYSYS MASON INVESTMENT 3 AS
· NOK −32,000 profit

ANALYSYS MASON INVESTMENT 3 AS has 11 registered shareholders:

All shareholders and roles →

Which companies does ANALYSYS MASON INVESTMENT 3 AS own?

ANALYSYS MASON INVESTMENT 3 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ANALYSYS MASON INVESTMENT 3 AS

Who owns ANALYSYS MASON INVESTMENT 3 AS?

BLUENOTE AS is the largest registered owner, with 8.7%.

Where is ANALYSYS MASON INVESTMENT 3 AS based?

ANALYSYS MASON INVESTMENT 3 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.