BIZTRAC BETA
Repair and maintenance of motor vehicles

OVESEN SERVICEPARTNER AS

Org. no. 826541962 Limited company (AS) Trondheim Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 354,000
Operating profit NOK 54,000
Equity NOK 19,000
Incorporated 2021
Share capital NOK 30,000

OVESEN SERVICEPARTNER AS is registered as a limited company in Trondheim, Trøndelag with organisation number 826541962. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Bilverksted og bruktbilsalg.”. The most recent filed accounts, for the 2025 financial year, show NOK 354,000 in revenue and NOK 54,000 in operating profit.

Key figures · 2025

Revenue
NOK 354,000
Operating profit
NOK 54,000
Equity
NOK 19,000
Est. value
NOK 213,000

Financial health · 2025

Liquidity
1.20
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns OVESEN SERVICEPARTNER AS?

BØRGE OVESEN
OVESEN SERVICEPARTNER AS
NOK 354,000 rev. · NOK 54,000 profit

OVESEN SERVICEPARTNER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OVESEN SERVICEPARTNER AS

Who owns OVESEN SERVICEPARTNER AS?

BØRGE OVESEN is the largest registered owner, with 100.0%.

What is the revenue of OVESEN SERVICEPARTNER AS?

OVESEN SERVICEPARTNER AS had revenue of NOK 354,000 in 2025.

Who is the general manager of OVESEN SERVICEPARTNER AS?

Børge Ovesen is registered as general manager of OVESEN SERVICEPARTNER AS.

Where is OVESEN SERVICEPARTNER AS based?

OVESEN SERVICEPARTNER AS has its business address in Trondheim.

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.