BIZTRAC BETA
Restaurant activities

ELGSJØ KAFE AS

Org. no. 825272852 Limited company (AS) Notodden Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK −125,000
Equity NOK −75,000
Incorporated 2020
Employees 5
Share capital NOK 30,000

Signals

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

ELGSJØ KAFE AS is registered as a limited company in Notodden, Telemark with organisation number 825272852. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2020 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drift av restaurant/kafe og salg som hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK −125,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
Operating profit
NOK −125,000
Equity
NOK −75,000

Financial health · 2025

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

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

Who owns ELGSJØ KAFE AS?

HANS GUNNAR HAAVE
ELGSJØ KAFE AS
NOK 2.7m rev. · NOK −125,000 profit

ELGSJØ KAFE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ELGSJØ KAFE AS

Who owns ELGSJØ KAFE AS?

HANS GUNNAR HAAVE is the largest registered owner, with 100.0%.

What is the revenue of ELGSJØ KAFE AS?

ELGSJØ KAFE AS had revenue of NOK 2.7m in 2025.

Who is the general manager of ELGSJØ KAFE AS?

Hans Gunnar Haave is registered as general manager of ELGSJØ KAFE AS.

Where is ELGSJØ KAFE AS based?

ELGSJØ KAFE AS has its business address in Notodden.

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.