BIZTRAC BETA
Retail sale of motor vehicles

KJELL ORE AS

Org. no. 951346780 Limited company (AS) Farsund Incorporated 1989 Active
Ownership graph ↗
Revenue 2025 NOK 154.1m
Operating profit NOK 7.2m
Equity NOK 25.5m
Incorporated 1989
Employees 33
Share capital NOK 2.1m

Signals

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

KJELL ORE AS is registered as a limited company in Farsund, Agder with organisation number 951346780. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 1989 and has 33 registered employees. Registered share capital is NOK 2.1m, divided into 700 shares. The company's stated purpose is: “Handel, verksted, samt alt hva dermed står i forbindelse, herunder gjennom aksjetegning eller på annen måte å delta i andre selskaper eller foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 154.1m in revenue and NOK 7.2m in operating profit.

Key figures · 2025

Revenue
NOK 154.1m
Operating profit
NOK 7.2m
Equity
NOK 25.5m
Est. value
NOK 41.9m

Financial health · 2025

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

Who owns KJELL ORE AS?

KARLSBORG AS
KJELL ORE AS
NOK 154.1m rev. · NOK 7.2m profit

KJELL ORE AS has 4 registered shareholders:

All shareholders and roles →

Which companies does KJELL ORE AS own?

KJELL ORE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KJELL ORE AS

Who owns KJELL ORE AS?

KARLSBORG AS is the largest registered owner, with 92.9%.

What is the revenue of KJELL ORE AS?

KJELL ORE AS had revenue of NOK 154.1m in 2025.

Where is KJELL ORE AS based?

KJELL ORE AS has its business address in Vanse.

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.