BIZTRAC BETA
Civil engineering activities

MARIUS BAKKEN HOLDING AS

Org. no. 928277720 Limited company (AS) Hamar Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −19,000
Equity NOK 4.9m
Incorporated 2021
Share capital NOK 40,000

Signals

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

MARIUS BAKKEN HOLDING AS is registered as a limited company in Hamar, Innlandet with organisation number 928277720. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2021. Registered share capital is NOK 40,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer, eiendom, verdipapirer og annen virksomhet med tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −19,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −19,000
Equity
NOK 4.9m
Est. value
NOK 29.6m

Financial health · 2025

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

Who owns MARIUS BAKKEN HOLDING AS?

MARIUS BAKKEN
MARIUS BAKKEN HOLDING AS
NOK 0 rev. · NOK −19,000 profit

MARIUS BAKKEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MARIUS BAKKEN HOLDING AS own?

MARIUS BAKKEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MARIUS BAKKEN HOLDING AS

Who owns MARIUS BAKKEN HOLDING AS?

MARIUS BAKKEN is the largest registered owner, with 100.0%.

What is the revenue of MARIUS BAKKEN HOLDING AS?

MARIUS BAKKEN HOLDING AS had revenue of NOK 0 in 2025.

Where is MARIUS BAKKEN HOLDING AS based?

MARIUS BAKKEN HOLDING AS has its business address in Hamar.

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.