BIZTRAC BETA
Restaurant activities

OPSAHLGARDEN AS

Org. no. 898884872 Limited company (AS) Kongsberg Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 5.8m
Operating profit NOK −644,000
Equity NOK 1.7m
Incorporated 2012
Employees 5
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−644k kr).

OPSAHLGARDEN AS is registered as a limited company in Kongsberg, Buskerud with organisation number 898884872. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2012 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 50 shares. The company's stated purpose is: “Restaurantdrift, catering, produksjon og omsetning av mat og drikke, import av alkoholholdige drikkevarer, samt annen virksomhet som står i nær tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.8m in revenue and NOK −644,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.8m
Operating profit
NOK −644,000
Equity
NOK 1.7m
Est. value
NOK 4.9m

Financial health · 2024

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

Who owns OPSAHLGARDEN AS?

EROHT AS
OPSAHLGARDEN AS
NOK 5.8m rev. · NOK −644,000 profit

OPSAHLGARDEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OPSAHLGARDEN AS

Who owns OPSAHLGARDEN AS?

EROHT AS is the largest registered owner, with 100.0%.

What is the revenue of OPSAHLGARDEN AS?

OPSAHLGARDEN AS had revenue of NOK 5.8m in 2024.

Who is the general manager of OPSAHLGARDEN AS?

Katrine Kvammen Kolset is registered as general manager of OPSAHLGARDEN AS.

Where is OPSAHLGARDEN AS based?

OPSAHLGARDEN AS has its business address in Kongsberg.

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.