BIZTRAC BETA
Restaurant activities

NORDIC BISTRO AS

Org. no. 833942662 Limited company (AS) Nord-Aurdal Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 337,000
Equity NOK 293,000
Incorporated 2024
Employees 9
Share capital NOK 30,000

NORDIC BISTRO AS is registered as a limited company in Nord-Aurdal, Innlandet with organisation number 833942662. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2024 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen restaurantdrift - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 337,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 337,000
Equity
NOK 293,000
Est. value
NOK 1.4m

Financial health · 2024

Liquidity
0.67
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.6%
Satisfactory
Equity as a share of total capital

Who owns NORDIC BISTRO AS?

MUHAMMED MAMMAND SALEH SALEH
NORDIC BISTRO AS
NOK 2.2m rev. · NOK 337,000 profit

NORDIC BISTRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORDIC BISTRO AS

Who owns NORDIC BISTRO AS?

MUHAMMED MAMMAND SALEH SALEH is the largest registered owner, with 100.0%.

What is the revenue of NORDIC BISTRO AS?

NORDIC BISTRO AS had revenue of NOK 2.2m in 2024.

Who is the general manager of NORDIC BISTRO AS?

Muhammed Mammand Saleh Saleh is registered as general manager of NORDIC BISTRO AS.

Where is NORDIC BISTRO AS based?

NORDIC BISTRO AS has its business address in Fagernes.

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.