BIZTRAC BETA
Restaurant activities

HEAVENLY AS

Org. no. 933671585 Limited company (AS) Lillestrøm Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 291,000
Operating profit NOK −41,000
Equity NOK −11,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−11k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−41k kr).

HEAVENLY AS is registered as a limited company in Lillestrøm, Akershus with organisation number 933671585. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Å drive en liten dessertrestaurant som tilbyr et bredt utvalg av desserter og søtsaker til kundene.”. The most recent filed accounts, for the 2024 financial year, show NOK 291,000 in revenue and NOK −41,000 in operating profit.

Key figures · 2024

Revenue
NOK 291,000
Operating profit
NOK −41,000
Equity
NOK −11,000

Financial health · 2024

Liquidity
11.50
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-9.5%
Weak
Equity as a share of total capital

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

Who owns HEAVENLY AS?

SULEMAN MUHAMMAD ABBAS
HEAVENLY AS
NOK 291,000 rev. · NOK −41,000 profit

HEAVENLY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HEAVENLY AS

Who owns HEAVENLY AS?

SULEMAN MUHAMMAD ABBAS is the largest registered owner, with 100.0%.

What is the revenue of HEAVENLY AS?

HEAVENLY AS had revenue of NOK 291,000 in 2024.

Who is the general manager of HEAVENLY AS?

Suleman Muhammad Abbas is registered as general manager of HEAVENLY AS.

Where is HEAVENLY AS based?

HEAVENLY AS has its business address in Strømmen.

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.