BIZTRAC BETA
Restaurant activities

TRIPPEL SALTO AS

Org. no. 929186494 Limited company (AS) Stjørdal Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK −9,000
Equity NOK −40,000
Incorporated 2022
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−40k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−9k kr).

TRIPPEL SALTO AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 929186494. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2022. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Servering av mat og drikke og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK −9,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK −9,000
Equity
NOK −40,000

Financial health · 2024

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

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

Who owns TRIPPEL SALTO AS?

DAKOTA HOLDING AS
TRIPPEL SALTO AS
NOK 1.2m rev. · NOK −9,000 profit

TRIPPEL SALTO AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about TRIPPEL SALTO AS

Who owns TRIPPEL SALTO AS?

DAKOTA HOLDING AS is the largest registered owner, with 39.0%.

What is the revenue of TRIPPEL SALTO AS?

TRIPPEL SALTO AS had revenue of NOK 1.2m in 2024.

Who is the general manager of TRIPPEL SALTO AS?

Frank Knutsen is registered as general manager of TRIPPEL SALTO AS.

Where is TRIPPEL SALTO AS based?

TRIPPEL SALTO AS has its business address in Stjørdal.

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.