BIZTRAC BETA
Repair and maintenance of machinery

TORE HAUGEN AS

Org. no. 971594896 Limited company (AS) Østre Toten Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 376,000
Operating profit NOK −57,000
Equity NOK 328,000
Incorporated 1994
Share capital NOK 200,000

Signals

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

TORE HAUGEN AS is registered as a limited company in Østre Toten, Innlandet with organisation number 971594896. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 1994. Registered share capital is NOK 200,000. The company's stated purpose is: “Rørbøying, rep. og vedlikehold maskiner og utstyr, og sveising av skilt, og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskaper med liknende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 376,000 in revenue and NOK −57,000 in operating profit.

Key figures · 2025

Revenue
NOK 376,000
Operating profit
NOK −57,000
Equity
NOK 328,000
Est. value
NOK 375,000

Financial health · 2025

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

Who owns TORE HAUGEN AS?

TORE HAUGEN
TORE HAUGEN AS
NOK 376,000 rev. · NOK −57,000 profit

TORE HAUGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TORE HAUGEN AS

Who owns TORE HAUGEN AS?

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

What is the revenue of TORE HAUGEN AS?

TORE HAUGEN AS had revenue of NOK 376,000 in 2025.

Who is the general manager of TORE HAUGEN AS?

Tore Haugen is registered as general manager of TORE HAUGEN AS.

Where is TORE HAUGEN AS based?

TORE HAUGEN AS has its business address in Lena.

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.