BIZTRAC BETA
Rental and operating of own or leased real estate

ØSTFOLD NÆRINGSPARK AS

Org. no. 981653726 Limited company (AS) Indre Østfold Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 26.1m
Operating profit NOK 10.9m
Equity NOK 59.5m
Incorporated 2000
Share capital NOK 10.0m

Signals

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

ØSTFOLD NÆRINGSPARK AS is registered as a limited company in Indre Østfold, Østfold with organisation number 981653726. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2000. Registered share capital is NOK 10.0m, divided into 10000 shares. The company's stated purpose is: “Drift, vedlikehold og utvikling av næringsparker, investering i drift og utvikling av fast eiendom samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 26.1m in revenue and NOK 10.9m in operating profit.

Key figures · 2024

Revenue
NOK 26.1m
Operating profit
NOK 10.9m
Equity
NOK 59.5m
Est. value
NOK 72.5m

Financial health · 2024

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

Who owns ØSTFOLD NÆRINGSPARK AS?

AFB EIENDOM AS
ØSTFOLD NÆRINGSPARK AS
NOK 26.1m rev. · NOK 10.9m profit

ØSTFOLD NÆRINGSPARK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØSTFOLD NÆRINGSPARK AS

Who owns ØSTFOLD NÆRINGSPARK AS?

AFB EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of ØSTFOLD NÆRINGSPARK AS?

ØSTFOLD NÆRINGSPARK AS had revenue of NOK 26.1m in 2024.

Where is ØSTFOLD NÆRINGSPARK AS based?

ØSTFOLD NÆRINGSPARK AS has its business address in Askim.

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.