BIZTRAC BETA
Beverage serving activities

RB BARDRIFT AS

Org. no. 932397625 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 5.2m
Operating profit NOK −17,000
Equity NOK 63,000
Incorporated 2023
Employees 11
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−17k kr).

RB BARDRIFT AS is registered as a limited company in Oslo, Oslo with organisation number 932397625. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 2023 and has 11 registered employees. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Drift av bar og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.2m in revenue and NOK −17,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.2m
Operating profit
NOK −17,000
Equity
NOK 63,000
Est. value
NOK 3.7m

Financial health · 2024

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

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

Who owns RB BARDRIFT AS?

LOKALRADIOENE I INNLANDET AS
RB BARDRIFT AS
NOK 5.2m rev. · NOK −17,000 profit

RB BARDRIFT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RB BARDRIFT AS

Who owns RB BARDRIFT AS?

LOKALRADIOENE I INNLANDET AS is the largest registered owner, with 50.0%.

What is the revenue of RB BARDRIFT AS?

RB BARDRIFT AS had revenue of NOK 5.2m in 2025.

Who is the general manager of RB BARDRIFT AS?

Sondre Kleppe Riseng is registered as general manager of RB BARDRIFT AS.

Where is RB BARDRIFT AS based?

RB BARDRIFT 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.