BIZTRAC BETA
Rental and operating of own or leased real estate

STANGELAND NÆRINGSPARK 1 AS

Org. no. 913109287 Limited company (AS) Sola Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 27.4m
Operating profit NOK 20.0m
Equity NOK 76.6m
Incorporated 2013
Share capital NOK 294,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

STANGELAND NÆRINGSPARK 1 AS is registered as a limited company in Sola, Rogaland with organisation number 913109287. 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 294,000, divided into 100 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 27.4m in revenue and NOK 20.0m in operating profit.

Key figures · 2025

Revenue
NOK 27.4m
Operating profit
NOK 20.0m
Equity
NOK 76.6m
Est. value
NOK 88.7m

Financial health · 2025

Liquidity
0.12
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.9%
Good
Equity as a share of total capital

Who owns STANGELAND NÆRINGSPARK 1 AS?

HEDLAND INVEST AS
STANGELAND NÆRINGSPARK 1 AS
NOK 27.4m rev. · NOK 20.0m profit

STANGELAND NÆRINGSPARK 1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STANGELAND NÆRINGSPARK 1 AS

Who owns STANGELAND NÆRINGSPARK 1 AS?

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

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

STANGELAND NÆRINGSPARK 1 AS had revenue of NOK 27.4m in 2025.

Where is STANGELAND NÆRINGSPARK 1 AS based?

STANGELAND NÆRINGSPARK 1 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.