biztrac. BETA
COMPANY REGISTER PROFILE
998811287 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

MAREHALM HOLDING AS

Org. no. 998811287 Limited company (AS) Grimstad Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −768,000
Equity NOK 30.8m
Incorporated 2012
Share capital NOK 452,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−768k kr).

MAREHALM HOLDING AS is registered as a limited company in Grimstad, Agder with organisation number 998811287. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2012. Registered share capital is NOK 452,000, divided into 452 shares. The company's stated purpose is: “Opptre som holdingselskap samt å investere i aksjer og andeler og alt som hermed står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −768,000
▼ −1807 %
Equity
NOK 30.8m
▼ −0 %
Est. value
NOK 31.6m

Financial health · 2025

Liquidity
27.31
Very good
Current assets ÷ current liabilities
Profitability
0.1%
Not satisfactory
Return on total assets
Solidity
99.5%
Very good
Equity as a share of total capital

Who owns MAREHALM HOLDING AS?

MAREHALM HOLDING AS
· NOK −768,000 profit

MAREHALM HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MAREHALM HOLDING AS own?

MAREHALM HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MAREHALM HOLDING AS

Who owns MAREHALM HOLDING AS?

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

Who is the general manager of MAREHALM HOLDING AS?

Jørn Tveite is registered as general manager of MAREHALM HOLDING AS.

Where is MAREHALM HOLDING AS based?

MAREHALM 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.