BIZTRAC BETA
Retail sale of automotive fuel

KOPERVIK BENSIN OG STORKIOSK AS

Org. no. 860203782 Limited company (AS) Karmøy Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 156,000
Equity NOK 3.1m
Incorporated 1991
Share capital NOK 100,000

KOPERVIK BENSIN OG STORKIOSK AS is registered as a limited company in Karmøy, Rogaland with organisation number 860203782. The business is classified under retail sale of automotive fuel (NACE 47.300). The company was incorporated in 1991. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Handel i forbindelse med drift av verksted og bensinstasjon.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 156,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 156,000
Equity
NOK 3.1m
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns KOPERVIK BENSIN OG STORKIOSK AS?

R KVALØY HOLDING AS
KOPERVIK BENSIN OG STORKIOSK AS
NOK 1.1m rev. · NOK 156,000 profit

KOPERVIK BENSIN OG STORKIOSK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KOPERVIK BENSIN OG STORKIOSK AS

Who owns KOPERVIK BENSIN OG STORKIOSK AS?

R KVALØY HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of KOPERVIK BENSIN OG STORKIOSK AS?

KOPERVIK BENSIN OG STORKIOSK AS had revenue of NOK 1.1m in 2025.

Who is the general manager of KOPERVIK BENSIN OG STORKIOSK AS?

Randi Kvaløy is registered as general manager of KOPERVIK BENSIN OG STORKIOSK AS.

Where is KOPERVIK BENSIN OG STORKIOSK AS based?

KOPERVIK BENSIN OG STORKIOSK AS has its business address in Kopervik.

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.