BIZTRAC BETA
Rental and operating of own or leased real estate

SKARVATUN FUTURE AS

Org. no. 998057272 Limited company (AS) Kvinnherad Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 336,000
Operating profit NOK 280,000
Equity NOK 768,000
Incorporated 2012
Share capital NOK 250,000

SKARVATUN FUTURE AS is registered as a limited company in Kvinnherad, Vestland with organisation number 998057272. 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 250,000, divided into 250 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom, import og salg av varer, samt være medeier i andre selskaper med tilsvarende eller nærliggende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 336,000 in revenue and NOK 280,000 in operating profit.

Key figures · 2025

Revenue
NOK 336,000
Operating profit
NOK 280,000
Equity
NOK 768,000
Est. value
NOK 956,000

Financial health · 2025

Liquidity
0.43
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.6%
Good
Equity as a share of total capital

Who owns SKARVATUN FUTURE AS?

JOHN SKARVATUN
SKARVATUN FUTURE AS
NOK 336,000 rev. · NOK 280,000 profit

SKARVATUN FUTURE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SKARVATUN FUTURE AS

Who owns SKARVATUN FUTURE AS?

JOHN SKARVATUN is the largest registered owner, with 40.0%.

What is the revenue of SKARVATUN FUTURE AS?

SKARVATUN FUTURE AS had revenue of NOK 336,000 in 2025.

Who is the general manager of SKARVATUN FUTURE AS?

Tony André Håvik Skarvatun is registered as general manager of SKARVATUN FUTURE AS.

Where is SKARVATUN FUTURE AS based?

SKARVATUN FUTURE AS has its business address in Ølve.

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.