biztrac. BETA
COMPANY REGISTER PROFILE
998227143 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

KVALE HOLMEN AS

Org. no. 998227143 Limited company (AS) Øygarden Incorporated 2012 Active
Revenue 2025 NOK 776,000
Operating profit NOK 359,000
Equity NOK 852,000
Incorporated 2012
Share capital NOK 100,000

KVALE HOLMEN AS is registered as a limited company in Øygarden, Vestland with organisation number 998227143. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selskapets formål er investering i andre selskaper, samt kjøp, utvikling, utleie og salg av fast eiendom og alt hva herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 776,000 in revenue and NOK 359,000 in operating profit.

Key figures · 2025

Revenue
NOK 776,000
▲ +3 %
Operating profit
NOK 359,000
▲ +5 %
Equity
NOK 852,000
▲ +4 %
Est. value
NOK 938,000

Financial health · 2025

Liquidity
1.24
Satisfactory
Current assets ÷ current liabilities
Profitability
4.5%
Weak
Return on total assets
Solidity
10.7%
Satisfactory
Equity as a share of total capital

Who owns KVALE HOLMEN AS?

KVALE HOLMEN AS
NOK 776,000 rev. · NOK 359,000 profit

KVALE HOLMEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KVALE HOLMEN AS

Who owns KVALE HOLMEN AS?

Gard Kvale is the largest registered owner, with 50.0%.

What is the revenue of KVALE HOLMEN AS?

KVALE HOLMEN AS had revenue of NOK 776,000 in 2025.

Who is the general manager of KVALE HOLMEN AS?

Gard Kvale is registered as general manager of KVALE HOLMEN AS.

Where is KVALE HOLMEN AS based?

KVALE HOLMEN AS has its business address in Bjørøyhamn.

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

Report a problem

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