BIZTRAC BETA
Other passenger transport in coastal waters

DRØBAK RIB SAFARI AS

Org. no. 929000552 Limited company (AS) Frogn Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 479,000
Operating profit NOK 41,000
Equity NOK −365,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

DRØBAK RIB SAFARI AS is registered as a limited company in Frogn, Akershus with organisation number 929000552. The business is classified under other passenger transport in coastal waters (NACE 50.109). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Persontransport. Rib safari i Oslofjorden.”. The most recent filed accounts, for the 2025 financial year, show NOK 479,000 in revenue and NOK 41,000 in operating profit.

Key figures · 2025

Revenue
NOK 479,000
Operating profit
NOK 41,000
Equity
NOK −365,000
Est. value
NOK 260,000

Financial health · 2025

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

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

Who owns DRØBAK RIB SAFARI AS?

AXEL BRUN
DRØBAK RIB SAFARI AS
NOK 479,000 rev. · NOK 41,000 profit

DRØBAK RIB SAFARI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DRØBAK RIB SAFARI AS

Who owns DRØBAK RIB SAFARI AS?

AXEL BRUN is the largest registered owner, with 100.0%.

What is the revenue of DRØBAK RIB SAFARI AS?

DRØBAK RIB SAFARI AS had revenue of NOK 479,000 in 2025.

Who is the general manager of DRØBAK RIB SAFARI AS?

Axel Brun is registered as general manager of DRØBAK RIB SAFARI AS.

Where is DRØBAK RIB SAFARI AS based?

DRØBAK RIB SAFARI AS has its business address in Drøbak.

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.