BIZTRAC BETA
Warehousing and storage

KECO LOGISTICS AS

Org. no. 994554344 Limited company (AS) Våler Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 13.0m
Operating profit NOK 2.6m
Equity NOK 829,000
Incorporated 2009
Employees 9
Share capital NOK 100,000

KECO LOGISTICS AS is registered as a limited company in Våler, Østfold with organisation number 994554344. The business is classified under warehousing and storage (NACE 52.100). The company was incorporated in 2009 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Lagerhåndtering / leie / utleie / handel av enhver art og med dette beslektet virksomhet samt deltagelse i andre virksomheter ved aksjetegning eller på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.0m in revenue and NOK 2.6m in operating profit.

Key figures · 2024

Revenue
NOK 13.0m
Operating profit
NOK 2.6m
Equity
NOK 829,000
Est. value
NOK 7.7m

Financial health · 2024

Liquidity
1.09
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.3%
Satisfactory
Equity as a share of total capital

Who owns KECO LOGISTICS AS?

LOFOTPRODUKT OSLO PRODUKSJON AS
KECO LOGISTICS AS
NOK 13.0m rev. · NOK 2.6m profit

KECO LOGISTICS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KECO LOGISTICS AS

Who owns KECO LOGISTICS AS?

LOFOTPRODUKT OSLO PRODUKSJON AS is the largest registered owner, with 100.0%.

What is the revenue of KECO LOGISTICS AS?

KECO LOGISTICS AS had revenue of NOK 13.0m in 2024.

Who is the general manager of KECO LOGISTICS AS?

Aksel Ivar Sørlie is registered as general manager of KECO LOGISTICS AS.

Where is KECO LOGISTICS AS based?

KECO LOGISTICS AS has its business address in Våler I Østfold.

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.