BIZTRAC BETA
Repair and maintenance of motor vehicles

SARTOR BILOPPRETTING AS

Org. no. 928886360 Limited company (AS) Øygarden Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 41.1m
Operating profit NOK 11.4m
Equity NOK 17.8m
Incorporated 2022
Employees 15
Share capital NOK 500,000

SARTOR BILOPPRETTING AS is registered as a limited company in Øygarden, Vestland with organisation number 928886360. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2022 and has 15 registered employees. Registered share capital is NOK 500,000, divided into 200 shares. The company's stated purpose is: “Verksted for motor- og bilskader og hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 41.1m in revenue and NOK 11.4m in operating profit.

Key figures · 2024

Revenue
NOK 41.1m
Operating profit
NOK 11.4m
Equity
NOK 17.8m
Est. value
NOK 43.3m

Financial health · 2024

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

Who owns SARTOR BILOPPRETTING AS?

PANORAMA EIGEDOMSUTVIKLING AS
SARTOR BILOPPRETTING AS
NOK 41.1m rev. · NOK 11.4m profit

SARTOR BILOPPRETTING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SARTOR BILOPPRETTING AS own?

SARTOR BILOPPRETTING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SARTOR BILOPPRETTING AS

Who owns SARTOR BILOPPRETTING AS?

PANORAMA EIGEDOMSUTVIKLING AS is the largest registered owner, with 50.0%.

What is the revenue of SARTOR BILOPPRETTING AS?

SARTOR BILOPPRETTING AS had revenue of NOK 41.1m in 2024.

Where is SARTOR BILOPPRETTING AS based?

SARTOR BILOPPRETTING AS has its business address in Straume.

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.