BIZTRAC BETA
Masonry and bricklaying activities

MURMESTER HILLEREN AS

Org. no. 990395969 Limited company (AS) Bergen Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 10.0m
Operating profit NOK 619,000
Equity NOK 900,000
Incorporated 2006
Employees 5
Share capital NOK 100,000

MURMESTER HILLEREN AS is registered as a limited company in Bergen, Vestland with organisation number 990395969. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2006 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Murerarbeid og tilbehørende bygningsarbeid, samt kjøp og salg av eiendom, oppføring og rehabilitering av bygg, samt beslektet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.0m in revenue and NOK 619,000 in operating profit.

Key figures · 2025

Revenue
NOK 10.0m
Operating profit
NOK 619,000
Equity
NOK 900,000
Est. value
NOK 2.3m

Financial health · 2025

Liquidity
1.28
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.3%
Good
Equity as a share of total capital

Who owns MURMESTER HILLEREN AS?

THOMAS HILLEREN
MURMESTER HILLEREN AS
NOK 10.0m rev. · NOK 619,000 profit

MURMESTER HILLEREN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MURMESTER HILLEREN AS

Who owns MURMESTER HILLEREN AS?

THOMAS HILLEREN is the largest registered owner, with 100.0%.

What is the revenue of MURMESTER HILLEREN AS?

MURMESTER HILLEREN AS had revenue of NOK 10.0m in 2025.

Who is the general manager of MURMESTER HILLEREN AS?

Thomas Hilleren is registered as general manager of MURMESTER HILLEREN AS.

Where is MURMESTER HILLEREN AS based?

MURMESTER HILLEREN AS has its business address in Nesttun.

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.