biztrac. BETA
COMPANY REGISTER PROFILE
921960417 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Hairdressing and barber activities

RBH AS

Org. no. 921960417 Limited company (AS) Oslo Incorporated 2018 Active
Revenue 2025 NOK 3.3m
Operating profit NOK −60,000
Equity NOK −111,000
Incorporated 2018
Share capital NOK 600,000

Signals

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

RBH AS is registered as a limited company in Oslo, Oslo with organisation number 921960417. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2018. Registered share capital is NOK 600,000, divided into 600 shares. The company's stated purpose is: “Frisør- og barberervirksomhet med tilhørende tjenester samt utføre enkle håndverker tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK −60,000 in operating profit.

Former names: M ROOM METRO SENTER AS, M ROOM SHOPS NORGE AS

Key figures · 2025

Revenue
NOK 3.3m
▼ −18 %
Operating profit
NOK −60,000
▼ −118 %
Equity
NOK −111,000
▼ −166 %
Est. value
NOK 609,000

Financial health · 2025

Liquidity
0.75
Weak
Current assets ÷ current liabilities
Profitability
-14.9%
Not satisfactory
Return on total assets
Solidity
-33.2%
Weak
Equity as a share of total capital

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

Who owns RBH AS?

RBH AS
NOK 3.3m rev. · NOK −60,000 profit

RBH AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RBH AS

Who owns RBH AS?

RIDIVEA AS is the largest registered owner, with 100.0%.

What is the revenue of RBH AS?

RBH AS had revenue of NOK 3.3m in 2025.

Who is the general manager of RBH AS?

Roger Bråten is registered as general manager of RBH AS.

Where is RBH AS based?

RBH 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 03.10.2026.

Report a problem

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