BIZTRAC BETA
Restaurant activities

NYE CAFE MOLDEBADET AS

Org. no. 914769183 Limited company (AS) Sarpsborg Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −3,000
Equity NOK −424,000
Incorporated 2014
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−424k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3k kr).

NYE CAFE MOLDEBADET AS is registered as a limited company in Sarpsborg, Østfold with organisation number 914769183. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drift av kafe.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK −424,000

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
Not available
Equity as a share of total capital

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

Who owns NYE CAFE MOLDEBADET AS?

LULZIM KOLDASHI
NYE CAFE MOLDEBADET AS
NOK 0 rev. · NOK −3,000 profit

NYE CAFE MOLDEBADET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NYE CAFE MOLDEBADET AS

Who owns NYE CAFE MOLDEBADET AS?

LULZIM KOLDASHI is the largest registered owner, with 100.0%.

What is the revenue of NYE CAFE MOLDEBADET AS?

NYE CAFE MOLDEBADET AS had revenue of NOK 0 in 2024.

Who is the general manager of NYE CAFE MOLDEBADET AS?

Lulzim Koldashi is registered as general manager of NYE CAFE MOLDEBADET AS.

Where is NYE CAFE MOLDEBADET AS based?

NYE CAFE MOLDEBADET AS has its business address in Sarpsborg.

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.