biztrac. BETA
COMPANY REGISTER PROFILE
935460743 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of motor vehicles

KVEEN MOTOR AS

Org. no. 935460743 Limited company (AS) Stryn Incorporated 2025 Active
Revenue 2025 NOK 54.1m
Operating profit NOK 2.0m
Equity NOK 14.4m
Incorporated 2025
Employees 13
Share capital NOK 782,000

KVEEN MOTOR AS is registered as a limited company in Stryn, Vestland with organisation number 935460743. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2025 and has 13 registered employees. Registered share capital is NOK 782,000, divided into 781597 shares. The company's stated purpose is: “Verkstedtjenester vedrørende motorkøyretøy og det som måtte stå i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 54.1m in revenue and NOK 2.0m in operating profit.

Key figures · 2025

Revenue
NOK 54.1m
Operating profit
NOK 2.0m
Equity
NOK 14.4m
Est. value
NOK 16.5m

Financial health · 2025

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

Who owns KVEEN MOTOR AS?

KVEEN MOTOR AS
NOK 54.1m rev. · NOK 2.0m profit

KVEEN MOTOR AS has 1 registered shareholder:

All shareholders and roles →

Group structure

KVEEN MOTOR AS er morselskap for 4 datterselskaper:

Frequently asked questions about KVEEN MOTOR AS

Who owns KVEEN MOTOR AS?

KVEEN AS is the largest registered owner, with 100.0%.

What is the revenue of KVEEN MOTOR AS?

KVEEN MOTOR AS had revenue of NOK 54.1m in 2025.

Who is the general manager of KVEEN MOTOR AS?

Jon Gudbrand Kveen Øvre-Flo is registered as general manager of KVEEN MOTOR AS.

Where is KVEEN MOTOR AS based?

KVEEN MOTOR AS has its business address in Stryn.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.