BIZTRAC BETA
Freight transport by road

ERIKSEN KRAN AS

Org. no. 948178931 Limited company (AS) Frogn Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 4.3m
Operating profit NOK −1.2m
Equity NOK 2.1m
Incorporated 1988
Share capital NOK 300,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,2 mill kr).

ERIKSEN KRAN AS is registered as a limited company in Frogn, Akershus with organisation number 948178931. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 1988. Registered share capital is NOK 300,000, divided into 300000 shares. The company's stated purpose is: “Å drive transport, import og varehandel samt deltakelse i andre selskaper med samme eller lignende formål. I tillegg investeringer i eiendom samt deltakelse i virksomhet med samme formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.3m in revenue and NOK −1.2m in operating profit.

Key figures · 2024

Revenue
NOK 4.3m
Operating profit
NOK −1.2m
Equity
NOK 2.1m
Est. value
NOK 2.2m

Financial health · 2024

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

Who owns ERIKSEN KRAN AS?

FINN ERIKSEN
ERIKSEN KRAN AS
NOK 4.3m rev. · NOK −1.2m profit

ERIKSEN KRAN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ERIKSEN KRAN AS

Who owns ERIKSEN KRAN AS?

FINN ERIKSEN is the largest registered owner, with 86.7%.

What is the revenue of ERIKSEN KRAN AS?

ERIKSEN KRAN AS had revenue of NOK 4.3m in 2024.

Who is the general manager of ERIKSEN KRAN AS?

Morten André Saasen Sagflaat is registered as general manager of ERIKSEN KRAN AS.

Where is ERIKSEN KRAN AS based?

ERIKSEN KRAN AS has its business address in Drøbak.

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.