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

VALNØTT AS

Org. no. 991402381 Limited company (AS) Austevoll Incorporated 2007 Active
Ownership graph ↗
Operating profit NOK −95,000
Equity NOK 11.4m
Incorporated 2007
Share capital NOK 45,000

Signals

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

VALNØTT AS is registered as a limited company in Austevoll, Vestland with organisation number 991402381. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2007. Registered share capital is NOK 45,000, divided into 44959 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder delta som eiere, långivere og garantister i andre selskaper. Selskapet skal også kunne drive vanlig handelsvirksomhet.”.

Key figures · 2024

Operating profit
NOK −95,000
Equity
NOK 11.4m
Est. value
NOK 6.6m

Financial health · 2024

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

Who owns VALNØTT AS?

VALNØTT AS
· NOK −95,000 profit

VALNØTT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VALNØTT AS

Who owns VALNØTT AS?

FINN WAHL is the largest registered owner, with 100.0%.

Where is VALNØTT AS based?

VALNØTT AS has its business address in Kolbeinsvik.

Property

Business address Hestavikvegen 112, 5394 Kolbeinsvik
Cadastral unit 4625-57/54/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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.