BIZTRAC BETA
Construction of residential and non-residential buildings

STOLT BOLIG AS

Org. no. 895169102 Limited company (AS) Sandnes Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 39.5m
Operating profit NOK 1.1m
Equity NOK 8.7m
Incorporated 2010
Employees 37
Share capital NOK 500,000

STOLT BOLIG AS is registered as a limited company in Sandnes, Rogaland with organisation number 895169102. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2010 and has 37 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Entreprenørvirksomhet innen bygg og eiendom, samt alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 39.5m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 39.5m
Operating profit
NOK 1.1m
Equity
NOK 8.7m
Est. value
NOK 7.9m

Financial health · 2025

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

Who owns STOLT BOLIG AS?

STOLT PROSJEKT AS
STOLT BOLIG AS
NOK 39.5m rev. · NOK 1.1m profit

STOLT BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STOLT BOLIG AS own?

STOLT BOLIG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STOLT BOLIG AS

Who owns STOLT BOLIG AS?

STOLT PROSJEKT AS is the largest registered owner, with 100.0%.

What is the revenue of STOLT BOLIG AS?

STOLT BOLIG AS had revenue of NOK 39.5m in 2025.

Who is the general manager of STOLT BOLIG AS?

Ingvar Sikveland is registered as general manager of STOLT BOLIG AS.

Where is STOLT BOLIG AS based?

STOLT BOLIG AS has its business address in Sandnes.

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.