BIZTRAC BETA
Development of building projects

STABU HOLDING AS

Org. no. 913642880 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −4,000
Equity NOK 38,000
Incorporated 2014
Share capital NOK 30,000

Signals

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

STABU HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 913642880. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investere i andre selskaper gjennom aksjer, andeler eller på annen måte, samt hva derved står i sammenheng. Selskapet skal også kunne kjøpe investering, utleie og salg av eiendommer samt investere i akjser og selskaper. Selskapet skal også kunne drive konsulentvirksomhet.”.

Key figures · 2025

Operating profit
NOK −4,000
Equity
NOK 38,000
Est. value
NOK 35,000

Financial health · 2025

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

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

Who owns STABU HOLDING AS?

TONY STABU
STABU HOLDING AS
· NOK −4,000 profit

STABU HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STABU HOLDING AS own?

STABU HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STABU HOLDING AS

Who owns STABU HOLDING AS?

TONY STABU is the largest registered owner, with 100.0%.

Who is the general manager of STABU HOLDING AS?

Tony Stabu is registered as general manager of STABU HOLDING AS.

Where is STABU HOLDING AS based?

STABU HOLDING 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.