BIZTRAC BETA
Site preparation

TORE HAGEN MASKIN AS

Org. no. 917269149 Limited company (AS) Øyer Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK −74,000
Equity NOK 1.4m
Incorporated 2016
Share capital NOK 30,000

Signals

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

TORE HAGEN MASKIN AS is registered as a limited company in Øyer, Innlandet with organisation number 917269149. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Maskinentreprenør og dermed beslektet virksomhet. Selskapet kan også ved aksjetegning eller på annen måte gjøre seg interessert i andre foretagender, samte eie, leie og kjøpe fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK −74,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK −74,000
Equity
NOK 1.4m
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns TORE HAGEN MASKIN AS?

TORE HAGEN
TORE HAGEN MASKIN AS
NOK 2.0m rev. · NOK −74,000 profit

TORE HAGEN MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TORE HAGEN MASKIN AS

Who owns TORE HAGEN MASKIN AS?

TORE HAGEN is the largest registered owner, with 100.0%.

What is the revenue of TORE HAGEN MASKIN AS?

TORE HAGEN MASKIN AS had revenue of NOK 2.0m in 2025.

Who is the general manager of TORE HAGEN MASKIN AS?

Tore Hagen is registered as general manager of TORE HAGEN MASKIN AS.

Where is TORE HAGEN MASKIN AS based?

TORE HAGEN MASKIN AS has its business address in Tretten.

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.