BIZTRAC BETA
Cultural history museum activities

AUKRUST AS

Org. no. 922342415 Limited company (AS) Alvdal Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 6.8m
Operating profit NOK −120,000
Equity NOK 2.7m
Incorporated 2019
Employees 62
Share capital NOK 2.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−120k kr).

AUKRUST AS is registered as a limited company in Alvdal, Innlandet with organisation number 922342415. The business is classified under cultural history museum activities (NACE 91.212). The company was incorporated in 2019 and has 62 registered employees. Registered share capital is NOK 2.0m, divided into 2000 shares. The company's stated purpose is: “Fremme Kjell Aukrust som nasjonal kunstner og forfatter, hans tilhørighet til Alvdalsbygda og bygge Aukrust som merkevare.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.8m in revenue and NOK −120,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.8m
Operating profit
NOK −120,000
Equity
NOK 2.7m
Est. value
NOK 8.0m

Financial health · 2024

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

Who owns AUKRUST AS?

KARI OG KJELL AUKRUSTS STIFTELSE - AUKRUSTSTIFTELSEN
AUKRUST AS
NOK 6.8m rev. · NOK −120,000 profit

AUKRUST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AUKRUST AS

Who owns AUKRUST AS?

KARI OG KJELL AUKRUSTS STIFTELSE - AUKRUSTSTIFTELSEN is the largest registered owner, with 50.0%.

What is the revenue of AUKRUST AS?

AUKRUST AS had revenue of NOK 6.8m in 2024.

Who is the general manager of AUKRUST AS?

Hilde Bergebakken is registered as general manager of AUKRUST AS.

Where is AUKRUST AS based?

AUKRUST AS has its business address in Alvdal.

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.