BIZTRAC BETA
Joinery installation

ULLENSAKER BYGGSERVICE AS

Org. no. 932791625 Limited company (AS) Nannestad Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK −290,000
Equity NOK −200,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−200k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−290k kr).

ULLENSAKER BYGGSERVICE AS is registered as a limited company in Nannestad, Akershus with organisation number 932791625. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Håndtverkertjenester. Andre produkter og tjenester som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK −290,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK −290,000
Equity
NOK −200,000

Financial health · 2024

Liquidity
0.33
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-59.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ULLENSAKER BYGGSERVICE AS?

OLEG DASCAL
ULLENSAKER BYGGSERVICE AS
NOK 2.1m rev. · NOK −290,000 profit

ULLENSAKER BYGGSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ULLENSAKER BYGGSERVICE AS

Who owns ULLENSAKER BYGGSERVICE AS?

OLEG DASCAL is the largest registered owner, with 50.0%.

What is the revenue of ULLENSAKER BYGGSERVICE AS?

ULLENSAKER BYGGSERVICE AS had revenue of NOK 2.1m in 2024.

Where is ULLENSAKER BYGGSERVICE AS based?

ULLENSAKER BYGGSERVICE AS has its business address in Nannestad.

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.