BIZTRAC BETA
Wholesale of mining, construction and civil engineering machinery

RIG SUPPLY AS

Org. no. 976943619 Limited company (AS) Stavanger Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 34.7m
Operating profit NOK 5.5m
Equity NOK 3.7m
Incorporated 1996
Share capital NOK 1.4m

RIG SUPPLY AS is registered as a limited company in Stavanger, Rogaland with organisation number 976943619. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 1996. Registered share capital is NOK 1.4m, divided into 1350 shares. The company's stated purpose is: “Investeringer i verdipapirer og fast eiendom. Selskapet kan også drive med fremstilling/salg av handelsvarer, konsulenttjenester og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 34.7m in revenue and NOK 5.5m in operating profit.

Key figures · 2025

Revenue
NOK 34.7m
Operating profit
NOK 5.5m
Equity
NOK 3.7m
Est. value
NOK 19.2m

Financial health · 2025

Liquidity
1.42
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.7%
Good
Equity as a share of total capital

Who owns RIG SUPPLY AS?

BS FINANS AS
RIG SUPPLY AS
NOK 34.7m rev. · NOK 5.5m profit

RIG SUPPLY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RIG SUPPLY AS

Who owns RIG SUPPLY AS?

BS FINANS AS is the largest registered owner, with 100.0%.

What is the revenue of RIG SUPPLY AS?

RIG SUPPLY AS had revenue of NOK 34.7m in 2025.

Who is the general manager of RIG SUPPLY AS?

Atle Stian Vaaland is registered as general manager of RIG SUPPLY AS.

Where is RIG SUPPLY AS based?

RIG SUPPLY AS has its business address in Stavanger.

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.