BIZTRAC BETA
Other non-specialised retail sale

RESERVEDEL AS

Org. no. 999177735 Limited company (AS) Lillestrøm Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 21.3m
Operating profit NOK 105,000
Equity NOK −108,000
Incorporated 2012
Employees 6
Share capital NOK 50,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−108k kr).

RESERVEDEL AS is registered as a limited company in Lillestrøm, Akershus with organisation number 999177735. The business is classified under other non-specialised retail sale (NACE 47.120). The company was incorporated in 2012 and has 6 registered employees. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Kjøp og salg av reservedeler, samt virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 21.3m in revenue and NOK 105,000 in operating profit.

Key figures · 2024

Revenue
NOK 21.3m
Operating profit
NOK 105,000
Equity
NOK −108,000
Est. value
NOK 552,000

Financial health · 2024

Liquidity
0.99
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns RESERVEDEL AS?

SELBOE GROUP AS
RESERVEDEL AS
NOK 21.3m rev. · NOK 105,000 profit

RESERVEDEL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RESERVEDEL AS

Who owns RESERVEDEL AS?

SELBOE GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of RESERVEDEL AS?

RESERVEDEL AS had revenue of NOK 21.3m in 2024.

Who is the general manager of RESERVEDEL AS?

Øyvind Skår Selboe is registered as general manager of RESERVEDEL AS.

Where is RESERVEDEL AS based?

RESERVEDEL 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.