BIZTRAC BETA
Passenger ocean transport

COLOR LINE CREW AS

Org. no. 991779434 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 1.1bn
Operating profit NOK 2.8m
Equity NOK 74.2m
Incorporated 2007
Employees 2296
Share capital NOK 3.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

COLOR LINE CREW AS is registered as a limited company in Oslo, Oslo with organisation number 991779434. The business is classified under passenger ocean transport (NACE 50.101). The company was incorporated in 2007 and has 2296 registered employees. Registered share capital is NOK 3.0m, divided into 3033000 shares. The company's stated purpose is: “Bemanne skipene i Color Line- konsernet, og annet som står i naturlig forbindelse til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1bn in revenue and NOK 2.8m in operating profit.

Key figures · 2024

Revenue
NOK 1.1bn
Operating profit
NOK 2.8m
Equity
NOK 74.2m
Est. value
NOK 47.5m

Financial health · 2024

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

Who owns COLOR LINE CREW AS?

COLOR LINE AS
COLOR LINE CREW AS
NOK 1.1bn rev. · NOK 2.8m profit

COLOR LINE CREW AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about COLOR LINE CREW AS

Who owns COLOR LINE CREW AS?

COLOR LINE AS is the largest registered owner, with 100.0%.

What is the revenue of COLOR LINE CREW AS?

COLOR LINE CREW AS had revenue of NOK 1.1bn in 2024.

Who is the general manager of COLOR LINE CREW AS?

Einar Ole Monstad is registered as general manager of COLOR LINE CREW AS.

Where is COLOR LINE CREW AS based?

COLOR LINE CREW 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.