BIZTRAC BETA
Restaurant activities

PIRI PIRI LYNGBYGG AS

Org. no. 922042446 Limited company (AS) Lyngdal Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK 377,000
Equity NOK 633,000
Incorporated 2018
Share capital NOK 30,000

PIRI PIRI LYNGBYGG AS is registered as a limited company in Lyngdal, Agder with organisation number 922042446. 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 30 shares. The company's stated purpose is: “Å drive restaurantvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK 377,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK 377,000
Equity
NOK 633,000
Est. value
NOK 1.4m

Financial health · 2024

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
50.2%
Very good
Equity as a share of total capital

Who owns PIRI PIRI LYNGBYGG AS?

MUSTAFA MUHAIMED MUSTAFA
PIRI PIRI LYNGBYGG AS
NOK 1.4m rev. · NOK 377,000 profit

PIRI PIRI LYNGBYGG AS has 2 registered shareholders:

All shareholders and roles →

Which companies does PIRI PIRI LYNGBYGG AS own?

PIRI PIRI LYNGBYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PIRI PIRI LYNGBYGG AS

Who owns PIRI PIRI LYNGBYGG AS?

MUSTAFA MUHAIMED MUSTAFA is the largest registered owner, with 50.0%.

What is the revenue of PIRI PIRI LYNGBYGG AS?

PIRI PIRI LYNGBYGG AS had revenue of NOK 1.4m in 2024.

Who is the general manager of PIRI PIRI LYNGBYGG AS?

Mustafa Muhaimed Mustafa is registered as general manager of PIRI PIRI LYNGBYGG AS.

Where is PIRI PIRI LYNGBYGG AS based?

PIRI PIRI LYNGBYGG AS has its business address in Lyngdal.

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.