BIZTRAC BETA
Wholesale of wood, construction materials and sanitary equipment

LAYHER AS

Org. no. 987768525 Limited company (AS) Ullensaker Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 60.6m
Operating profit NOK −10.3m
Equity NOK 14.4m
Incorporated 2004
Employees 10
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10,3 mill kr).

LAYHER AS is registered as a limited company in Ullensaker, Akershus with organisation number 987768525. The business is classified under wholesale of wood, construction materials and sanitary equipment (NACE 46.830). The company was incorporated in 2004 and has 10 registered employees. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Handel, agentur- og konsulentvirksomhet. Selskapet kan også ha økonomiske interesser i beslektede foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 60.6m in revenue and NOK −10.3m in operating profit.

Key figures · 2025

Revenue
NOK 60.6m
Operating profit
NOK −10.3m
Equity
NOK 14.4m
Est. value
NOK 26.5m

Financial health · 2025

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

Who owns LAYHER AS?

LAYHER INTERNATIONAL GMBH
LAYHER AS
NOK 60.6m rev. · NOK −10.3m profit

LAYHER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAYHER AS

Who owns LAYHER AS?

LAYHER INTERNATIONAL GMBH is the largest registered owner, with 100.0%.

What is the revenue of LAYHER AS?

LAYHER AS had revenue of NOK 60.6m in 2025.

Who is the general manager of LAYHER AS?

Harald Wahl Breivik is registered as general manager of LAYHER AS.

Where is LAYHER AS based?

LAYHER AS has its business address in Jessheim.

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.