biztrac. BETA
COMPANY REGISTER PROFILE
923430733 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

RIPEL HOLDING AS

Org. no. 923430733 Limited company (AS) Drammen Incorporated 2019 Active
Revenue 2025 NOK 0
Operating profit NOK −39,000
Equity NOK 1.4m
Incorporated 2019
Share capital NOK 100,000

Signals

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

RIPEL HOLDING AS is registered as a limited company in Drammen, Buskerud with organisation number 923430733. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie, kjøpe og selge aksjer og andeler i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −39,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −39,000
▲ +7 %
Equity
NOK 1.4m
▼ −64 %
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
2.72
Very good
Current assets ÷ current liabilities
Profitability
-0.2%
Not satisfactory
Return on total assets
Solidity
8.5%
Weak
Equity as a share of total capital

Who owns RIPEL HOLDING AS?

RIPEL HOLDING AS
NOK 0 rev. · NOK −39,000 profit

RIPEL HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RIPEL HOLDING AS own?

RIPEL HOLDING AS holds stakes in 5 companies:

See the full ownership structure →

Group structure

RIPEL HOLDING AS er morselskap for 5 datterselskaper:

Frequently asked questions about RIPEL HOLDING AS

Who owns RIPEL HOLDING AS?

STIAN R. INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of RIPEL HOLDING AS?

RIPEL HOLDING AS had revenue of NOK 0 in 2025.

Where is RIPEL HOLDING AS based?

RIPEL HOLDING AS has its business address in Drammen.

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.