BIZTRAC BETA
Growing of other non-perennial crops

INDRE ØSTFOLD EIENDOMSUTVIKLING AS

Org. no. 979356323 Limited company (AS) Indre Østfold Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 3.0m
Operating profit NOK 1.7m
Equity NOK 8.0m
Incorporated 1997
Share capital NOK 172,000

INDRE ØSTFOLD EIENDOMSUTVIKLING AS is registered as a limited company in Indre Østfold, Østfold with organisation number 979356323. The business is classified under growing of other non-perennial crops (NACE 01.190). The company was incorporated in 1997. Registered share capital is NOK 172,000, divided into 500 shares. The company's stated purpose is: “Ervervelse og utleie av eiendom samt investeringer i aksjer og deltakelse i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.0m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 3.0m
Operating profit
NOK 1.7m
Equity
NOK 8.0m
Est. value
NOK 9.2m

Financial health · 2024

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

Who owns INDRE ØSTFOLD EIENDOMSUTVIKLING AS?

DEGNES HOLDING AS
INDRE ØSTFOLD EIENDOMSUTVIKLING AS
NOK 3.0m rev. · NOK 1.7m profit

INDRE ØSTFOLD EIENDOMSUTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Group structure

INDRE ØSTFOLD EIENDOMSUTVIKLING AS er morselskap for 1 datterselskap:

Frequently asked questions about INDRE ØSTFOLD EIENDOMSUTVIKLING AS

Who owns INDRE ØSTFOLD EIENDOMSUTVIKLING AS?

DEGNES HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of INDRE ØSTFOLD EIENDOMSUTVIKLING AS?

INDRE ØSTFOLD EIENDOMSUTVIKLING AS had revenue of NOK 3.0m in 2024.

Where is INDRE ØSTFOLD EIENDOMSUTVIKLING AS based?

INDRE ØSTFOLD EIENDOMSUTVIKLING AS has its business address in Eidsberg.

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.