BIZTRAC BETA
Rental and leasing of agricultural machinery and equipment

KOGSTAD AS

Org. no. 979202482 Limited company (AS) Lier Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK 471,000
Equity NOK 12.2m
Incorporated 1997
Share capital NOK 100,000

KOGSTAD AS is registered as a limited company in Lier, Buskerud with organisation number 979202482. The business is classified under rental and leasing of agricultural machinery and equipment (NACE 77.310). The company was incorporated in 1997. Registered share capital is NOK 100,000. The company's stated purpose is: “Utleie, kjøp og salg av maskiner og redskap. Investering i eiendom, aksjer og andre verdipapir samt andre virksomheter som står i forbindelse med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 471,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.5m
Operating profit
NOK 471,000
Equity
NOK 12.2m
Est. value
NOK 8.1m

Financial health · 2025

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

Who owns KOGSTAD AS?

MARTIN SØRUM
KOGSTAD AS
NOK 3.5m rev. · NOK 471,000 profit

KOGSTAD AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KOGSTAD AS own?

KOGSTAD AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KOGSTAD AS

Who owns KOGSTAD AS?

MARTIN SØRUM is the largest registered owner, with 100.0%.

What is the revenue of KOGSTAD AS?

KOGSTAD AS had revenue of NOK 3.5m in 2025.

Who is the general manager of KOGSTAD AS?

Martin Sørum is registered as general manager of KOGSTAD AS.

Where is KOGSTAD AS based?

KOGSTAD AS has its business address in Lier.

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.