BIZTRAC BETA
Manufacture of furniture

RINGERIKSVEIEN HOLDING AS

Org. no. 921861621 Limited company (AS) Bærum Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −981
Equity NOK −614,000
Incorporated 2018
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−614k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−981 kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RINGERIKSVEIEN HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 921861621. The business is classified under manufacture of furniture (NACE 31.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i verdipapirer, eiendom samt utleie. I tillegg til kjøp og salg av konsulenttjenester.”.

Key figures · 2024

Operating profit
NOK −981
Equity
NOK −614,000

Financial health · 2024

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

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

Who owns RINGERIKSVEIEN HOLDING AS?

KRIS OG KJELLS MØBELSNEKKERI AS
RINGERIKSVEIEN HOLDING AS
· NOK −981 profit

RINGERIKSVEIEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RINGERIKSVEIEN HOLDING AS

Who owns RINGERIKSVEIEN HOLDING AS?

KRIS OG KJELLS MØBELSNEKKERI AS is the largest registered owner, with 100.0%.

Who is the general manager of RINGERIKSVEIEN HOLDING AS?

Edmond Oliver Risth is registered as general manager of RINGERIKSVEIEN HOLDING AS.

Where is RINGERIKSVEIEN HOLDING AS based?

RINGERIKSVEIEN HOLDING AS has its business address in Skui.

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.