BIZTRAC BETA
Wholesale of agricultural machinery, equipment and supplies

KROKKASSER.NO AS

Org. no. 931994719 Limited company (AS) Ringebu Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 185.4m
Operating profit NOK 14.8m
Equity NOK 82.6m
Incorporated 2023
Employees 30
Share capital NOK 1.0m

KROKKASSER.NO AS is registered as a limited company in Ringebu, Innlandet with organisation number 931994719. The business is classified under wholesale of agricultural machinery, equipment and supplies (NACE 46.610). The company was incorporated in 2023 and has 30 registered employees. Registered share capital is NOK 1.0m, divided into 30 shares. The company's stated purpose is: “Kjøp og salg av maskiner og utstyr, verksted, transport, import og tilliggende virksomhet samt eie aksjer i andre selskaper og virksomhet i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 185.4m in revenue and NOK 14.8m in operating profit.

Key figures · 2024

Revenue
NOK 185.4m
Operating profit
NOK 14.8m
Equity
NOK 82.6m
Est. value
NOK 95.0m

Financial health · 2024

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

Who owns KROKKASSER.NO AS?

KK DRIFT HOLDING AS
KROKKASSER.NO AS
NOK 185.4m rev. · NOK 14.8m profit

KROKKASSER.NO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KROKKASSER.NO AS

Who owns KROKKASSER.NO AS?

KK DRIFT HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of KROKKASSER.NO AS?

KROKKASSER.NO AS had revenue of NOK 185.4m in 2024.

Who is the general manager of KROKKASSER.NO AS?

Svein Skurdal is registered as general manager of KROKKASSER.NO AS.

Where is KROKKASSER.NO AS based?

KROKKASSER.NO AS has its business address in Ringebu.

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.