BIZTRAC BETA
Construction of residential and non-residential buildings

DAROM BYGG AS

Org. no. 933098494 Limited company (AS) Lier Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 81,000
Operating profit NOK −9,000
Equity NOK −7,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−7k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).

DAROM BYGG AS is registered as a limited company in Lier, Buskerud with organisation number 933098494. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg av håndverktjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 81,000 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 81,000
Operating profit
NOK −9,000
Equity
NOK −7,000

Financial health · 2025

Liquidity
7.31
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-130.3%
Weak
Equity as a share of total capital

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

Who owns DAROM BYGG AS?

MARTINAS BIELSKIS
DAROM BYGG AS
NOK 81,000 rev. · NOK −9,000 profit

DAROM BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DAROM BYGG AS

Who owns DAROM BYGG AS?

MARTINAS BIELSKIS is the largest registered owner, with 100.0%.

What is the revenue of DAROM BYGG AS?

DAROM BYGG AS had revenue of NOK 81,000 in 2025.

Who is the general manager of DAROM BYGG AS?

Martinas Bielskis is registered as general manager of DAROM BYGG AS.

Where is DAROM BYGG AS based?

DAROM BYGG AS has its business address in Lierstranda.

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.