BIZTRAC BETA
Other captive investment companies

MACE INVESTMENT AS

Org. no. 913400968 Limited company (AS) Larvik Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK 1.8m
Incorporated 2014
Share capital NOK 30,000

Signals

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

MACE INVESTMENT AS is registered as a limited company in Larvik, Vestfold with organisation number 913400968. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Delta i, investere i, og drive andre selskaper, kjøp, salg og drift av fast eiendom, samt virksomhet som står i naturlig sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK 1.8m
Est. value
NOK 4.2m

Financial health · 2024

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

Who owns MACE INVESTMENT AS?

TOMMY BJERKSETH
MACE INVESTMENT AS
NOK 0 rev. · NOK −14,000 profit

MACE INVESTMENT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MACE INVESTMENT AS own?

MACE INVESTMENT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MACE INVESTMENT AS

Who owns MACE INVESTMENT AS?

TOMMY BJERKSETH is the largest registered owner, with 100.0%.

What is the revenue of MACE INVESTMENT AS?

MACE INVESTMENT AS had revenue of NOK 0 in 2025.

Where is MACE INVESTMENT AS based?

MACE INVESTMENT AS has its business address in Larvik.

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.