BIZTRAC BETA
Site preparation

KROON MASKIN AS

Org. no. 980169227 Limited company (AS) Nord-Aurdal Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 33.6m
Operating profit NOK 2.4m
Equity NOK 17.1m
Incorporated 1998
Employees 6
Share capital NOK 550,000

Signals

1 flags
  • Nylig endring 2026-07-02 Adresseendring registrert 2026-07-02.

KROON MASKIN AS is registered as a limited company in Nord-Aurdal, Innlandet with organisation number 980169227. The business is classified under site preparation (NACE 43.120). The company was incorporated in 1998 and has 6 registered employees. Registered share capital is NOK 550,000, divided into 550 shares. The company's stated purpose is: “Maskin og entreprenørvirksomhet innenfor bygg og anleggs- bransjen, herunder utleie av maskiner, deltakelse i andre selskaper samt alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 33.6m in revenue and NOK 2.4m in operating profit.

Key figures · 2025

Revenue
NOK 33.6m
Operating profit
NOK 2.4m
Equity
NOK 17.1m
Est. value
NOK 17.9m

Financial health · 2025

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

Who owns KROON MASKIN AS?

FRANS KROON HOLDING AS
KROON MASKIN AS
NOK 33.6m rev. · NOK 2.4m profit

KROON MASKIN AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about KROON MASKIN AS

Who owns KROON MASKIN AS?

FRANS KROON HOLDING AS is the largest registered owner, with 35.3%.

What is the revenue of KROON MASKIN AS?

KROON MASKIN AS had revenue of NOK 33.6m in 2025.

Who is the general manager of KROON MASKIN AS?

Lars Ole Myhre is registered as general manager of KROON MASKIN AS.

Where is KROON MASKIN AS based?

KROON MASKIN AS has its business address in Fagernes.

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.