BIZTRAC BETA
Manufacture of other plastic products

CALORA MOORING SYSTEMS AS

Org. no. 917883734 Limited company (AS) Sandefjord Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −725,000
Equity NOK 2.7m
Incorporated 2016
Share capital NOK 936,000

Signals

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

CALORA MOORING SYSTEMS AS is registered as a limited company in Sandefjord, Vestfold with organisation number 917883734. The business is classified under manufacture of other plastic products (NACE 22.260). The company was incorporated in 2016. Registered share capital is NOK 936,000, divided into 33441 shares. The company's stated purpose is: “Eie eller drive industri- og annen tilknyttet virksomhet, forvaltning av kapital og andre funksjoner for konsernet, samt delta i eller overta annen virksomhet.”.

Key figures · 2025

Operating profit
NOK −725,000
Equity
NOK 2.7m
Est. value
NOK 3.1m

Financial health · 2025

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

Who owns CALORA MOORING SYSTEMS AS?

BAATHOLMEN AS
CALORA MOORING SYSTEMS AS
· NOK −725,000 profit

CALORA MOORING SYSTEMS AS has 8 registered shareholders:

All shareholders and roles →

Which companies does CALORA MOORING SYSTEMS AS own?

CALORA MOORING SYSTEMS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CALORA MOORING SYSTEMS AS

Who owns CALORA MOORING SYSTEMS AS?

BAATHOLMEN AS is the largest registered owner, with 74.8%.

Who is the general manager of CALORA MOORING SYSTEMS AS?

Allan Boye Hansen is registered as general manager of CALORA MOORING SYSTEMS AS.

Where is CALORA MOORING SYSTEMS AS based?

CALORA MOORING SYSTEMS AS has its business address in Sandefjord.

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.