BIZTRAC BETA
Other captive investment companies

HENRY SØRRA EIENDOM AS

Org. no. 921405561 Limited company (AS) Alstahaug Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −17,000
Equity NOK −125,000
Incorporated 2018
Share capital NOK 60,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−125k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−17k kr).

HENRY SØRRA EIENDOM AS is registered as a limited company in Alstahaug, Nordland with organisation number 921405561. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2018. Registered share capital is NOK 60,000, divided into 600 shares. The company's stated purpose is: “Investering og deltakelse i andre selskaper og eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −17,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −17,000
Equity
NOK −125,000

Financial health · 2025

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

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

Who owns HENRY SØRRA EIENDOM AS?

ÅSGATA 7 AS
HENRY SØRRA EIENDOM AS
NOK 0 rev. · NOK −17,000 profit

HENRY SØRRA EIENDOM AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about HENRY SØRRA EIENDOM AS

Who owns HENRY SØRRA EIENDOM AS?

ÅSGATA 7 AS is the largest registered owner, with 16.7%.

What is the revenue of HENRY SØRRA EIENDOM AS?

HENRY SØRRA EIENDOM AS had revenue of NOK 0 in 2025.

Where is HENRY SØRRA EIENDOM AS based?

HENRY SØRRA EIENDOM AS has its business address in Sandnessjøen.

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.