BIZTRAC BETA
Rental and operating of own or leased real estate

STORØY NÆRINGSPARK AS

Org. no. 912493458 Limited company (AS) Karmøy Incorporated 1912 Active
Ownership graph ↗
Revenue 2024 NOK 2.6m
Operating profit NOK 1.2m
Equity NOK 10.4m
Incorporated 1912
Share capital NOK 2.2m

STORØY NÆRINGSPARK AS is registered as a limited company in Karmøy, Rogaland with organisation number 912493458. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1912. Registered share capital is NOK 2.2m. The company's stated purpose is: “Eie og utnytte fast eiendom, utvikle næringsområder, samt deltagelse i andre virksomheter av enhver art.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.6m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 2.6m
Operating profit
NOK 1.2m
Equity
NOK 10.4m
Est. value
NOK 10.4m

Financial health · 2024

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

Who owns STORØY NÆRINGSPARK AS?

STORØY HOLDING AS
STORØY NÆRINGSPARK AS
NOK 2.6m rev. · NOK 1.2m profit

STORØY NÆRINGSPARK AS has 16 registered shareholders:

All shareholders and roles →

Which companies does STORØY NÆRINGSPARK AS own?

STORØY NÆRINGSPARK AS holds a stake in 1 company:

See the full ownership structure →

Group structure

STORØY NÆRINGSPARK AS er morselskap for 1 datterselskap:

Frequently asked questions about STORØY NÆRINGSPARK AS

Who owns STORØY NÆRINGSPARK AS?

STORØY HOLDING AS is the largest registered owner, with 73.6%.

What is the revenue of STORØY NÆRINGSPARK AS?

STORØY NÆRINGSPARK AS had revenue of NOK 2.6m in 2024.

Where is STORØY NÆRINGSPARK AS based?

STORØY NÆRINGSPARK AS has its business address in Karmsund.

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.