biztrac. BETA
COMPANY REGISTER PROFILE
916620209 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

AGDER BOLIG AS

Org. no. 916620209 Limited company (AS) Lindesnes Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 175.7m
Operating profit NOK 11.1m
Equity NOK 22.0m
Incorporated 2016
Share capital NOK 2.2m

AGDER BOLIG AS is registered as a limited company in Lindesnes, Agder with organisation number 916620209. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2016. Registered share capital is NOK 2.2m, divided into 900 shares. The company's stated purpose is: “Eiendomsutvikling, kjøp, salg og utleie av eiendom, deltagelse i andre virksomheter samt alt hva som står i forbindelse med ovennevnte.”. The most recent filed accounts, for the 2025 financial year, show NOK 175.7m in revenue and NOK 11.1m in operating profit.

Former names: AGDER BOLIGUTVIKLING AS

Key figures · 2025

Revenue
NOK 175.7m
▲ +12 %
Operating profit
NOK 11.1m
▲ +0 %
Equity
NOK 22.0m
▲ +28 %
Est. value
NOK 35.0m

Financial health · 2025

Liquidity
1.83
Good
Current assets ÷ current liabilities
Profitability
8.6%
Satisfactory
Return on total assets
Solidity
15.1%
Satisfactory
Equity as a share of total capital

Who owns AGDER BOLIG AS?

AGDER BOLIG AS
NOK 175.7m rev. · NOK 11.1m profit

AGDER BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AGDER BOLIG AS

Who owns AGDER BOLIG AS?

AGDER BOLIG GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of AGDER BOLIG AS?

AGDER BOLIG AS had revenue of NOK 175.7m in 2025.

Who is the general manager of AGDER BOLIG AS?

Rune Johnsen is registered as general manager of AGDER BOLIG AS.

Where is AGDER BOLIG AS based?

AGDER BOLIG AS has its business address in Mandal.

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.