BIZTRAC BETA
Site preparation

NYHAGEN MASKIN AS

Org. no. 915448747 Limited company (AS) Bodø Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 15,000
Operating profit NOK −11,000
Equity NOK 78,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−11k kr).

NYHAGEN MASKIN AS is registered as a limited company in Bodø, Nordland with organisation number 915448747. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Maskinentrepenørvirksomhet, utleie av maskin og fører, salg av fyllmasse og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 15,000 in revenue and NOK −11,000 in operating profit.

Key figures · 2024

Revenue
NOK 15,000
Operating profit
NOK −11,000
Equity
NOK 78,000
Est. value
NOK 80,000

Financial health · 2024

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

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

Who owns NYHAGEN MASKIN AS?

CHRISTOFFER NYHAGEN
NYHAGEN MASKIN AS
NOK 15,000 rev. · NOK −11,000 profit

NYHAGEN MASKIN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NYHAGEN MASKIN AS

Who owns NYHAGEN MASKIN AS?

CHRISTOFFER NYHAGEN is the largest registered owner, with 50.0%.

What is the revenue of NYHAGEN MASKIN AS?

NYHAGEN MASKIN AS had revenue of NOK 15,000 in 2024.

Who is the general manager of NYHAGEN MASKIN AS?

Øystein Nyhagen is registered as general manager of NYHAGEN MASKIN AS.

Where is NYHAGEN MASKIN AS based?

NYHAGEN MASKIN AS has its business address in Bodø.

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.