BIZTRAC BETA
Construction of residential and non-residential buildings

SOLY SERVICE AS

Org. no. 930864668 Limited company (AS) Nome Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 39,000
Equity NOK 470,000
Incorporated 2023
Share capital NOK 300,000

SOLY SERVICE AS is registered as a limited company in Nome, Telemark with organisation number 930864668. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2023. Registered share capital is NOK 300,000, divided into 300000 shares. The company's stated purpose is: “Selge tjenester og varer innen håndverkertjenester - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 39,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK 39,000
Equity
NOK 470,000
Est. value
NOK 348,000

Financial health · 2024

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

Who owns SOLY SERVICE AS?

DARIUSZ MATEUSZ SOLTYS
SOLY SERVICE AS
NOK 1.7m rev. · NOK 39,000 profit

SOLY SERVICE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SOLY SERVICE AS

Who owns SOLY SERVICE AS?

DARIUSZ MATEUSZ SOLTYS is the largest registered owner, with 50.0%.

What is the revenue of SOLY SERVICE AS?

SOLY SERVICE AS had revenue of NOK 1.7m in 2025.

Who is the general manager of SOLY SERVICE AS?

Dariusz Mateusz Soltys is registered as general manager of SOLY SERVICE AS.

Where is SOLY SERVICE AS based?

SOLY SERVICE AS has its business address in Ulefoss.

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.