BIZTRAC BETA
Masonry and bricklaying activities

MURMESTER ERLING NILSSEN AS

Org. no. 978632807 Limited company (AS) Overhalla Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 12.0m
Operating profit NOK 1.0m
Equity NOK 3.5m
Incorporated 1997
Employees 9
Share capital NOK 90,000

MURMESTER ERLING NILSSEN AS is registered as a limited company in Overhalla, Trøndelag with organisation number 978632807. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 1997 and has 9 registered employees. Registered share capital is NOK 90,000, divided into 500 shares. The company's stated purpose is: “Mur, puss og flisarbeid. Samt betongarbeid. ”. The most recent filed accounts, for the 2024 financial year, show NOK 12.0m in revenue and NOK 1.0m in operating profit.

Key figures · 2024

Revenue
NOK 12.0m
Operating profit
NOK 1.0m
Equity
NOK 3.5m
Est. value
NOK 5.4m

Financial health · 2024

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

Who owns MURMESTER ERLING NILSSEN AS?

JAN EINAR NILSSEN
MURMESTER ERLING NILSSEN AS
NOK 12.0m rev. · NOK 1.0m profit

MURMESTER ERLING NILSSEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MURMESTER ERLING NILSSEN AS

Who owns MURMESTER ERLING NILSSEN AS?

JAN EINAR NILSSEN is the largest registered owner, with 66.7%.

What is the revenue of MURMESTER ERLING NILSSEN AS?

MURMESTER ERLING NILSSEN AS had revenue of NOK 12.0m in 2024.

Who is the general manager of MURMESTER ERLING NILSSEN AS?

Jan Einar Nilssen is registered as general manager of MURMESTER ERLING NILSSEN AS.

Where is MURMESTER ERLING NILSSEN AS based?

MURMESTER ERLING NILSSEN AS has its business address in Skage I Namdalen.

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.