BIZTRAC BETA
COMPANY REGISTER PROFILE
920544401 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Restaurant activities

NOMADE CAFÈ AS

Org. no. 920544401 Limited company (AS) Vestvågøy Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 214,000
Operating profit NOK 32,000
Equity NOK 73,000
Incorporated 2018
Share capital NOK 30,000

NOMADE CAFÈ AS is registered as a limited company in Vestvågøy, Nordland with organisation number 920544401. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drift av cafèer og salg av produkter som naturlig faller inn under dette. Selskapet kan også delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 214,000 in revenue and NOK 32,000 in operating profit.

Key figures · 2024

Revenue
NOK 214,000
Operating profit
NOK 32,000
Equity
NOK 73,000
Est. value
NOK 164,000

Financial health · 2024

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

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

Who owns NOMADE CAFÈ AS?

ZUZANA SLOVAKOVA
NOMADE CAFÈ AS
NOK 214,000 rev. · NOK 32,000 profit

NOMADE CAFÈ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NOMADE CAFÈ AS

Who owns NOMADE CAFÈ AS?

ZUZANA SLOVAKOVA is the largest registered owner, with 100.0%.

What is the revenue of NOMADE CAFÈ AS?

NOMADE CAFÈ AS had revenue of NOK 214,000 in 2024.

Who is the general manager of NOMADE CAFÈ AS?

Zuzana Slovakova is registered as general manager of NOMADE CAFÈ AS.

Where is NOMADE CAFÈ AS based?

NOMADE CAFÈ AS has its business address in Bøstad.

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.