biztrac. BETA
COMPANY REGISTER PROFILE
985231982 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

AGDER EIENDOM AS

Org. no. 985231982 Limited company (AS) Lillesand Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 18.0m
Operating profit NOK 4.4m
Equity NOK 10.8m
Incorporated 2002
Share capital NOK 140,000

AGDER EIENDOM AS is registered as a limited company in Lillesand, Agder with organisation number 985231982. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 140,000, divided into 396 shares. The company's stated purpose is: “Utvikle eiendommen Gaupemyr, Gnr 43., bnr 74. i Lillesand kommune.”. The most recent filed accounts, for the 2025 financial year, show NOK 18.0m in revenue and NOK 4.4m in operating profit.

Former names: SAND MØLLE DRIFT AS, AGDER MAT FOREDLING AS

Key figures · 2025

Revenue
NOK 18.0m
▲ +8 %
Operating profit
NOK 4.4m
▼ −21 %
Equity
NOK 10.8m
▲ +16 %
Est. value
NOK 14.3m

Financial health · 2025

Liquidity
0.94
Weak
Current assets ÷ current liabilities
Profitability
5.5%
Weak
Return on total assets
Solidity
12.8%
Satisfactory
Equity as a share of total capital

Who owns AGDER EIENDOM AS?

AGDER EIENDOM AS
NOK 18.0m rev. · NOK 4.4m profit

AGDER EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AGDER EIENDOM AS

Who owns AGDER EIENDOM AS?

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

What is the revenue of AGDER EIENDOM AS?

AGDER EIENDOM AS had revenue of NOK 18.0m in 2025.

Who is the general manager of AGDER EIENDOM AS?

Jens Øystein Eide is registered as general manager of AGDER EIENDOM AS.

Where is AGDER EIENDOM AS based?

AGDER EIENDOM AS has its business address in Lillesand.

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.