BIZTRAC BETA
Development of building projects

AGDER BOLIG AS

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

Signals

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

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 2024 financial year, show NOK 156.8m in revenue and NOK 11.1m in operating profit.

Key figures · 2024

Revenue
NOK 156.8m
Operating profit
NOK 11.1m
Equity
NOK 17.2m
Est. value
NOK 32.9m

Financial health · 2024

Liquidity
1.68
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.7%
Satisfactory
Equity as a share of total capital

Who owns AGDER BOLIG AS?

AGDER BOLIG GRUPPEN AS
AGDER BOLIG AS
NOK 156.8m 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 156.8m in 2024.

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

Report a problem

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