BIZTRAC BETA
Beverage serving activities

TORGGATA CAMPING AS

Org. no. 919681136 Limited company (AS) Drammen Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK −303,000
Equity NOK 1.3m
Incorporated 2017
Employees 6
Share capital NOK 30,000

Signals

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

TORGGATA CAMPING AS is registered as a limited company in Drammen, Buskerud with organisation number 919681136. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 2017 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 120 shares. The company's stated purpose is: “Cafe- og restaurantdrift og dermed beslektet virksomhet samt aktiviteter som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK −303,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
Operating profit
NOK −303,000
Equity
NOK 1.3m
Est. value
NOK 2.7m

Financial health · 2024

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

Who owns TORGGATA CAMPING AS?

COCOBOLO AS
TORGGATA CAMPING AS
NOK 2.9m rev. · NOK −303,000 profit

TORGGATA CAMPING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TORGGATA CAMPING AS

Who owns TORGGATA CAMPING AS?

COCOBOLO AS is the largest registered owner, with 33.3%.

What is the revenue of TORGGATA CAMPING AS?

TORGGATA CAMPING AS had revenue of NOK 2.9m in 2025.

Who is the general manager of TORGGATA CAMPING AS?

Gunnar Grinaker is registered as general manager of TORGGATA CAMPING AS.

Where is TORGGATA CAMPING AS based?

TORGGATA CAMPING 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.