BIZTRAC BETA
Restaurant activities

CAFÉ TRIPPEL M AS

Org. no. 928442721 Limited company (AS) Arendal Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 3.8m
Operating profit NOK −180,000
Equity NOK −644,000
Incorporated 2021
Employees 12
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−644k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−180k kr).

CAFÉ TRIPPEL M AS is registered as a limited company in Arendal, Agder with organisation number 928442721. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2021 and has 12 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drift av cafe og hva som hører naturlig sammen med dette. Selskapet kan også delta med eierandel i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.8m in revenue and NOK −180,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.8m
Operating profit
NOK −180,000
Equity
NOK −644,000

Financial health · 2025

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

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

Who owns CAFÉ TRIPPEL M AS?

No shareholders are registered for CAFÉ TRIPPEL M AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about CAFÉ TRIPPEL M AS

What is the revenue of CAFÉ TRIPPEL M AS?

CAFÉ TRIPPEL M AS had revenue of NOK 3.8m in 2025.

Who is the general manager of CAFÉ TRIPPEL M AS?

Maria Naine is registered as general manager of CAFÉ TRIPPEL M AS.

Where is CAFÉ TRIPPEL M AS based?

CAFÉ TRIPPEL M AS has its business address in Arendal.

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.