BIZTRAC BETA
Rental and operating of own or leased real estate

KVITSØY PRESERVING AS

Org. no. 913679652 Limited company (AS) Kvitsøy Incorporated 1923 Active
Ownership graph ↗
Revenue 2025 NOK 228,000
Operating profit NOK 24,000
Equity NOK 431,000
Incorporated 1923
Share capital NOK 136,000

KVITSØY PRESERVING AS is registered as a limited company in Kvitsøy, Rogaland with organisation number 913679652. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1923. Registered share capital is NOK 136,000. The company's stated purpose is: “Kjøp og salg av skalldyr, herunder foredling.”. The most recent filed accounts, for the 2025 financial year, show NOK 228,000 in revenue and NOK 24,000 in operating profit.

Key figures · 2025

Revenue
NOK 228,000
Operating profit
NOK 24,000
Equity
NOK 431,000
Est. value
NOK 374,000

Financial health · 2025

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

Who owns KVITSØY PRESERVING AS?

ØYVIND HVIDING
KVITSØY PRESERVING AS
NOK 228,000 rev. · NOK 24,000 profit

KVITSØY PRESERVING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KVITSØY PRESERVING AS own?

KVITSØY PRESERVING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KVITSØY PRESERVING AS

Who owns KVITSØY PRESERVING AS?

ØYVIND HVIDING is the largest registered owner, with 100.0%.

What is the revenue of KVITSØY PRESERVING AS?

KVITSØY PRESERVING AS had revenue of NOK 228,000 in 2025.

Who is the general manager of KVITSØY PRESERVING AS?

Øyvind Hviding is registered as general manager of KVITSØY PRESERVING AS.

Where is KVITSØY PRESERVING AS based?

KVITSØY PRESERVING AS has its business address in Kvitsøy.

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.