BIZTRAC BETA
Construction of residential and non-residential buildings

BG SULDAL AS

Org. no. 937550987 Limited company (AS) Suldal Incorporated 1985 Active
Ownership graph ↗
Revenue 2025 NOK 54.6m
Operating profit NOK 9.0m
Equity NOK 13.1m
Incorporated 1985
Employees 24
Share capital NOK 4.0m

BG SULDAL AS is registered as a limited company in Suldal, Rogaland with organisation number 937550987. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1985 and has 24 registered employees. Registered share capital is NOK 4.0m, divided into 50 shares. The company's stated purpose is: “Drive med entreprenørvirksomhet og annen beslektet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 54.6m in revenue and NOK 9.0m in operating profit.

Key figures · 2025

Revenue
NOK 54.6m
Operating profit
NOK 9.0m
Equity
NOK 13.1m
Est. value
NOK 29.0m

Financial health · 2025

Liquidity
2.38
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.1%
Good
Equity as a share of total capital

Who owns BG SULDAL AS?

JAMO SULDAL AS
BG SULDAL AS
NOK 54.6m rev. · NOK 9.0m profit

BG SULDAL AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BG SULDAL AS own?

BG SULDAL AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

BG SULDAL AS er morselskap for 4 datterselskaper:

Frequently asked questions about BG SULDAL AS

Who owns BG SULDAL AS?

JAMO SULDAL AS is the largest registered owner, with 80.0%.

What is the revenue of BG SULDAL AS?

BG SULDAL AS had revenue of NOK 54.6m in 2025.

Who is the general manager of BG SULDAL AS?

Jan Moen is registered as general manager of BG SULDAL AS.

Where is BG SULDAL AS based?

BG SULDAL 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.