BIZTRAC BETA
Other real estate activities on a fee or contract basis

BELEGU HOLDING AS

Org. no. 918639144 Limited company (AS) Arendal Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −62,000
Equity NOK 90,000
Incorporated 2017
Share capital NOK 65,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−62k kr).

BELEGU HOLDING AS is registered as a limited company in Arendal, Agder with organisation number 918639144. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2017. Registered share capital is NOK 65,000, divided into 100 shares. The company's stated purpose is: “Investering og forvaltning, herunder eiendom, aksjehandel og verdipapirer, samt delta i andre selskaper ved aksjekjøp eller lignende. Vaktmestertjenester og alt som naturlig inngår i dette.”.

Key figures · 2024

Operating profit
NOK −62,000
Equity
NOK 90,000
Est. value
NOK 393,000

Financial health · 2024

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

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

Who owns BELEGU HOLDING AS?

SHPETIM BELEGU
BELEGU HOLDING AS
· NOK −62,000 profit

BELEGU HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BELEGU HOLDING AS own?

BELEGU HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about BELEGU HOLDING AS

Who owns BELEGU HOLDING AS?

SHPETIM BELEGU is the largest registered owner, with 100.0%.

Who is the general manager of BELEGU HOLDING AS?

Shpetim Belegu is registered as general manager of BELEGU HOLDING AS.

Where is BELEGU HOLDING AS based?

BELEGU HOLDING AS has its business address in Saltrød.

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.