BIZTRAC BETA
Development of building projects

ABOLIG AS

Org. no. 922867739 Limited company (AS) Nærøysund Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 11.3m
Operating profit NOK 1.7m
Equity NOK 3.5m
Incorporated 2019
Share capital NOK 1.7m

ABOLIG AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 922867739. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 1.7m, divided into 1680000 shares. The company's stated purpose is: “Kjøp, salg, utleie og utvikling av fast eiendom, oppføring av bygninger for boligformål og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.3m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 11.3m
Operating profit
NOK 1.7m
Equity
NOK 3.5m
Est. value
NOK 4.0m

Financial health · 2024

Liquidity
0.84
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.2%
Weak
Equity as a share of total capital

Who owns ABOLIG AS?

DIV INVEST AS
ABOLIG AS
NOK 11.3m rev. · NOK 1.7m profit

ABOLIG AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ABOLIG AS er morselskap for 3 datterselskaper:

Frequently asked questions about ABOLIG AS

Who owns ABOLIG AS?

DIV INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of ABOLIG AS?

ABOLIG AS had revenue of NOK 11.3m in 2024.

Who is the general manager of ABOLIG AS?

Chriss William Waagø is registered as general manager of ABOLIG AS.

Where is ABOLIG AS based?

ABOLIG AS has its business address in Ottersøy.

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.