BIZTRAC BETA
Growing of cereals, other than rice, leguminous crops and oil seeds

HEST- OG FORSERVICE AS

Org. no. 951225673 Limited company (AS) Nes Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 6.3m
Operating profit NOK 1.2m
Equity NOK 2.8m
Incorporated 1988
Share capital NOK 300,000

HEST- OG FORSERVICE AS is registered as a limited company in Nes, Akershus with organisation number 951225673. The business is classified under growing of cereals, other than rice, leguminous crops and oil seeds (NACE 01.110). The company was incorporated in 1988. Registered share capital is NOK 300,000, divided into 150 shares. The company's stated purpose is: “Produksjon og omsetning av for til hest, samt leiekjøring og entreprenørvirksomhet. Samt hva styret finner interessant for selskapet.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.3m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 6.3m
Operating profit
NOK 1.2m
Equity
NOK 2.8m
Est. value
NOK 4.9m

Financial health · 2024

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

Who owns HEST- OG FORSERVICE AS?

AUDUN FONÅS WAHL
HEST- OG FORSERVICE AS
NOK 6.3m rev. · NOK 1.2m profit

HEST- OG FORSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HEST- OG FORSERVICE AS

Who owns HEST- OG FORSERVICE AS?

AUDUN FONÅS WAHL is the largest registered owner, with 100.0%.

What is the revenue of HEST- OG FORSERVICE AS?

HEST- OG FORSERVICE AS had revenue of NOK 6.3m in 2024.

Who is the general manager of HEST- OG FORSERVICE AS?

Audun Fonås Wahl is registered as general manager of HEST- OG FORSERVICE AS.

Where is HEST- OG FORSERVICE AS based?

HEST- OG FORSERVICE AS has its business address in Vormsund.

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.