BIZTRAC BETA
Wholesale of other household goods

R8 ENGROS AS

Org. no. 929918312 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 4,000
Operating profit NOK −11,000
Equity NOK −14,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−14k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−11k kr).

R8 ENGROS AS is registered as a limited company in Oslo, Oslo with organisation number 929918312. The business is classified under wholesale of other household goods (NACE 46.490). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 60 shares. The company's stated purpose is: “Import og salg av interiørartikler, gaveartikler og møbler mot butikker, bedrifter og reklamegave markedet.”. The most recent filed accounts, for the 2025 financial year, show NOK 4,000 in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 4,000
Operating profit
NOK −11,000
Equity
NOK −14,000

Financial health · 2025

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

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

Who owns R8 ENGROS AS?

ELVI HOLDING AS
R8 ENGROS AS
NOK 4,000 rev. · NOK −11,000 profit

R8 ENGROS AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about R8 ENGROS AS

Who owns R8 ENGROS AS?

ELVI HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of R8 ENGROS AS?

R8 ENGROS AS had revenue of NOK 4,000 in 2025.

Who is the general manager of R8 ENGROS AS?

Vidar Myrer is registered as general manager of R8 ENGROS AS.

Where is R8 ENGROS AS based?

R8 ENGROS AS has its business address in Oslo.

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.