BIZTRAC BETA
Restaurant activities

TASTY BITE AS

Org. no. 997826043 Limited company (AS) Bærum Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 4.2m
Operating profit NOK 562,000
Equity NOK −50,000
Incorporated 2012
Employees 5
Share capital NOK 30,000

Signals

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

TASTY BITE AS is registered as a limited company in Bærum, Akershus with organisation number 997826043. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2012 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Selskapets virksomhet er gatekjøkken og bilvaskehall og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.2m in revenue and NOK 562,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.2m
Operating profit
NOK 562,000
Equity
NOK −50,000
Est. value
NOK 4.2m

Financial health · 2024

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

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

Who owns TASTY BITE AS?

SHAHID BASHIR
TASTY BITE AS
NOK 4.2m rev. · NOK 562,000 profit

TASTY BITE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TASTY BITE AS

Who owns TASTY BITE AS?

SHAHID BASHIR is the largest registered owner, with 100.0%.

What is the revenue of TASTY BITE AS?

TASTY BITE AS had revenue of NOK 4.2m in 2024.

Who is the general manager of TASTY BITE AS?

Shahid Bashir is registered as general manager of TASTY BITE AS.

Where is TASTY BITE AS based?

TASTY BITE AS has its business address in Bekkestua.

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.