BIZTRAC BETA
Masonry and bricklaying activities

MURMESTER OLE A. BROEN AS

Org. no. 947278681 Limited company (AS) Tønsberg Incorporated 1988 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 7,000
Equity NOK 794,000
Incorporated 1988
Share capital NOK 100,000

MURMESTER OLE A. BROEN AS is registered as a limited company in Tønsberg, Vestfold with organisation number 947278681. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 1988. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Håndverksvirksomhet, handel, import og hva dermed står i forbindelse, herunder også deltagelse i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 7,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 7,000
Equity
NOK 794,000
Est. value
NOK 372,000

Financial health · 2025

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

Who owns MURMESTER OLE A. BROEN AS?

OLE ANTON BROEN
MURMESTER OLE A. BROEN AS
NOK 1.1m rev. · NOK 7,000 profit

MURMESTER OLE A. BROEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MURMESTER OLE A. BROEN AS

Who owns MURMESTER OLE A. BROEN AS?

OLE ANTON BROEN is the largest registered owner, with 100.0%.

What is the revenue of MURMESTER OLE A. BROEN AS?

MURMESTER OLE A. BROEN AS had revenue of NOK 1.1m in 2025.

Who is the general manager of MURMESTER OLE A. BROEN AS?

Ole Anton Broen is registered as general manager of MURMESTER OLE A. BROEN AS.

Where is MURMESTER OLE A. BROEN AS based?

MURMESTER OLE A. BROEN AS has its business address in Tønsberg.

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.