BIZTRAC BETA
Restaurant activities

VESTBY SPISERI AS

Org. no. 930816736 Limited company (AS) Moss Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK 165,000
Equity NOK −26,000
Incorporated 2023
Employees 7
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−26k kr).

VESTBY SPISERI AS is registered as a limited company in Moss, Østfold with organisation number 930816736. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2023 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Drive kafé og restaurant, og annet som naturlig hører til under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK 165,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK 165,000
Equity
NOK −26,000
Est. value
NOK 961,000

Financial health · 2024

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

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

Who owns VESTBY SPISERI AS?

FAISAL MUNIR
VESTBY SPISERI AS
NOK 2.1m rev. · NOK 165,000 profit

VESTBY SPISERI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VESTBY SPISERI AS

Who owns VESTBY SPISERI AS?

FAISAL MUNIR is the largest registered owner, with 100.0%.

What is the revenue of VESTBY SPISERI AS?

VESTBY SPISERI AS had revenue of NOK 2.1m in 2024.

Who is the general manager of VESTBY SPISERI AS?

Faisal Munir is registered as general manager of VESTBY SPISERI AS.

Where is VESTBY SPISERI AS based?

VESTBY SPISERI AS has its business address in Moss.

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.