BIZTRAC BETA
Repair and maintenance of machinery

JONE OGNEDAL AS

Org. no. 927887657 Limited company (AS) Bjerkreim Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 18.1m
Operating profit NOK 2.6m
Equity NOK 4.8m
Incorporated 2021
Employees 8
Share capital NOK 30,000

JONE OGNEDAL AS is registered as a limited company in Bjerkreim, Rogaland with organisation number 927887657. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2021 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Reparasjon av landbruksmaskiner, og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, 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 2025 financial year, show NOK 18.1m in revenue and NOK 2.6m in operating profit.

Key figures · 2025

Revenue
NOK 18.1m
Operating profit
NOK 2.6m
Equity
NOK 4.8m
Est. value
NOK 11.8m

Financial health · 2025

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

Who owns JONE OGNEDAL AS?

JONE OGNEDAL
JONE OGNEDAL AS
NOK 18.1m rev. · NOK 2.6m profit

JONE OGNEDAL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JONE OGNEDAL AS

Who owns JONE OGNEDAL AS?

JONE OGNEDAL is the largest registered owner, with 50.0%.

What is the revenue of JONE OGNEDAL AS?

JONE OGNEDAL AS had revenue of NOK 18.1m in 2025.

Who is the general manager of JONE OGNEDAL AS?

Jone Ognedal is registered as general manager of JONE OGNEDAL AS.

Where is JONE OGNEDAL AS based?

JONE OGNEDAL AS has its business address in Vikeså.

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.