BIZTRAC BETA
Rental and operating of own or leased real estate

MAGNETUN EIGEDOM AS

Org. no. 913580435 Limited company (AS) Gol Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 383,000
Operating profit NOK 258,000
Equity NOK 703,000
Incorporated 2014
Share capital NOK 430,000

MAGNETUN EIGEDOM AS is registered as a limited company in Gol, Buskerud with organisation number 913580435. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 430,000, divided into 430 shares. The company's stated purpose is: “Kjøp, salg, utvikling, drift og utleie av fast eiendom. Kjøp, salg og utleie av anleggsmaskiner. Herunder å delta i andre selskap med tilsvarende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 383,000 in revenue and NOK 258,000 in operating profit.

Key figures · 2025

Revenue
NOK 383,000
Operating profit
NOK 258,000
Equity
NOK 703,000
Est. value
NOK 800,000

Financial health · 2025

Liquidity
0.10
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.1%
Satisfactory
Equity as a share of total capital

Who owns MAGNETUN EIGEDOM AS?

KAI INGE MAGNETUN
MAGNETUN EIGEDOM AS
NOK 383,000 rev. · NOK 258,000 profit

MAGNETUN EIGEDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MAGNETUN EIGEDOM AS

Who owns MAGNETUN EIGEDOM AS?

KAI INGE MAGNETUN is the largest registered owner, with 50.0%.

What is the revenue of MAGNETUN EIGEDOM AS?

MAGNETUN EIGEDOM AS had revenue of NOK 383,000 in 2025.

Who is the general manager of MAGNETUN EIGEDOM AS?

Olaf Magnetun is registered as general manager of MAGNETUN EIGEDOM AS.

Where is MAGNETUN EIGEDOM AS based?

MAGNETUN EIGEDOM AS has its business address in Gol.

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.