biztrac. BETA
COMPANY REGISTER PROFILE
934606035 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

ALSHAB AS

Org. no. 934606035 Limited company (AS) Kongsvinger Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −1,000
Equity NOK 595,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1k kr).
  • Nylig endring 2026-06-28 Adresseendring registrert 2026-06-28.

ALSHAB AS is registered as a limited company in Kongsvinger, Innlandet with organisation number 934606035. 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 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −1,000
▲ +77 %
Equity
NOK 595,000
▲ +2356 %
Est. value
NOK 5.3m

Financial health · 2025

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

Who owns ALSHAB AS?

ALSHAB AS
· NOK −1,000 profit

ALSHAB AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ALSHAB AS own?

ALSHAB AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ALSHAB AS

Who owns ALSHAB AS?

Alloush Alshab is the largest registered owner, with 100.0%.

Who is the general manager of ALSHAB AS?

Alloush Alshab is registered as general manager of ALSHAB AS.

Where is ALSHAB AS based?

ALSHAB AS has its business address in Kongsvinger.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.