BIZTRAC BETA
Repair and maintenance of machinery

FON MEKANISKE AS

Org. no. 993905291 Limited company (AS) Tønsberg Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 15.6m
Operating profit NOK 3.2m
Equity NOK 13.2m
Incorporated 2009
Employees 7
Share capital NOK 30,000

FON MEKANISKE AS is registered as a limited company in Tønsberg, Vestfold with organisation number 993905291. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2009 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Service og reparasjon av landbruksmaskiner. Maskiner som anskaffes skal kunne leies ut over en periode i forbindelse med reparasjoner av redskap/maskiner. Investering i fast eiendom bl.a utleie. Investeringer i aksjer, fond og lignende.”. The most recent filed accounts, for the 2025 financial year, show NOK 15.6m in revenue and NOK 3.2m in operating profit.

Key figures · 2025

Revenue
NOK 15.6m
Operating profit
NOK 3.2m
Equity
NOK 13.2m
Est. value
NOK 18.5m

Financial health · 2025

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

Who owns FON MEKANISKE AS?

HALVOR FON
FON MEKANISKE AS
NOK 15.6m rev. · NOK 3.2m profit

FON MEKANISKE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FON MEKANISKE AS

Who owns FON MEKANISKE AS?

HALVOR FON is the largest registered owner, with 50.0%.

What is the revenue of FON MEKANISKE AS?

FON MEKANISKE AS had revenue of NOK 15.6m in 2025.

Who is the general manager of FON MEKANISKE AS?

Halvor Fon is registered as general manager of FON MEKANISKE AS.

Where is FON MEKANISKE AS based?

FON MEKANISKE AS has its business address in Revetal.

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.