BIZTRAC BETA
Rental and operating of own or leased real estate

MAGO HOLDING AS

Org. no. 917619832 Limited company (AS) Stavanger Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 170,000
Operating profit NOK 113,000
Equity NOK 10.2m
Incorporated 2016
Share capital NOK 240,000

MAGO HOLDING AS is registered as a limited company in Stavanger, Rogaland with organisation number 917619832. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 240,000, divided into 400 shares. The company's stated purpose is: “Eie aksjer, investering i eiendom samt forvaltning av kapital og hva herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 170,000 in revenue and NOK 113,000 in operating profit.

Key figures · 2024

Revenue
NOK 170,000
Operating profit
NOK 113,000
Equity
NOK 10.2m
Est. value
NOK 7.7m

Financial health · 2024

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

Who owns MAGO HOLDING AS?

GAUTE OTTESEN
MAGO HOLDING AS
NOK 170,000 rev. · NOK 113,000 profit

MAGO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MAGO HOLDING AS own?

MAGO HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MAGO HOLDING AS

Who owns MAGO HOLDING AS?

GAUTE OTTESEN is the largest registered owner, with 100.0%.

What is the revenue of MAGO HOLDING AS?

MAGO HOLDING AS had revenue of NOK 170,000 in 2024.

Who is the general manager of MAGO HOLDING AS?

Gaute Ottesen is registered as general manager of MAGO HOLDING AS.

Where is MAGO HOLDING AS based?

MAGO HOLDING AS has its business address in Stavanger.

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.