BIZTRAC BETA
Restaurant activities

TRIPPEL S, CAFE, KIOSK OG RESTAURANTDRIFT AS

Org. no. 922359180 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 3.8m
Operating profit NOK 40,000
Equity NOK 190,000
Incorporated 2019
Share capital NOK 30,000

TRIPPEL S, CAFE, KIOSK OG RESTAURANTDRIFT AS is registered as a limited company in Oslo, Oslo with organisation number 922359180. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drift av restaurant, bar, servering, take away, kiosk og alt som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.8m in revenue and NOK 40,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.8m
Operating profit
NOK 40,000
Equity
NOK 190,000
Est. value
NOK 245,000

Financial health · 2024

Liquidity
0.54
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.7%
Good
Equity as a share of total capital

Who owns TRIPPEL S, CAFE, KIOSK OG RESTAURANTDRIFT AS?

WENCHE SELVIG JOHANSEN
TRIPPEL S, CAFE, KIOSK OG RESTAURANTDRIFT AS
NOK 3.8m rev. · NOK 40,000 profit

TRIPPEL S, CAFE, KIOSK OG RESTAURANTDRIFT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TRIPPEL S, CAFE, KIOSK OG RESTAURANTDRIFT AS

Who owns TRIPPEL S, CAFE, KIOSK OG RESTAURANTDRIFT AS?

WENCHE SELVIG JOHANSEN is the largest registered owner, with 80.0%.

What is the revenue of TRIPPEL S, CAFE, KIOSK OG RESTAURANTDRIFT AS?

TRIPPEL S, CAFE, KIOSK OG RESTAURANTDRIFT AS had revenue of NOK 3.8m in 2024.

Where is TRIPPEL S, CAFE, KIOSK OG RESTAURANTDRIFT AS based?

TRIPPEL S, CAFE, KIOSK OG RESTAURANTDRIFT AS has its business address in Oslo.

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.