BIZTRAC BETA
Wholesale of wood, construction materials and sanitary equipment

XL-BYGG OSTERØY AS

Org. no. 989081373 Limited company (AS) Osterøy Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 34.7m
Operating profit NOK 1.6m
Equity NOK 533,000
Incorporated 2005
Employees 14
Share capital NOK 100,000

XL-BYGG OSTERØY AS is registered as a limited company in Osterøy, Vestland with organisation number 989081373. The business is classified under wholesale of wood, construction materials and sanitary equipment (NACE 46.830). The company was incorporated in 2005 and has 14 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Handel innen byggevare og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 34.7m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 34.7m
Operating profit
NOK 1.6m
Equity
NOK 533,000
Est. value
NOK 6.5m

Financial health · 2024

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

Who owns XL-BYGG OSTERØY AS?

KNERTEN AS
XL-BYGG OSTERØY AS
NOK 34.7m rev. · NOK 1.6m profit

XL-BYGG OSTERØY AS has 1 registered shareholder:

All shareholders and roles →

Group structure

XL-BYGG OSTERØY AS er morselskap for 4 datterselskaper:

Frequently asked questions about XL-BYGG OSTERØY AS

Who owns XL-BYGG OSTERØY AS?

KNERTEN AS is the largest registered owner, with 100.0%.

What is the revenue of XL-BYGG OSTERØY AS?

XL-BYGG OSTERØY AS had revenue of NOK 34.7m in 2024.

Who is the general manager of XL-BYGG OSTERØY AS?

Rolf Henning Rød is registered as general manager of XL-BYGG OSTERØY AS.

Where is XL-BYGG OSTERØY AS based?

XL-BYGG OSTERØY AS has its business address in Valestrandsfossen.

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.