BIZTRAC BETA
Freight transport by road

KOO BETONGTRANSPORT AS

Org. no. 931996924 Limited company (AS) Haugesund Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 14.5m
Operating profit NOK 1.2m
Equity NOK 3.3m
Incorporated 2023
Employees 8
Share capital NOK 60,000

KOO BETONGTRANSPORT AS is registered as a limited company in Haugesund, Rogaland with organisation number 931996924. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2023 and has 8 registered employees. Registered share capital is NOK 60,000, divided into 100 shares. The company's stated purpose is: “Godstransport på vei samt investeringer i aksjer m.m. og deltakelse i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.5m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 14.5m
Operating profit
NOK 1.2m
Equity
NOK 3.3m
Est. value
NOK 5.7m

Financial health · 2024

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

Who owns KOO BETONGTRANSPORT AS?

KOO-HOLDING AS
KOO BETONGTRANSPORT AS
NOK 14.5m rev. · NOK 1.2m profit

KOO BETONGTRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Group structure

KOO BETONGTRANSPORT AS er morselskap for 1 datterselskap:

Frequently asked questions about KOO BETONGTRANSPORT AS

Who owns KOO BETONGTRANSPORT AS?

KOO-HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of KOO BETONGTRANSPORT AS?

KOO BETONGTRANSPORT AS had revenue of NOK 14.5m in 2024.

Who is the general manager of KOO BETONGTRANSPORT AS?

Kjell Ove Osnes is registered as general manager of KOO BETONGTRANSPORT AS.

Where is KOO BETONGTRANSPORT AS based?

KOO BETONGTRANSPORT AS has its business address in Haugesund.

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.