biztrac. BETA
COMPANY REGISTER PROFILE
920804861 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

MORTVOLD AS

Org. no. 920804861 Limited company (AS) Moss Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −14,000
Equity NOK 14.8m
Incorporated 2018
Share capital NOK 1.0m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−14k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MORTVOLD AS is registered as a limited company in Moss, Østfold with organisation number 920804861. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 1.0m, divided into 50000 shares. The company's stated purpose is: “Investering i aksjer, herunder deltakelse og utvikling av forretninger, kjøp, salg og drift av fast eiendom, kjøp og salg av motorkjøretøy samt det som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −14,000
▲ +26 %
Equity
NOK 14.8m
▲ +533 %
Est. value
NOK 113.3m

Financial health · 2025

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

Who owns MORTVOLD AS?

MORTVOLD AS
· NOK −14,000 profit

MORTVOLD AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MORTVOLD AS own?

MORTVOLD AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MORTVOLD AS

Who owns MORTVOLD AS?

Ove Morten Grønvold is the largest registered owner, with 100.0%.

Who is the general manager of MORTVOLD AS?

Ove Morten Grønvold is registered as general manager of MORTVOLD AS.

Where is MORTVOLD AS based?

MORTVOLD AS has its business address in Moss.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.