BIZTRAC BETA
Construction of residential and non-residential buildings

AABAK BYGGTJENESTER AS

Org. no. 929349466 Limited company (AS) Vegårshei Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 106,000
Equity NOK 72,000
Incorporated 2022
Share capital NOK 30,000

AABAK BYGGTJENESTER AS is registered as a limited company in Vegårshei, Agder with organisation number 929349466. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utføre tjenester knyttet til byggebransjen, samt utleie av arbeidskraft.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 106,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 106,000
Equity
NOK 72,000
Est. value
NOK 392,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns AABAK BYGGTJENESTER AS?

GEIR ARNE AABAK
AABAK BYGGTJENESTER AS
NOK 1.3m rev. · NOK 106,000 profit

AABAK BYGGTJENESTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AABAK BYGGTJENESTER AS

Who owns AABAK BYGGTJENESTER AS?

GEIR ARNE AABAK is the largest registered owner, with 100.0%.

What is the revenue of AABAK BYGGTJENESTER AS?

AABAK BYGGTJENESTER AS had revenue of NOK 1.3m in 2025.

Who is the general manager of AABAK BYGGTJENESTER AS?

Geir Arne Aabak is registered as general manager of AABAK BYGGTJENESTER AS.

Where is AABAK BYGGTJENESTER AS based?

AABAK BYGGTJENESTER AS has its business address in Vegårshei.

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.