BIZTRAC BETA
Rental and operating of own or leased real estate

STAKKEVOLLVN. 27 EIENDOM AS

Org. no. 887327572 Limited company (AS) Trondheim Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 6.3m
Operating profit NOK 201,000
Equity NOK 49.3m
Incorporated 2004
Share capital NOK 40.2m

STAKKEVOLLVN. 27 EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 887327572. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2004. Registered share capital is NOK 40.2m, divided into 16100 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter å eie og drive eiendom, samt ved å eie aksjer og/eller andeler delta i andre selskaper som driver liknende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.3m in revenue and NOK 201,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.3m
Operating profit
NOK 201,000
Equity
NOK 49.3m
Est. value
NOK 34.1m

Financial health · 2024

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

Who owns STAKKEVOLLVN. 27 EIENDOM AS?

NHP EIENDOM AS
STAKKEVOLLVN. 27 EIENDOM AS
NOK 6.3m rev. · NOK 201,000 profit

STAKKEVOLLVN. 27 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STAKKEVOLLVN. 27 EIENDOM AS

Who owns STAKKEVOLLVN. 27 EIENDOM AS?

NHP EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of STAKKEVOLLVN. 27 EIENDOM AS?

STAKKEVOLLVN. 27 EIENDOM AS had revenue of NOK 6.3m in 2024.

Where is STAKKEVOLLVN. 27 EIENDOM AS based?

STAKKEVOLLVN. 27 EIENDOM AS has its business address in Trondheim.

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.