BIZTRAC BETA
COMPANY REGISTER PROFILE
912976033 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

VALHEIM AS

Org. no. 912976033 Limited company (AS) Øksnes Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 307,000
Operating profit NOK −838,000
Equity NOK 45.0m
Incorporated 2013
Share capital NOK 561,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−838k kr).

VALHEIM AS is registered as a limited company in Øksnes, Nordland with organisation number 912976033. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2013. Registered share capital is NOK 561,000, divided into 11007 shares. The company's stated purpose is: “Rådgivning og deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 307,000 in revenue and NOK −838,000 in operating profit.

Key figures · 2025

Revenue
NOK 307,000
▲ +668 %
Operating profit
NOK −838,000
▼ −1035 %
Equity
NOK 45.0m
▲ +8 %
Est. value
NOK 31.5m

Financial health · 2025

Liquidity
84.05
Very good
Current assets ÷ current liabilities
Profitability
8.4%
Satisfactory
Return on total assets
Solidity
99.3%
Very good
Equity as a share of total capital

Who owns VALHEIM AS?

VALHEIM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does VALHEIM AS own?

VALHEIM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VALHEIM AS

Who owns VALHEIM AS?

JARLE RAGNAR MELØY is the largest registered owner, with 80.0%.

What is the revenue of VALHEIM AS?

VALHEIM AS had revenue of NOK 307,000 in 2025.

Who is the general manager of VALHEIM AS?

Monica Vottestad Meløy is registered as general manager of VALHEIM AS.

Where is VALHEIM AS based?

VALHEIM AS has its business address in Alsvåg.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.