BIZTRAC BETA
COMPANY REGISTER PROFILE
917232229 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other captive investment companies

MAGHAN INVEST AS

Org. no. 917232229 Limited company (AS) Trondheim Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −12,000
Equity NOK 738,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

MAGHAN INVEST AS is registered as a limited company in Trondheim, Trøndelag with organisation number 917232229. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Selskapets formål er å drive virksomhet som omfatter: Finansiering, erverv og salg av verdipapirer og andre investeringer, kjøp og salg og utvikling og drift av fast eiendom og enhver annen virksomhet i sammenheng med det her nevnte. Virksomheten drives av selskapet selv eller gjennom dets datterselskaper i inn- og utland.”.

Key figures · 2025

Operating profit
NOK −12,000
Equity
NOK 738,000
Est. value
NOK 494,000

Financial health · 2025

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

Who owns MAGHAN INVEST AS?

OLAV JULIUS GAUPEN
MAGHAN INVEST AS
· NOK −12,000 profit

MAGHAN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MAGHAN INVEST AS

Who owns MAGHAN INVEST AS?

OLAV JULIUS GAUPEN is the largest registered owner, with 100.0%.

Who is the general manager of MAGHAN INVEST AS?

Olav Julius Gaupen is registered as general manager of MAGHAN INVEST AS.

Where is MAGHAN INVEST AS based?

MAGHAN INVEST AS has its business address in Trondheim.

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.