BIZTRAC BETA
Repair and maintenance of motor vehicles

STORBILSERVICE AS

Org. no. 980059227 Limited company (AS) Sykkylven Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 15.3m
Operating profit NOK 38,000
Equity NOK 1.5m
Incorporated 1998
Employees 9
Share capital NOK 1.4m

STORBILSERVICE AS is registered as a limited company in Sykkylven, Møre og Romsdal with organisation number 980059227. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 1998 and has 9 registered employees. Registered share capital is NOK 1.4m, divided into 1350 shares. The company's stated purpose is: “Drift av vaskehall og verksted for reparasjon og vedlikehold av kjøretøy, og hva dermed står i forbindelse, samt salg av diesel.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.3m in revenue and NOK 38,000 in operating profit.

Key figures · 2024

Revenue
NOK 15.3m
Operating profit
NOK 38,000
Equity
NOK 1.5m
Est. value
NOK 899,000

Financial health · 2024

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

Who owns STORBILSERVICE AS?

RUSUP AS
STORBILSERVICE AS
NOK 15.3m rev. · NOK 38,000 profit

STORBILSERVICE AS has 3 registered shareholders:

All shareholders and roles →

Group structure

STORBILSERVICE AS er morselskap for 4 datterselskaper:

Frequently asked questions about STORBILSERVICE AS

Who owns STORBILSERVICE AS?

RUSUP AS is the largest registered owner, with 47.5%.

What is the revenue of STORBILSERVICE AS?

STORBILSERVICE AS had revenue of NOK 15.3m in 2024.

Who is the general manager of STORBILSERVICE AS?

Fredrik Emdal is registered as general manager of STORBILSERVICE AS.

Where is STORBILSERVICE AS based?

STORBILSERVICE AS has its business address in Straumgjerde.

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.