BIZTRAC BETA
Rental and operating of own or leased real estate

STRYN NÆRINGSPARK AS

Org. no. 922430861 Limited company (AS) Stryn Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK 2.7m
Equity NOK 4.5m
Incorporated 2019
Share capital NOK 30,000

Signals

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

STRYN NÆRINGSPARK AS is registered as a limited company in Stryn, Vestland with organisation number 922430861. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utbyging og utleie av eiendommer, samt prosjektering og utvikling av konstruksjoner av nye produkt, og ellers hva som måtte stå i forbindelse med dette, herunder å ta del i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 2.7m in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
Operating profit
NOK 2.7m
Equity
NOK 4.5m
Est. value
NOK 8.1m

Financial health · 2025

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

Who owns STRYN NÆRINGSPARK AS?

SVARSTAD BRUK AS
STRYN NÆRINGSPARK AS
NOK 3.3m rev. · NOK 2.7m profit

STRYN NÆRINGSPARK AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about STRYN NÆRINGSPARK AS

Who owns STRYN NÆRINGSPARK AS?

SVARSTAD BRUK AS is the largest registered owner, with 60.1%.

What is the revenue of STRYN NÆRINGSPARK AS?

STRYN NÆRINGSPARK AS had revenue of NOK 3.3m in 2025.

Where is STRYN NÆRINGSPARK AS based?

STRYN NÆRINGSPARK AS has its business address in Stryn.

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.