BIZTRAC BETA
Freight transport by road

KROKAN TRANSPORT AS

Org. no. 991223991 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 109,000
Equity NOK 1.0m
Incorporated 2007
Share capital NOK 100,000

KROKAN TRANSPORT AS is registered as a limited company in Oslo, Oslo with organisation number 991223991. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Godstranport på vei, logistikkløsninger, montering av diverse installasjoner og investering i verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 109,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK 109,000
Equity
NOK 1.0m
Est. value
NOK 946,000

Financial health · 2025

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

Who owns KROKAN TRANSPORT AS?

ROGER KROKAN
KROKAN TRANSPORT AS
NOK 1.7m rev. · NOK 109,000 profit

KROKAN TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KROKAN TRANSPORT AS own?

KROKAN TRANSPORT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KROKAN TRANSPORT AS

Who owns KROKAN TRANSPORT AS?

ROGER KROKAN is the largest registered owner, with 100.0%.

What is the revenue of KROKAN TRANSPORT AS?

KROKAN TRANSPORT AS had revenue of NOK 1.7m in 2025.

Who is the general manager of KROKAN TRANSPORT AS?

Roger Krokan is registered as general manager of KROKAN TRANSPORT AS.

Where is KROKAN TRANSPORT AS based?

KROKAN TRANSPORT 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.