BIZTRAC BETA
Rental and operating of own or leased real estate

UBUNTU HOLDING AS

Org. no. 892700192 Limited company (AS) Østre Toten Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 152,000
Operating profit NOK 17,000
Equity NOK −3.7m
Incorporated 2008
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−3,7 mill kr).

UBUNTU HOLDING AS is registered as a limited company in Østre Toten, Innlandet with organisation number 892700192. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Investeringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 152,000 in revenue and NOK 17,000 in operating profit.

Key figures · 2024

Revenue
NOK 152,000
Operating profit
NOK 17,000
Equity
NOK −3.7m
Est. value
NOK 179,000

Financial health · 2024

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

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

Who owns UBUNTU HOLDING AS?

HANNE STØEN
UBUNTU HOLDING AS
NOK 152,000 rev. · NOK 17,000 profit

UBUNTU HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about UBUNTU HOLDING AS

Who owns UBUNTU HOLDING AS?

HANNE STØEN is the largest registered owner, with 50.0%.

What is the revenue of UBUNTU HOLDING AS?

UBUNTU HOLDING AS had revenue of NOK 152,000 in 2024.

Who is the general manager of UBUNTU HOLDING AS?

Frank Jørgen Vangen is registered as general manager of UBUNTU HOLDING AS.

Where is UBUNTU HOLDING AS based?

UBUNTU HOLDING AS has its business address in Kapp.

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.