BIZTRAC BETA
Other technical consultancy

MARPRO HOLDING AS

Org. no. 995970007 Limited company (AS) Østre Toten Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −45,000
Equity NOK 1.4m
Incorporated 2010
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−45k kr).

MARPRO HOLDING AS is registered as a limited company in Østre Toten, Innlandet with organisation number 995970007. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2010. Registered share capital is NOK 30,000, divided into 50 shares. The company's stated purpose is: “Rådgiving og deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −45,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −45,000
Equity
NOK 1.4m
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns MARPRO HOLDING AS?

ERLING HOLE
MARPRO HOLDING AS
NOK 0 rev. · NOK −45,000 profit

MARPRO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MARPRO HOLDING AS own?

MARPRO HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MARPRO HOLDING AS

Who owns MARPRO HOLDING AS?

ERLING HOLE is the largest registered owner, with 100.0%.

What is the revenue of MARPRO HOLDING AS?

MARPRO HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of MARPRO HOLDING AS?

Erling Hole is registered as general manager of MARPRO HOLDING AS.

Where is MARPRO HOLDING AS based?

MARPRO HOLDING AS has its business address in Nordre Toten.

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.