BIZTRAC BETA
Repair and maintenance of motor vehicles

RIPLE AUTO AS

Org. no. 861801772 Limited company (AS) Bergen Incorporated 1991 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK 79,000
Equity NOK −7.0m
Incorporated 1991
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−7,0 mill kr).

RIPLE AUTO AS is registered as a limited company in Bergen, Vestland with organisation number 861801772. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 1991. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Verkstedsdrift, kjøp og salg av nye og brukte biler, kjøp og salg av nye og brukte deler, skrap- handel samt tilknyttet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK 79,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK 79,000
Equity
NOK −7.0m
Est. value
NOK 376,000

Financial health · 2024

Liquidity
1.11
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1713.4%
Weak
Equity as a share of total capital

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

Who owns RIPLE AUTO AS?

TORUNN RIPLE
RIPLE AUTO AS
NOK 2.1m rev. · NOK 79,000 profit

RIPLE AUTO AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about RIPLE AUTO AS

Who owns RIPLE AUTO AS?

TORUNN RIPLE is the largest registered owner, with 33.5%.

What is the revenue of RIPLE AUTO AS?

RIPLE AUTO AS had revenue of NOK 2.1m in 2024.

Who is the general manager of RIPLE AUTO AS?

Karl Johan Riple is registered as general manager of RIPLE AUTO AS.

Where is RIPLE AUTO AS based?

RIPLE AUTO AS has its business address in Nesttun.

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.