BIZTRAC BETA
Central agencies for goods and transportation procurement

CABONLINE NORGE AS

Org. no. 978655521 Limited company (AS) Oslo Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 540.3m
Operating profit NOK 28.1m
Equity NOK 81.2m
Incorporated 1997
Employees 25
Share capital NOK 7.6m

CABONLINE NORGE AS is registered as a limited company in Oslo, Oslo with organisation number 978655521. The business is classified under central agencies for goods and transportation procurement (NACE 52.211). The company was incorporated in 1997 and has 25 registered employees. Registered share capital is NOK 7.6m, divided into 140120 shares. The company's stated purpose is: “Persontransport og hva som dermed står i forbindelse, herunder deltagelse i andre selskaper med samme formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 540.3m in revenue and NOK 28.1m in operating profit.

Key figures · 2024

Revenue
NOK 540.3m
Operating profit
NOK 28.1m
Equity
NOK 81.2m
Est. value
NOK 140.6m

Financial health · 2024

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

Who owns CABONLINE NORGE AS?

CABONLINE REGION STOCKHOLM AB
CABONLINE NORGE AS
NOK 540.3m rev. · NOK 28.1m profit

CABONLINE NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CABONLINE NORGE AS

Who owns CABONLINE NORGE AS?

CABONLINE REGION STOCKHOLM AB is the largest registered owner, with 100.0%.

What is the revenue of CABONLINE NORGE AS?

CABONLINE NORGE AS had revenue of NOK 540.3m in 2024.

Who is the general manager of CABONLINE NORGE AS?

Håkon Røkke Christiansen is registered as general manager of CABONLINE NORGE AS.

Where is CABONLINE NORGE AS based?

CABONLINE NORGE 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.