BIZTRAC BETA
Repair and maintenance of motor vehicles

SARPSBORG AUTOSERVICE AS

Org. no. 815763262 Limited company (AS) Sarpsborg Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 5.5m
Operating profit NOK 1.0m
Equity NOK 7.7m
Incorporated 2015
Share capital NOK 30,000

SARPSBORG AUTOSERVICE AS is registered as a limited company in Sarpsborg, Østfold with organisation number 815763262. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Virksomhet bransjer, Reparasjon samt salgs og kjøp kjøretøy bilutleie og vedlikehold og reparasjon av motorvogner, unntatt motorsykler”. The most recent filed accounts, for the 2025 financial year, show NOK 5.5m in revenue and NOK 1.0m in operating profit.

Key figures · 2025

Revenue
NOK 5.5m
Operating profit
NOK 1.0m
Equity
NOK 7.7m
Est. value
NOK 8.1m

Financial health · 2025

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

Who owns SARPSBORG AUTOSERVICE AS?

FAISAL HAMID HAJI
SARPSBORG AUTOSERVICE AS
NOK 5.5m rev. · NOK 1.0m profit

SARPSBORG AUTOSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SARPSBORG AUTOSERVICE AS

Who owns SARPSBORG AUTOSERVICE AS?

FAISAL HAMID HAJI is the largest registered owner, with 100.0%.

What is the revenue of SARPSBORG AUTOSERVICE AS?

SARPSBORG AUTOSERVICE AS had revenue of NOK 5.5m in 2025.

Who is the general manager of SARPSBORG AUTOSERVICE AS?

Faisal Hamid Haji is registered as general manager of SARPSBORG AUTOSERVICE AS.

Where is SARPSBORG AUTOSERVICE AS based?

SARPSBORG AUTOSERVICE AS has its business address in Sarpsborg.

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.