BIZTRAC BETA
Computer programming activities

MA-INVEST AS

Org. no. 988167088 Limited company (AS) Bamble Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −115,000
Equity NOK 150.2m
Incorporated 2005
Share capital NOK 125,000

Signals

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

MA-INVEST AS is registered as a limited company in Bamble, Telemark with organisation number 988167088. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2005. Registered share capital is NOK 125,000, divided into 125000 shares. The company's stated purpose is: “Eie aksjer i andre selskap, investere i aksjer, andeler og andre verdipapirer. Konsulentvirksomhet. Utvikling og salg av fast eiendom, utleie av fast eiendom samt virksomhet som naturlig faller innunder dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −115,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −115,000
Equity
NOK 150.2m
Est. value
NOK 136.3m

Financial health · 2024

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

Who owns MA-INVEST AS?

MORTEN ANDRESEN
MA-INVEST AS
NOK 0 rev. · NOK −115,000 profit

MA-INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MA-INVEST AS own?

MA-INVEST AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about MA-INVEST AS

Who owns MA-INVEST AS?

MORTEN ANDRESEN is the largest registered owner, with 82.0%.

What is the revenue of MA-INVEST AS?

MA-INVEST AS had revenue of NOK 0 in 2024.

Where is MA-INVEST AS based?

MA-INVEST AS has its business address in Stathelle.

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.