biztrac. BETA
COMPANY REGISTER PROFILE
968358987 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Manufacture of furniture

RIVAL AS

Org. no. 968358987 Limited company (AS) Vestby Incorporated 1993 Active
Ownership graph ↗
Revenue 2025 NOK 25.4m
Operating profit NOK −5.5m
Equity NOK 2.4m
Incorporated 1993
Employees 17
Share capital NOK 2.4m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5,5 mill kr).

RIVAL AS is registered as a limited company in Vestby, Akershus with organisation number 968358987. The business is classified under manufacture of furniture (NACE 31.000). The company was incorporated in 1993 and has 17 registered employees. Registered share capital is NOK 2.4m, divided into 240 shares. The company's stated purpose is: “Handel og produksjon med interiørprodukter og annen virksomhet som naturlig hører inn under dette, drift og forvaltning av eiendommer, samt kjøp og salg av disse.”. The most recent filed accounts, for the 2025 financial year, show NOK 25.4m in revenue and NOK −5.5m in operating profit.

Key figures · 2025

Revenue
NOK 25.4m
▼ −1 %
Operating profit
NOK −5.5m
▲ +33 %
Equity
NOK 2.4m
▼ −70 %
Est. value
NOK 14.9m

Financial health · 2025

Liquidity
1.42
Satisfactory
Current assets ÷ current liabilities
Profitability
-48.8%
Not satisfactory
Return on total assets
Solidity
24.8%
Good
Equity as a share of total capital

Who owns RIVAL AS?

RIVAL AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about RIVAL AS

Who owns RIVAL AS?

Birger Torleif Grønland is the largest registered owner, with 50.8%.

What is the revenue of RIVAL AS?

RIVAL AS had revenue of NOK 25.4m in 2025.

Who is the general manager of RIVAL AS?

Remi Bhaskar Greiner is registered as general manager of RIVAL AS.

Where is RIVAL AS based?

RIVAL AS has its business address in Vestby.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.