BIZTRAC BETA
Freight coastal transport

KERKO PROCESS AS

Org. no. 921437935 Limited company (AS) Bergen Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 21.6m
Operating profit NOK 7.2m
Equity NOK 14.5m
Incorporated 2018
Employees 9
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KERKO PROCESS AS is registered as a limited company in Bergen, Vestland with organisation number 921437935. The business is classified under freight coastal transport (NACE 50.202). The company was incorporated in 2018 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 3 shares. The company's stated purpose is: “Transport av fisk samt annen transportvirksomhet og det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 21.6m in revenue and NOK 7.2m in operating profit.

Key figures · 2024

Revenue
NOK 21.6m
Operating profit
NOK 7.2m
Equity
NOK 14.5m
Est. value
NOK 28.6m

Financial health · 2024

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

Who owns KERKO PROCESS AS?

KERKO SHIPPING AS
KERKO PROCESS AS
NOK 21.6m rev. · NOK 7.2m profit

KERKO PROCESS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KERKO PROCESS AS

Who owns KERKO PROCESS AS?

KERKO SHIPPING AS is the largest registered owner, with 100.0%.

What is the revenue of KERKO PROCESS AS?

KERKO PROCESS AS had revenue of NOK 21.6m in 2024.

Who is the general manager of KERKO PROCESS AS?

Endre Haugland is registered as general manager of KERKO PROCESS AS.

Where is KERKO PROCESS AS based?

KERKO PROCESS AS has its business address in Bergen.

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.