BIZTRAC BETA
Rental and operating of own or leased real estate

TRIPPEL HOLDING AS

Org. no. 917509956 Limited company (AS) Drammen Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −137,000
Equity NOK 40.8m
Incorporated 2016
Share capital NOK 30,000

Signals

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

TRIPPEL HOLDING AS is registered as a limited company in Drammen, Buskerud with organisation number 917509956. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eie andre selskaper. Selskapet kan også drive med kjøp/salg av løsøre og verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −137,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −137,000
Equity
NOK 40.8m
Est. value
NOK 37.2m

Financial health · 2025

Liquidity
30.72
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
90.1%
Very good
Equity as a share of total capital

Who owns TRIPPEL HOLDING AS?

OVE BYRMO HOLDING AS
TRIPPEL HOLDING AS
NOK 0 rev. · NOK −137,000 profit

TRIPPEL HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TRIPPEL HOLDING AS own?

TRIPPEL HOLDING AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about TRIPPEL HOLDING AS

Who owns TRIPPEL HOLDING AS?

OVE BYRMO HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of TRIPPEL HOLDING AS?

TRIPPEL HOLDING AS had revenue of NOK 0 in 2025.

Where is TRIPPEL HOLDING AS based?

TRIPPEL 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 15.06.2026.

Report a problem

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