BIZTRAC BETA
Construction of residential and non-residential buildings

JORDALEN BYGG AS

Org. no. 915617859 Limited company (AS) Voss Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK −129,000
Equity NOK 66,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−129k kr).

JORDALEN BYGG AS is registered as a limited company in Voss, Vestland with organisation number 915617859. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive tømrervirksomhet samt hva herved hører til.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK −129,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK −129,000
Equity
NOK 66,000
Est. value
NOK 596,000

Financial health · 2025

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

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

Who owns JORDALEN BYGG AS?

EIRIK JORDALEN
JORDALEN BYGG AS
NOK 1.6m rev. · NOK −129,000 profit

JORDALEN BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JORDALEN BYGG AS

Who owns JORDALEN BYGG AS?

EIRIK JORDALEN is the largest registered owner, with 100.0%.

What is the revenue of JORDALEN BYGG AS?

JORDALEN BYGG AS had revenue of NOK 1.6m in 2025.

Who is the general manager of JORDALEN BYGG AS?

Eirik Jordalen is registered as general manager of JORDALEN BYGG AS.

Where is JORDALEN BYGG AS based?

JORDALEN BYGG AS has its business address in Voss.

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.