BIZTRAC BETA
Rental and operating of own or leased real estate

SVERRE VALVIK AS

Org. no. 988462942 Limited company (AS) Arendal Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 171,000
Operating profit NOK 93,000
Equity NOK 99.8m
Incorporated 2005
Share capital NOK 3.8m

SVERRE VALVIK AS is registered as a limited company in Arendal, Agder with organisation number 988462942. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 3.8m, divided into 152 shares. The company's stated purpose is: “Opptre som holdingselskap samt investere i aksjer og andeler samt alt hva som hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 171,000 in revenue and NOK 93,000 in operating profit.

Key figures · 2025

Revenue
NOK 171,000
Operating profit
NOK 93,000
Equity
NOK 99.8m
Est. value
NOK 68.6m

Financial health · 2025

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

Who owns SVERRE VALVIK AS?

SVERRE VALVIK
SVERRE VALVIK AS
NOK 171,000 rev. · NOK 93,000 profit

SVERRE VALVIK AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SVERRE VALVIK AS own?

SVERRE VALVIK AS holds stakes in 8 companies:

See the full ownership structure →

Frequently asked questions about SVERRE VALVIK AS

Who owns SVERRE VALVIK AS?

SVERRE VALVIK is the largest registered owner, with 93.4%.

What is the revenue of SVERRE VALVIK AS?

SVERRE VALVIK AS had revenue of NOK 171,000 in 2025.

Who is the general manager of SVERRE VALVIK AS?

Sverre Valvik is registered as general manager of SVERRE VALVIK AS.

Where is SVERRE VALVIK AS based?

SVERRE VALVIK AS has its business address in Færvik.

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.