BIZTRAC BETA
Construction of residential and non-residential buildings

DRAMMEN MESTERBYGG AS

Org. no. 989160737 Limited company (AS) Drammen Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 3.6m
Operating profit NOK −142,000
Equity NOK 499,000
Incorporated 2005
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−142k kr).

DRAMMEN MESTERBYGG AS is registered as a limited company in Drammen, Buskerud with organisation number 989160737. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2005. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Oppføring av bygninger og det som naturlig hører innunder.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.6m in revenue and NOK −142,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.6m
Operating profit
NOK −142,000
Equity
NOK 499,000
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns DRAMMEN MESTERBYGG AS?

PÅL SØRUM
DRAMMEN MESTERBYGG AS
NOK 3.6m rev. · NOK −142,000 profit

DRAMMEN MESTERBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DRAMMEN MESTERBYGG AS

Who owns DRAMMEN MESTERBYGG AS?

PÅL SØRUM is the largest registered owner, with 100.0%.

What is the revenue of DRAMMEN MESTERBYGG AS?

DRAMMEN MESTERBYGG AS had revenue of NOK 3.6m in 2025.

Who is the general manager of DRAMMEN MESTERBYGG AS?

Pål Sørum is registered as general manager of DRAMMEN MESTERBYGG AS.

Where is DRAMMEN MESTERBYGG AS based?

DRAMMEN MESTERBYGG AS has its business address in Drammen.

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.