BIZTRAC BETA
Construction of residential and non-residential buildings

SULDAL BYGG AS

Org. no. 986193677 Limited company (AS) Suldal Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 23.8m
Operating profit NOK 170,000
Equity NOK 2.3m
Incorporated 2003
Employees 16
Share capital NOK 600,000

SULDAL BYGG AS is registered as a limited company in Suldal, Rogaland with organisation number 986193677. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2003 and has 16 registered employees. Registered share capital is NOK 600,000, divided into 600 shares. The company's stated purpose is: “Eiendomsutvikling og bygge- og anleggsverksemd.”. The most recent filed accounts, for the 2025 financial year, show NOK 23.8m in revenue and NOK 170,000 in operating profit.

Key figures · 2025

Revenue
NOK 23.8m
Operating profit
NOK 170,000
Equity
NOK 2.3m
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns SULDAL BYGG AS?

SIRDAL INVEST AS
SULDAL BYGG AS
NOK 23.8m rev. · NOK 170,000 profit

SULDAL BYGG AS has 4 registered shareholders:

All shareholders and roles →

Which companies does SULDAL BYGG AS own?

SULDAL BYGG AS holds stakes in 9 companies:

See the full ownership structure →

Frequently asked questions about SULDAL BYGG AS

Who owns SULDAL BYGG AS?

SIRDAL INVEST AS is the largest registered owner, with 48.8%.

What is the revenue of SULDAL BYGG AS?

SULDAL BYGG AS had revenue of NOK 23.8m in 2025.

Who is the general manager of SULDAL BYGG AS?

Lars Christian Benninghoff Øystad is registered as general manager of SULDAL BYGG AS.

Where is SULDAL BYGG AS based?

SULDAL BYGG AS has its business address in Sand.

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.