BIZTRAC BETA
Rental and leasing of other personal and household goods

RIGGPARTNER AS

Org. no. 914264758 Limited company (AS) Lillestrøm Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 9.6m
Operating profit NOK −387,000
Equity NOK 983,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−387k kr).

RIGGPARTNER AS is registered as a limited company in Lillestrøm, Akershus with organisation number 914264758. The business is classified under rental and leasing of other personal and household goods (NACE 77.220). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Tilby salg og utleie av produkter og utstyr til kulturbransjen, samt annet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.6m in revenue and NOK −387,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.6m
Operating profit
NOK −387,000
Equity
NOK 983,000
Est. value
NOK 6.4m

Financial health · 2024

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

Who owns RIGGPARTNER AS?

EPS SCANDINAVIA AB
RIGGPARTNER AS
NOK 9.6m rev. · NOK −387,000 profit

RIGGPARTNER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RIGGPARTNER AS

Who owns RIGGPARTNER AS?

EPS SCANDINAVIA AB is the largest registered owner, with 100.0%.

What is the revenue of RIGGPARTNER AS?

RIGGPARTNER AS had revenue of NOK 9.6m in 2024.

Who is the general manager of RIGGPARTNER AS?

Torgeir Stegane is registered as general manager of RIGGPARTNER AS.

Where is RIGGPARTNER AS based?

RIGGPARTNER AS has its business address in Skedsmokorset.

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.