BIZTRAC BETA
Repair and maintenance of motor vehicles

ØYES KAROSSERI AS

Org. no. 911877082 Limited company (AS) Kristiansund Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 7.1m
Operating profit NOK −270,000
Equity NOK 1.8m
Incorporated 2013
Share capital NOK 830,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−270k kr).

ØYES KAROSSERI AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 911877082. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2013. Registered share capital is NOK 830,000, divided into 330000 shares. The company's stated purpose is: “Reparasjon og lakkering av biler og andre gjenstander, samt hva her med står i forbindelse, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.1m in revenue and NOK −270,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.1m
Operating profit
NOK −270,000
Equity
NOK 1.8m
Est. value
NOK 4.5m

Financial health · 2024

Liquidity
0.56
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.3%
Good
Equity as a share of total capital

Who owns ØYES KAROSSERI AS?

BRAVÆR HOLDING AS
ØYES KAROSSERI AS
NOK 7.1m rev. · NOK −270,000 profit

ØYES KAROSSERI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØYES KAROSSERI AS

Who owns ØYES KAROSSERI AS?

BRAVÆR HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ØYES KAROSSERI AS?

ØYES KAROSSERI AS had revenue of NOK 7.1m in 2024.

Who is the general manager of ØYES KAROSSERI AS?

Luca Mork Brandshaug is registered as general manager of ØYES KAROSSERI AS.

Where is ØYES KAROSSERI AS based?

ØYES KAROSSERI AS has its business address in Frei.

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.