BIZTRAC BETA
Retail sale of automotive fuel

SMØRHOLM OLJEPRODUKTER AS

Org. no. 947079956 Limited company (AS) Hustadvika Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK 34,000
Equity NOK 621,000
Incorporated 1988
Share capital NOK 200,000

SMØRHOLM OLJEPRODUKTER AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 947079956. The business is classified under retail sale of automotive fuel (NACE 47.300). The company was incorporated in 1988. Registered share capital is NOK 200,000. The company's stated purpose is: “Å drive forretningsvirksomhet, samt det som naturlig står i forbindelse med dette, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK 34,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK 34,000
Equity
NOK 621,000
Est. value
NOK 487,000

Financial health · 2024

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

Who owns SMØRHOLM OLJEPRODUKTER AS?

ALF EGIL SMØRHOLM
SMØRHOLM OLJEPRODUKTER AS
NOK 2.5m rev. · NOK 34,000 profit

SMØRHOLM OLJEPRODUKTER AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SMØRHOLM OLJEPRODUKTER AS

Who owns SMØRHOLM OLJEPRODUKTER AS?

ALF EGIL SMØRHOLM is the largest registered owner, with 50.0%.

What is the revenue of SMØRHOLM OLJEPRODUKTER AS?

SMØRHOLM OLJEPRODUKTER AS had revenue of NOK 2.5m in 2024.

Who is the general manager of SMØRHOLM OLJEPRODUKTER AS?

Roy Arve Smørholm is registered as general manager of SMØRHOLM OLJEPRODUKTER AS.

Where is SMØRHOLM OLJEPRODUKTER AS based?

SMØRHOLM OLJEPRODUKTER AS has its business address in Vevang.

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.