BIZTRAC BETA
Site preparation

HOF MASKIN AS

Org. no. 924557648 Limited company (AS) Holmestrand Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 14.2m
Operating profit NOK 705,000
Equity NOK 4.5m
Incorporated 2020
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HOF MASKIN AS is registered as a limited company in Holmestrand, Vestfold with organisation number 924557648. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Entreprenørvirksomhet, grunnarbeid, leiekjøring, kjøp, salg og utleie av maskiner og løsøre og andre produkter/tjenester som naturlig hører sammen med dette. Herunder også å delta i andre selskap, kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.2m in revenue and NOK 705,000 in operating profit.

Key figures · 2024

Revenue
NOK 14.2m
Operating profit
NOK 705,000
Equity
NOK 4.5m
Est. value
NOK 4.8m

Financial health · 2024

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

Who owns HOF MASKIN AS?

SONO HOLDING AS
HOF MASKIN AS
NOK 14.2m rev. · NOK 705,000 profit

HOF MASKIN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HOF MASKIN AS

Who owns HOF MASKIN AS?

SONO HOLDING AS is the largest registered owner, with 80.0%.

What is the revenue of HOF MASKIN AS?

HOF MASKIN AS had revenue of NOK 14.2m in 2024.

Where is HOF MASKIN AS based?

HOF MASKIN AS has its business address in Hof.

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.