BIZTRAC BETA
Rental and operating of own or leased real estate

EIENDOMSUTVIKLING AGDER AS

Org. no. 994180363 Limited company (AS) Arendal Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 4.6m
Operating profit NOK 3.3m
Equity NOK 27.1m
Incorporated 2009
Share capital NOK 100,000

Signals

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

EIENDOMSUTVIKLING AGDER AS is registered as a limited company in Arendal, Agder with organisation number 994180363. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utvikling, kjøp og salg av fast eiendom, og hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.6m in revenue and NOK 3.3m in operating profit.

Key figures · 2024

Revenue
NOK 4.6m
Operating profit
NOK 3.3m
Equity
NOK 27.1m
Est. value
NOK 26.3m

Financial health · 2024

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

Who owns EIENDOMSUTVIKLING AGDER AS?

AEB EIENDOMINVEST AS
EIENDOMSUTVIKLING AGDER AS
NOK 4.6m rev. · NOK 3.3m profit

EIENDOMSUTVIKLING AGDER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EIENDOMSUTVIKLING AGDER AS

Who owns EIENDOMSUTVIKLING AGDER AS?

AEB EIENDOMINVEST AS is the largest registered owner, with 100.0%.

What is the revenue of EIENDOMSUTVIKLING AGDER AS?

EIENDOMSUTVIKLING AGDER AS had revenue of NOK 4.6m in 2024.

Where is EIENDOMSUTVIKLING AGDER AS based?

EIENDOMSUTVIKLING AGDER AS has its business address in Arendal.

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.