BIZTRAC BETA
Construction of residential and non-residential buildings

BYGGMESTER APELAND AS

Org. no. 880681052 Limited company (AS) Kragerø Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 12.0m
Operating profit NOK 775,000
Equity NOK 2.8m
Incorporated 1999
Share capital NOK 100,000

BYGGMESTER APELAND AS is registered as a limited company in Kragerø, Telemark with organisation number 880681052. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Entreprenørtjenester i forbindelse med bygg og anleggsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.0m in revenue and NOK 775,000 in operating profit.

Key figures · 2025

Revenue
NOK 12.0m
Operating profit
NOK 775,000
Equity
NOK 2.8m
Est. value
NOK 4.1m

Financial health · 2025

Liquidity
2.06
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
57.5%
Very good
Equity as a share of total capital

Who owns BYGGMESTER APELAND AS?

ASTURI HOLDING AS
BYGGMESTER APELAND AS
NOK 12.0m rev. · NOK 775,000 profit

BYGGMESTER APELAND AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BYGGMESTER APELAND AS er morselskap for 2 datterselskaper:

Frequently asked questions about BYGGMESTER APELAND AS

Who owns BYGGMESTER APELAND AS?

ASTURI HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BYGGMESTER APELAND AS?

BYGGMESTER APELAND AS had revenue of NOK 12.0m in 2025.

Who is the general manager of BYGGMESTER APELAND AS?

Arve Apeland is registered as general manager of BYGGMESTER APELAND AS.

Where is BYGGMESTER APELAND AS based?

BYGGMESTER APELAND AS has its business address in Kragerø.

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.