BIZTRAC BETA
COMPANY REGISTER PROFILE
823833652 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

MAGIS AS

Org. no. 823833652 Limited company (AS) Bærum Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −13,000
Equity NOK 6.6m
Incorporated 2019
Share capital NOK 30,000

Signals

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

MAGIS AS is registered as a limited company in Bærum, Akershus with organisation number 823833652. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 101 shares. The company's stated purpose is: “Investering i verdipapirer og eiendom.”.

Key figures · 2025

Operating profit
NOK −13,000
▲ +4 %
Equity
NOK 6.6m
▲ +71 %
Est. value
NOK 21.4m

Financial health · 2025

Liquidity
100.67
Very good
Current assets ÷ current liabilities
Profitability
54.8%
Very good
Return on total assets
Solidity
99.2%
Very good
Equity as a share of total capital

Who owns MAGIS AS?

MAGIS AS
· NOK −13,000 profit

MAGIS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MAGIS AS own?

MAGIS AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MAGIS AS

Who owns MAGIS AS?

MORTEN BJØRN VENOLD is the largest registered owner, with 100.0%.

Where is MAGIS AS based?

MAGIS AS has its business address in Stabekk.

Property

Business address Kyrres vei 36, 1369 Stabekk
Cadastral unit 3201-14/290/0/0
Building Enebolig · 1 unit

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.