biztrac. BETA
COMPANY REGISTER PROFILE
980366537 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

MOUM HOLDING AS

Org. no. 980366537 Limited company (AS) Grimstad Incorporated 1998 Active
Ownership graph ↗
Operating profit NOK −46,000
Equity NOK 24.6m
Incorporated 1998
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−46k kr).
  • Nylig endring 2026-05-05 Adresseendring registrert 2026-05-05.

MOUM HOLDING AS is registered as a limited company in Grimstad, Agder with organisation number 980366537. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 1998. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Investering, eiendomsutvikling, administrasjon og konsulentvirksomhet og alt som hermed står i forbindelse, herunder delta i andre selskap med samme eller lignende formål.”.

Key figures · 2025

Operating profit
NOK −46,000
▲ +4 %
Equity
NOK 24.6m
▼ −10 %
Est. value
NOK 17.0m

Financial health · 2025

Liquidity
14.01
Very good
Current assets ÷ current liabilities
Profitability
4.6%
Weak
Return on total assets
Solidity
94.3%
Very good
Equity as a share of total capital

Who owns MOUM HOLDING AS?

MOUM HOLDING AS
· NOK −46,000 profit

MOUM HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MOUM HOLDING AS own?

MOUM HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about MOUM HOLDING AS

Who owns MOUM HOLDING AS?

Jørn Harald Moum is the largest registered owner, with 100.0%.

Who is the general manager of MOUM HOLDING AS?

Jørn Harald Moum is registered as general manager of MOUM HOLDING AS.

Where is MOUM HOLDING AS based?

MOUM HOLDING AS has its business address in Grimstad.

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.