BIZTRAC BETA
Intermediation service activities for freight transportation by ship

PARETO SHIPBROKERS AS

Org. no. 959266158 Limited company (AS) Kristiansand Incorporated 1990 Active
Ownership graph ↗
Revenue 2025 NOK 73.1m
Operating profit NOK 44.9m
Equity NOK 88.4m
Incorporated 1990
Employees 9
Share capital NOK 6.7m

PARETO SHIPBROKERS AS is registered as a limited company in Kristiansand, Agder with organisation number 959266158. The business is classified under intermediation service activities for freight transportation by ship (NACE 52.311). The company was incorporated in 1990 and has 9 registered employees. Registered share capital is NOK 6.7m, divided into 3500000 shares. The company's stated purpose is: “Skipsmegling og virksomhet som står i forbindelse hermed.”. The most recent filed accounts, for the 2025 financial year, show NOK 73.1m in revenue and NOK 44.9m in operating profit.

Key figures · 2025

Revenue
NOK 73.1m
Operating profit
NOK 44.9m
Equity
NOK 88.4m
Est. value
NOK 173.8m

Financial health · 2025

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

Who owns PARETO SHIPBROKERS AS?

PARETO AS
PARETO SHIPBROKERS AS
NOK 73.1m rev. · NOK 44.9m profit

PARETO SHIPBROKERS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PARETO SHIPBROKERS AS

Who owns PARETO SHIPBROKERS AS?

PARETO AS is the largest registered owner, with 100.0%.

What is the revenue of PARETO SHIPBROKERS AS?

PARETO SHIPBROKERS AS had revenue of NOK 73.1m in 2025.

Who is the general manager of PARETO SHIPBROKERS AS?

Karsten Christensen is registered as general manager of PARETO SHIPBROKERS AS.

Where is PARETO SHIPBROKERS AS based?

PARETO SHIPBROKERS AS has its business address in Kristiansand S.

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.