BIZTRAC BETA
Rental and operating of own or leased real estate

KROON AS

Org. no. 927297809 Limited company (AS) Nord-Aurdal Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK 1.0m
Equity NOK 2.1m
Incorporated 2021
Share capital NOK 472,000

Signals

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

KROON AS is registered as a limited company in Nord-Aurdal, Innlandet with organisation number 927297809. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 472,000, divided into 472 shares. The company's stated purpose is: “Drive turistrettet virksomhet, herunder campingplass med kiosk og forøvrig alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 1.0m in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
Operating profit
NOK 1.0m
Equity
NOK 2.1m
Est. value
NOK 3.3m

Financial health · 2025

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

Who owns KROON AS?

ERIK KROON AS
KROON AS
NOK 2.5m rev. · NOK 1.0m profit

KROON AS has 3 registered shareholders:

All shareholders and roles →

Which companies does KROON AS own?

KROON AS holds a stake in 1 company:

See the full ownership structure →

Group structure

KROON AS er morselskap for 1 datterselskap:

Frequently asked questions about KROON AS

Who owns KROON AS?

ERIK KROON AS is the largest registered owner, with 33.5%.

What is the revenue of KROON AS?

KROON AS had revenue of NOK 2.5m in 2025.

Where is KROON AS based?

KROON 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.