BIZTRAC BETA
Rental and operating of own or leased real estate

STAKKEVOLLVEGEN EIENDOM AS

Org. no. 913079736 Limited company (AS) Tromsø Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 8.3m
Operating profit NOK 4.2m
Equity NOK 8.3m
Incorporated 2014
Share capital NOK 99,000

STAKKEVOLLVEGEN EIENDOM AS is registered as a limited company in Tromsø, Troms with organisation number 913079736. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 99,000, divided into 100 shares. The company's stated purpose is: “Eie fast eiendom eller aksjer i selskaper som eier fast eiendom, utvikle, omsette, leie ut og for øvrig administrere fast eiendom, samt hva som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.3m in revenue and NOK 4.2m in operating profit.

Key figures · 2025

Revenue
NOK 8.3m
Operating profit
NOK 4.2m
Equity
NOK 8.3m
Est. value
NOK 9.7m

Financial health · 2025

Liquidity
0.25
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.5%
Weak
Equity as a share of total capital

Who owns STAKKEVOLLVEGEN EIENDOM AS?

TOTAL PROSJEKT AS
STAKKEVOLLVEGEN EIENDOM AS
NOK 8.3m rev. · NOK 4.2m profit

STAKKEVOLLVEGEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

STAKKEVOLLVEGEN EIENDOM AS er morselskap for 249 datterselskaper:

Frequently asked questions about STAKKEVOLLVEGEN EIENDOM AS

Who owns STAKKEVOLLVEGEN EIENDOM AS?

TOTAL PROSJEKT AS is the largest registered owner, with 100.0%.

What is the revenue of STAKKEVOLLVEGEN EIENDOM AS?

STAKKEVOLLVEGEN EIENDOM AS had revenue of NOK 8.3m in 2025.

Where is STAKKEVOLLVEGEN EIENDOM AS based?

STAKKEVOLLVEGEN EIENDOM AS has its business address in Tromsø.

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.