BIZTRAC BETA
Rental and operating of own or leased real estate

STANGELAND NÆRINGSPARK 3 AS

Org. no. 913109155 Limited company (AS) Sola Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 11.8m
Operating profit NOK 8.1m
Equity NOK 49.4m
Incorporated 2013
Share capital NOK 5.5m

STANGELAND NÆRINGSPARK 3 AS is registered as a limited company in Sola, Rogaland with organisation number 913109155. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 5.5m, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av egen fast eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.8m in revenue and NOK 8.1m in operating profit.

Key figures · 2025

Revenue
NOK 11.8m
Operating profit
NOK 8.1m
Equity
NOK 49.4m
Est. value
NOK 47.9m

Financial health · 2025

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

Who owns STANGELAND NÆRINGSPARK 3 AS?

HEDLAND INVEST AS
STANGELAND NÆRINGSPARK 3 AS
NOK 11.8m rev. · NOK 8.1m profit

STANGELAND NÆRINGSPARK 3 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STANGELAND NÆRINGSPARK 3 AS

Who owns STANGELAND NÆRINGSPARK 3 AS?

HEDLAND INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of STANGELAND NÆRINGSPARK 3 AS?

STANGELAND NÆRINGSPARK 3 AS had revenue of NOK 11.8m in 2025.

Who is the general manager of STANGELAND NÆRINGSPARK 3 AS?

Jan Klingsheim is registered as general manager of STANGELAND NÆRINGSPARK 3 AS.

Where is STANGELAND NÆRINGSPARK 3 AS based?

STANGELAND NÆRINGSPARK 3 AS has its business address in Sola.

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.