BIZTRAC BETA
Masonry and bricklaying activities

NORSK MURERSERVICE AS

Org. no. 923151230 Limited company (AS) Aurskog-Høland Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK 470,000
Equity NOK 483,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-05-07 Adresseendring registrert 2026-05-07.

NORSK MURERSERVICE AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 923151230. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Murertjenester til privatpersoner og bedrifter.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK 470,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK 470,000
Equity
NOK 483,000
Est. value
NOK 1.6m

Financial health · 2024

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

Who owns NORSK MURERSERVICE AS?

MARIANNE HOEM KOLDEN
NORSK MURERSERVICE AS
NOK 1.3m rev. · NOK 470,000 profit

NORSK MURERSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORSK MURERSERVICE AS

Who owns NORSK MURERSERVICE AS?

MARIANNE HOEM KOLDEN is the largest registered owner, with 100.0%.

What is the revenue of NORSK MURERSERVICE AS?

NORSK MURERSERVICE AS had revenue of NOK 1.3m in 2024.

Who is the general manager of NORSK MURERSERVICE AS?

Hans Roger Holm Kolden is registered as general manager of NORSK MURERSERVICE AS.

Where is NORSK MURERSERVICE AS based?

NORSK MURERSERVICE AS has its business address in Bjørkelangen.

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.