BIZTRAC BETA
Retail sale of clothing

SPESIALKAFFE AS

Org. no. 928091287 Limited company (AS) Eidskog Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 75,000
Operating profit NOK −6,000
Equity NOK −136,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

SPESIALKAFFE AS is registered as a limited company in Eidskog, Innlandet with organisation number 928091287. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive kaffebar, baristakurs og kjøpe og selge kaffe.”. The most recent filed accounts, for the 2025 financial year, show NOK 75,000 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 75,000
Operating profit
NOK −6,000
Equity
NOK −136,000

Financial health · 2025

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

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

Who owns SPESIALKAFFE AS?

BALINT MESZAROS
SPESIALKAFFE AS
NOK 75,000 rev. · NOK −6,000 profit

SPESIALKAFFE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SPESIALKAFFE AS

Who owns SPESIALKAFFE AS?

BALINT MESZAROS is the largest registered owner, with 50.0%.

What is the revenue of SPESIALKAFFE AS?

SPESIALKAFFE AS had revenue of NOK 75,000 in 2025.

Who is the general manager of SPESIALKAFFE AS?

Csilla Katalin Szabo is registered as general manager of SPESIALKAFFE AS.

Where is SPESIALKAFFE AS based?

SPESIALKAFFE AS has its business address in Åbogen.

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.