BIZTRAC BETA
Construction of residential and non-residential buildings

BYGGMESTER AABEL AS

Org. no. 932396386 Limited company (AS) Birkenes Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 49,000
Equity NOK 17,000
Incorporated 2023
Share capital NOK 30,000

BYGGMESTER AABEL AS is registered as a limited company in Birkenes, Agder with organisation number 932396386. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Byggmestertjenester samt drift og vedlikehold av bygg og natur. I tillegg alt hva styret måtte finne formålstjenlig.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 49,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 49,000
Equity
NOK 17,000
Est. value
NOK 135,000

Financial health · 2024

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

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

Who owns BYGGMESTER AABEL AS?

KJETIL AABEL
BYGGMESTER AABEL AS
NOK 1.2m rev. · NOK 49,000 profit

BYGGMESTER AABEL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYGGMESTER AABEL AS

Who owns BYGGMESTER AABEL AS?

KJETIL AABEL is the largest registered owner, with 100.0%.

What is the revenue of BYGGMESTER AABEL AS?

BYGGMESTER AABEL AS had revenue of NOK 1.2m in 2024.

Who is the general manager of BYGGMESTER AABEL AS?

Kjetil Aabel is registered as general manager of BYGGMESTER AABEL AS.

Where is BYGGMESTER AABEL AS based?

BYGGMESTER AABEL AS has its business address in Birkeland.

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.