BIZTRAC BETA
Rental and operating of own or leased real estate

SIVA HERØYA AS

Org. no. 961599466 Limited company (AS) Trondheim Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 36.7m
Operating profit NOK −14.9m
Equity NOK 83.2m
Incorporated 1991
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−14,9 mill kr).

SIVA HERØYA AS is registered as a limited company in Trondheim, Trøndelag with organisation number 961599466. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1991. Registered share capital is NOK 1.0m, divided into 1000000 shares. The company's stated purpose is: “Investeringer i, herunder erverv, utvikling og forvaltning av fast eiendom. Selskapet kan med aksjeinnskudd eller på annen måte delta i virksomhet med tilsvarende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 36.7m in revenue and NOK −14.9m in operating profit.

Key figures · 2025

Revenue
NOK 36.7m
Operating profit
NOK −14.9m
Equity
NOK 83.2m
Est. value
NOK 88.0m

Financial health · 2025

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

Who owns SIVA HERØYA AS?

SIVA EIENDOM HOLDING AS
SIVA HERØYA AS
NOK 36.7m rev. · NOK −14.9m profit

SIVA HERØYA AS has 2 registered shareholders:

All shareholders and roles →

Group structure

SIVA HERØYA AS er morselskap for 32 datterselskaper:

Frequently asked questions about SIVA HERØYA AS

Who owns SIVA HERØYA AS?

SIVA EIENDOM HOLDING AS is the largest registered owner, with 88.0%.

What is the revenue of SIVA HERØYA AS?

SIVA HERØYA AS had revenue of NOK 36.7m in 2025.

Where is SIVA HERØYA AS based?

SIVA HERØYA 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.