BIZTRAC BETA
Raising of horses and other equines

JÆREN HINGST AS

Org. no. 997705580 Limited company (AS) Klepp Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 13.8m
Operating profit NOK 1.3m
Equity NOK 6.1m
Incorporated 2011
Share capital NOK 100,000

JÆREN HINGST AS is registered as a limited company in Klepp, Rogaland with organisation number 997705580. The business is classified under raising of horses and other equines (NACE 01.430). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Avlsarbeid med hest, trening og oppstalling av hester for å fremme travsporten i distriktet og hva herved som står i forbindelse. I tillegg vil selskapet drive med valutahandel, kjøp og salg av aksjer, herunder investeringer i andre selskap og alt hva som inngår under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.8m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 13.8m
Operating profit
NOK 1.3m
Equity
NOK 6.1m
Est. value
NOK 7.4m

Financial health · 2024

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

Who owns JÆREN HINGST AS?

ODD DVERGSDAL
JÆREN HINGST AS
NOK 13.8m rev. · NOK 1.3m profit

JÆREN HINGST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JÆREN HINGST AS

Who owns JÆREN HINGST AS?

ODD DVERGSDAL is the largest registered owner, with 100.0%.

What is the revenue of JÆREN HINGST AS?

JÆREN HINGST AS had revenue of NOK 13.8m in 2024.

Who is the general manager of JÆREN HINGST AS?

Odd Dvergsdal is registered as general manager of JÆREN HINGST AS.

Where is JÆREN HINGST AS based?

JÆREN HINGST AS has its business address in Kleppe.

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.