BIZTRAC BETA
Construction of residential and non-residential buildings

BYGGMESTER ESPELAND AS

Org. no. 924332395 Limited company (AS) Lyngdal Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 7.2m
Operating profit NOK 299,000
Equity NOK 181,000
Incorporated 2019
Employees 6
Share capital NOK 30,000

BYGGMESTER ESPELAND AS is registered as a limited company in Lyngdal, Agder with organisation number 924332395. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2019 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Bygge- og anleggsvirksomhet, og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.2m in revenue and NOK 299,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.2m
Operating profit
NOK 299,000
Equity
NOK 181,000
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns BYGGMESTER ESPELAND AS?

PETTER ESPELAND HOLDING AS
BYGGMESTER ESPELAND AS
NOK 7.2m rev. · NOK 299,000 profit

BYGGMESTER ESPELAND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYGGMESTER ESPELAND AS

Who owns BYGGMESTER ESPELAND AS?

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

What is the revenue of BYGGMESTER ESPELAND AS?

BYGGMESTER ESPELAND AS had revenue of NOK 7.2m in 2024.

Who is the general manager of BYGGMESTER ESPELAND AS?

Petter Vetås Espeland is registered as general manager of BYGGMESTER ESPELAND AS.

Where is BYGGMESTER ESPELAND AS based?

BYGGMESTER ESPELAND AS has its business address in Lyngdal.

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.