BIZTRAC BETA
Repair and maintenance of motor vehicles

SØVIK BILSERVICE AS

Org. no. 917807922 Limited company (AS) Rauma Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 3.4m
Operating profit NOK 43,000
Equity NOK 264,000
Incorporated 2016
Share capital NOK 80,000

SØVIK BILSERVICE AS is registered as a limited company in Rauma, Møre og Romsdal with organisation number 917807922. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2016. Registered share capital is NOK 80,000, divided into 80 shares. The company's stated purpose is: “Reparasjon og service av biler, investering i aksjer, samt det som naturlig står i forbindelse med dette herunder deltakelse i andre selskaper i tilsvarende bransje.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.4m in revenue and NOK 43,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.4m
Operating profit
NOK 43,000
Equity
NOK 264,000
Est. value
NOK 307,000

Financial health · 2024

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

Who owns SØVIK BILSERVICE AS?

FRODE BRUDESKAR TALSTAD
SØVIK BILSERVICE AS
NOK 3.4m rev. · NOK 43,000 profit

SØVIK BILSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SØVIK BILSERVICE AS

Who owns SØVIK BILSERVICE AS?

FRODE BRUDESKAR TALSTAD is the largest registered owner, with 100.0%.

What is the revenue of SØVIK BILSERVICE AS?

SØVIK BILSERVICE AS had revenue of NOK 3.4m in 2024.

Who is the general manager of SØVIK BILSERVICE AS?

Frode Brudeskar Talstad is registered as general manager of SØVIK BILSERVICE AS.

Where is SØVIK BILSERVICE AS based?

SØVIK BILSERVICE AS has its business address in Måndalen.

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.