BIZTRAC BETA
Construction of residential and non-residential buildings

MURMESTER REIDAR PETTERSEN AS

Org. no. 915205585 Limited company (AS) Drammen Incorporated 1972 Active
Ownership graph ↗
Revenue 2024 NOK 697,000
Operating profit NOK 61,000
Equity NOK 1.7m
Incorporated 1972
Share capital NOK 350,000

MURMESTER REIDAR PETTERSEN AS is registered as a limited company in Drammen, Buskerud with organisation number 915205585. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1972. Registered share capital is NOK 350,000. The company's stated purpose is: “Håndverksvirksomhet og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 697,000 in revenue and NOK 61,000 in operating profit.

Key figures · 2024

Revenue
NOK 697,000
Operating profit
NOK 61,000
Equity
NOK 1.7m
Est. value
NOK 963,000

Financial health · 2024

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

Who owns MURMESTER REIDAR PETTERSEN AS?

ODD PETTERSEN
MURMESTER REIDAR PETTERSEN AS
NOK 697,000 rev. · NOK 61,000 profit

MURMESTER REIDAR PETTERSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MURMESTER REIDAR PETTERSEN AS

Who owns MURMESTER REIDAR PETTERSEN AS?

ODD PETTERSEN is the largest registered owner, with 100.0%.

What is the revenue of MURMESTER REIDAR PETTERSEN AS?

MURMESTER REIDAR PETTERSEN AS had revenue of NOK 697,000 in 2024.

Who is the general manager of MURMESTER REIDAR PETTERSEN AS?

Odd Pettersen is registered as general manager of MURMESTER REIDAR PETTERSEN AS.

Where is MURMESTER REIDAR PETTERSEN AS based?

MURMESTER REIDAR PETTERSEN AS has its business address in Svelvik.

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.