BIZTRAC BETA
Business and other management consultancy activities

CUSTOS SHIPBUILDING AS

Org. no. 914456843 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −1,000
Equity NOK 5,000
Incorporated 2014
Share capital NOK 1.2m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1k kr).
  • Nylig endring 2026-04-17 Adresseendring registrert 2026-04-17.

CUSTOS SHIPBUILDING AS is registered as a limited company in Oslo, Oslo with organisation number 914456843. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2014. Registered share capital is NOK 1.2m, divided into 1250000 shares. The company's stated purpose is: “Å drive investeringer innen maritim- og forsvars-virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −1,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −1,000
Equity
NOK 5,000
Est. value
NOK 630,000

Financial health · 2024

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

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

Who owns CUSTOS SHIPBUILDING AS?

CUSTOS MARITIME & DEFENCE INDUS
CUSTOS SHIPBUILDING AS
NOK 0 rev. · NOK −1,000 profit

CUSTOS SHIPBUILDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CUSTOS SHIPBUILDING AS

Who owns CUSTOS SHIPBUILDING AS?

CUSTOS MARITIME & DEFENCE INDUS is the largest registered owner, with 100.0%.

What is the revenue of CUSTOS SHIPBUILDING AS?

CUSTOS SHIPBUILDING AS had revenue of NOK 0 in 2024.

Where is CUSTOS SHIPBUILDING AS based?

CUSTOS SHIPBUILDING 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.