BIZTRAC BETA
Materials recovery

WILHELMSEN MARITIME SERVICES INVEST AS

Org. no. 930982075 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −137,000
Equity NOK 118.1m
Incorporated 2023
Share capital NOK 90,000

Signals

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

WILHELMSEN MARITIME SERVICES INVEST AS is registered as a limited company in Bærum, Akershus with organisation number 930982075. The business is classified under materials recovery (NACE 38.210). The company was incorporated in 2023. Registered share capital is NOK 90,000, divided into 300 shares. The company's stated purpose is: “Investering i maritim sektor og beslektede tjenester.”.

Key figures · 2024

Operating profit
NOK −137,000
Equity
NOK 118.1m
Est. value
NOK 73.1m

Financial health · 2024

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

Who owns WILHELMSEN MARITIME SERVICES INVEST AS?

WILHELMSEN MARITIME SERVICES AS
WILHELMSEN MARITIME SERVICES INVEST AS
· NOK −137,000 profit

WILHELMSEN MARITIME SERVICES INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does WILHELMSEN MARITIME SERVICES INVEST AS own?

WILHELMSEN MARITIME SERVICES INVEST AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about WILHELMSEN MARITIME SERVICES INVEST AS

Who owns WILHELMSEN MARITIME SERVICES INVEST AS?

WILHELMSEN MARITIME SERVICES AS is the largest registered owner, with 100.0%.

Where is WILHELMSEN MARITIME SERVICES INVEST AS based?

WILHELMSEN MARITIME SERVICES INVEST AS has its business address in Lysaker.

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.