biztrac. BETA
COMPANY REGISTER PROFILE
989678590 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
In liquidation UPDATED 03.10.2026
⚠HINNØY MASKIN AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Site preparation

HINNØY MASKIN AS

Org. no. 989678590 Limited company (AS) Harstad Incorporated 2006 In liquidation
Revenue 2025 NOK 6,000
Operating profit NOK −51,000
Equity NOK −405,000
Incorporated 2006
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−405k kr).

HINNØY MASKIN AS is registered as a limited company in Harstad, Troms with organisation number 989678590. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Maskinentrepenør, samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6,000 in revenue and NOK −51,000 in operating profit.

Key figures · 2025

Revenue
NOK 6,000
▼ −98 %
Operating profit
NOK −51,000
▲ +71 %
Equity
NOK −405,000
▼ −14 %

Financial health · 2025

Liquidity
0.31
Not satisfactory
Current assets ÷ current liabilities
Profitability
-24.4%
Not satisfactory
Return on total assets
Solidity
-219.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HINNØY MASKIN AS?

HINNØY MASKIN AS
NOK 6,000 rev. · NOK −51,000 profit

HINNØY MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HINNØY MASKIN AS

Who owns HINNØY MASKIN AS?

Gøte Aspen is the largest registered owner, with 100.0%.

What is the revenue of HINNØY MASKIN AS?

HINNØY MASKIN AS had revenue of NOK 6,000 in 2025.

Where is HINNØY MASKIN AS based?

HINNØY MASKIN AS has its business address in Harstad.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.