BIZTRAC BETA
COMPANY REGISTER PROFILE
829452642 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Restaurant activities

LULU SADAF RESTAURANT AS

Org. no. 829452642 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −23,000
Equity NOK 7,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−23k kr).

LULU SADAF RESTAURANT AS is registered as a limited company in Oslo, Oslo with organisation number 829452642. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Restaurant og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −23,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −23,000
Equity
NOK 7,000
Est. value
NOK 9,000

Financial health · 2025

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

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

Who owns LULU SADAF RESTAURANT AS?

No shareholders are registered for LULU SADAF RESTAURANT AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about LULU SADAF RESTAURANT AS

What is the revenue of LULU SADAF RESTAURANT AS?

LULU SADAF RESTAURANT AS had revenue of NOK 0 in 2025.

Who is the general manager of LULU SADAF RESTAURANT AS?

Loay Rahim Jasim Al Husseini is registered as general manager of LULU SADAF RESTAURANT AS.

Where is LULU SADAF RESTAURANT AS based?

LULU SADAF RESTAURANT AS has its business address in Oslo.

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.