biztrac. BETA
COMPANY REGISTER PROFILE
981653726 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
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 2025 NOK 26.4m
Operating profit NOK 13.1m
Equity NOK 56.1m
Incorporated 2000
Share capital NOK 10.0m

Ø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 2025 financial year, show NOK 26.4m in revenue and NOK 13.1m in operating profit.

Former names: G FLEX AS, GEFLEX AS

Key figures · 2025

Revenue
NOK 26.4m
▲ +1 %
Operating profit
NOK 13.1m
▲ +20 %
Equity
NOK 56.1m
▼ −6 %
Est. value
NOK 73.4m

Financial health · 2025

Liquidity
1.63
Good
Current assets ÷ current liabilities
Profitability
19.4%
Very good
Return on total assets
Solidity
77.4%
Very good
Equity as a share of total capital

Who owns ØSTFOLD NÆRINGSPARK AS?

ØSTFOLD NÆRINGSPARK AS
NOK 26.4m rev. · NOK 13.1m 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.4m in 2025.

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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.