BIZTRAC BETA
Wholesale of mining, construction and civil engineering machinery

FØNHUS MASKIN AS

Org. no. 935060826 Limited company (AS) Larvik Incorporated 1984 Active
Ownership graph ↗
Revenue 2024 NOK 13.2m
Operating profit NOK 4.4m
Equity NOK 3.6m
Incorporated 1984
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-03-25 Adresseendring registrert 2026-03-25.

FØNHUS MASKIN AS is registered as a limited company in Larvik, Vestfold with organisation number 935060826. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 1984. Registered share capital is NOK 100,000. The company's stated purpose is: “Agenturvirksomhet, kjøp og salg av maskiner og utstyr, særlig for treindustrien og virksomhet som har tilknyttning til denne.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.2m in revenue and NOK 4.4m in operating profit.

Key figures · 2024

Revenue
NOK 13.2m
Operating profit
NOK 4.4m
Equity
NOK 3.6m
Est. value
NOK 16.6m

Financial health · 2024

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

Who owns FØNHUS MASKIN AS?

ROLWAL HOLDING AS
FØNHUS MASKIN AS
NOK 13.2m rev. · NOK 4.4m profit

FØNHUS MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FØNHUS MASKIN AS

Who owns FØNHUS MASKIN AS?

ROLWAL HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of FØNHUS MASKIN AS?

FØNHUS MASKIN AS had revenue of NOK 13.2m in 2024.

Who is the general manager of FØNHUS MASKIN AS?

Rolf Andreas Wallin is registered as general manager of FØNHUS MASKIN AS.

Where is FØNHUS MASKIN AS based?

FØNHUS MASKIN AS has its business address in Larvik.

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.