biztrac. BETA
COMPANY REGISTER PROFILE
917199809 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other building completion and finishing

SOLTYSBYGG AS

Org. no. 917199809 Limited company (AS) Bømlo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 8.4m
Operating profit NOK 1.8m
Equity NOK 1.9m
Incorporated 2016
Employees 8
Share capital NOK 30,000

SOLTYSBYGG AS is registered as a limited company in Bømlo, Vestland with organisation number 917199809. The business is classified under other building completion and finishing (NACE 43.350). The company was incorporated in 2016 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Byggetjenester, betongarbeid, taktekking, graving, oppussing inne og ute, snekkerarbeid, maling, import og salg av byggevarer.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.4m in revenue and NOK 1.8m in operating profit.

Key figures · 2025

Revenue
NOK 8.4m
▲ +20 %
Operating profit
NOK 1.8m
▲ +1229 %
Equity
NOK 1.9m
▲ +88 %
Est. value
NOK 3.9m

Financial health · 2025

Liquidity
2.07
Very good
Current assets ÷ current liabilities
Profitability
56.8%
Very good
Return on total assets
Solidity
51.7%
Very good
Equity as a share of total capital

Who owns SOLTYSBYGG AS?

SOLTYSBYGG AS
NOK 8.4m rev. · NOK 1.8m profit

SOLTYSBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOLTYSBYGG AS

Who owns SOLTYSBYGG AS?

Zbigniew Mariusz Soltys is the largest registered owner, with 100.0%.

What is the revenue of SOLTYSBYGG AS?

SOLTYSBYGG AS had revenue of NOK 8.4m in 2025.

Who is the general manager of SOLTYSBYGG AS?

Zbigniew Mariusz Soltys is registered as general manager of SOLTYSBYGG AS.

Where is SOLTYSBYGG AS based?

SOLTYSBYGG AS has its business address in Rubbestadneset.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.