BIZTRAC BETA
Freight transport by road

ERIK KIRKERØD TRANSPORT AS

Org. no. 912591085 Limited company (AS) Fredrikstad Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK −135,000
Equity NOK −17,000
Incorporated 2013
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−17k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−135k kr).

ERIK KIRKERØD TRANSPORT AS is registered as a limited company in Fredrikstad, Østfold with organisation number 912591085. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utøving av transporttjenester, samt tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK −135,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK −135,000
Equity
NOK −17,000

Financial health · 2025

Liquidity
1.25
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ERIK KIRKERØD TRANSPORT AS?

ERIK KIRKERØD
ERIK KIRKERØD TRANSPORT AS
NOK 1.9m rev. · NOK −135,000 profit

ERIK KIRKERØD TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ERIK KIRKERØD TRANSPORT AS

Who owns ERIK KIRKERØD TRANSPORT AS?

ERIK KIRKERØD is the largest registered owner, with 100.0%.

What is the revenue of ERIK KIRKERØD TRANSPORT AS?

ERIK KIRKERØD TRANSPORT AS had revenue of NOK 1.9m in 2025.

Where is ERIK KIRKERØD TRANSPORT AS based?

ERIK KIRKERØD TRANSPORT AS has its business address in Gressvik.

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.