BIZTRAC BETA
Cutting, shaping and finishing of stone

MØRE MONUMENTSERVICE AS

Org. no. 987690607 Limited company (AS) Hustadvika Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 6.6m
Operating profit NOK 1.5m
Equity NOK 5.7m
Incorporated 2005
Share capital NOK 69,000

MØRE MONUMENTSERVICE AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 987690607. The business is classified under cutting, shaping and finishing of stone (NACE 23.700). The company was incorporated in 2005. Registered share capital is NOK 69,000, divided into 685 shares. The company's stated purpose is: “Skrifthugging og oppussing av gravminner samt det som er i forbindelse med dette, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.6m in revenue and NOK 1.5m in operating profit.

Key figures · 2025

Revenue
NOK 6.6m
Operating profit
NOK 1.5m
Equity
NOK 5.7m
Est. value
NOK 8.5m

Financial health · 2025

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

Who owns MØRE MONUMENTSERVICE AS?

ARVE GJENDEM
MØRE MONUMENTSERVICE AS
NOK 6.6m rev. · NOK 1.5m profit

MØRE MONUMENTSERVICE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about MØRE MONUMENTSERVICE AS

Who owns MØRE MONUMENTSERVICE AS?

ARVE GJENDEM is the largest registered owner, with 49.9%.

What is the revenue of MØRE MONUMENTSERVICE AS?

MØRE MONUMENTSERVICE AS had revenue of NOK 6.6m in 2025.

Who is the general manager of MØRE MONUMENTSERVICE AS?

Arve Gjendem is registered as general manager of MØRE MONUMENTSERVICE AS.

Where is MØRE MONUMENTSERVICE AS based?

MØRE MONUMENTSERVICE AS has its business address in Elnesvågen.

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.