BIZTRAC BETA
Restaurant activities

THE CROWN AS

Org. no. 921535856 Limited company (AS) Ringsaker Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 4.5m
Operating profit NOK −275,000
Equity NOK −1.5m
Incorporated 2018
Employees 14
Share capital NOK 300,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,5 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−275k kr).

THE CROWN AS is registered as a limited company in Ringsaker, Innlandet with organisation number 921535856. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2018 and has 14 registered employees. Registered share capital is NOK 300,000, divided into 300000 shares. The company's stated purpose is: “Drive restaurant.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.5m in revenue and NOK −275,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.5m
Operating profit
NOK −275,000
Equity
NOK −1.5m

Financial health · 2025

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

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

Who owns THE CROWN AS?

MOHAMED TAFECH AHMAD ABU-AL-ULA
THE CROWN AS
NOK 4.5m rev. · NOK −275,000 profit

THE CROWN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about THE CROWN AS

Who owns THE CROWN AS?

MOHAMED TAFECH AHMAD ABU-AL-ULA is the largest registered owner, with 70.0%.

What is the revenue of THE CROWN AS?

THE CROWN AS had revenue of NOK 4.5m in 2025.

Who is the general manager of THE CROWN AS?

Hanan Tafish Abu-Al-Ula is registered as general manager of THE CROWN AS.

Where is THE CROWN AS based?

THE CROWN AS has its business address in Moelv.

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.