BIZTRAC BETA
Repair and maintenance of machinery

HAMAR MASKINSERVICE AS

Org. no. 990906491 Limited company (AS) Hamar Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 102,000
Operating profit NOK −38,000
Equity NOK 1.1m
Incorporated 2007
Share capital NOK 200,000

Signals

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

HAMAR MASKINSERVICE AS is registered as a limited company in Hamar, Innlandet with organisation number 990906491. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2007. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Butikkhandel og verksted for skog/hage/landbruksprodukter.”. The most recent filed accounts, for the 2025 financial year, show NOK 102,000 in revenue and NOK −38,000 in operating profit.

Key figures · 2025

Revenue
NOK 102,000
Operating profit
NOK −38,000
Equity
NOK 1.1m
Est. value
NOK 629,000

Financial health · 2025

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

Who owns HAMAR MASKINSERVICE AS?

JØRN TORE TVETER
HAMAR MASKINSERVICE AS
NOK 102,000 rev. · NOK −38,000 profit

HAMAR MASKINSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HAMAR MASKINSERVICE AS

Who owns HAMAR MASKINSERVICE AS?

JØRN TORE TVETER is the largest registered owner, with 75.0%.

What is the revenue of HAMAR MASKINSERVICE AS?

HAMAR MASKINSERVICE AS had revenue of NOK 102,000 in 2025.

Who is the general manager of HAMAR MASKINSERVICE AS?

Jørn Tore Tveter is registered as general manager of HAMAR MASKINSERVICE AS.

Where is HAMAR MASKINSERVICE AS based?

HAMAR MASKINSERVICE AS has its business address in Hamar.

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.