BIZTRAC BETA
Rental and operating of own or leased real estate

STOREVEGEN 15 AS

Org. no. 995676842 Limited company (AS) Årdal Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 438,000
Operating profit NOK 230,000
Equity NOK −1.1m
Incorporated 2010
Share capital NOK 1.2m

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,1 mill kr).

STOREVEGEN 15 AS is registered as a limited company in Årdal, Vestland with organisation number 995676842. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 1.2m, divided into 1180 shares. The company's stated purpose is: “Drive utleige av eigedom og det som står i forbindelse med det.”. The most recent filed accounts, for the 2025 financial year, show NOK 438,000 in revenue and NOK 230,000 in operating profit.

Key figures · 2025

Revenue
NOK 438,000
Operating profit
NOK 230,000
Equity
NOK −1.1m
Est. value
NOK 1.8m

Financial health · 2025

Liquidity
0.98
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-57.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns STOREVEGEN 15 AS?

FRODE THUNE
STOREVEGEN 15 AS
NOK 438,000 rev. · NOK 230,000 profit

STOREVEGEN 15 AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about STOREVEGEN 15 AS

Who owns STOREVEGEN 15 AS?

FRODE THUNE is the largest registered owner, with 25.0%.

What is the revenue of STOREVEGEN 15 AS?

STOREVEGEN 15 AS had revenue of NOK 438,000 in 2025.

Who is the general manager of STOREVEGEN 15 AS?

Henrik Rønningen is registered as general manager of STOREVEGEN 15 AS.

Where is STOREVEGEN 15 AS based?

STOREVEGEN 15 AS has its business address in Øvre Årdal.

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.