BIZTRAC BETA
Buying and selling of own real estate

GLOBAL HUS 2.0 AS

Org. no. 923032533 Limited company (AS) Stavanger Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 290,000
Equity NOK −745,000
Incorporated 2019
Share capital NOK 1.0m

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−745k kr).

GLOBAL HUS 2.0 AS is registered as a limited company in Stavanger, Rogaland with organisation number 923032533. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2019. Registered share capital is NOK 1.0m, divided into 100000 shares. The company's stated purpose is: “Kjøp, salg og utvikling av eiendom, investere i andre selskaper, herunder eie aksjer og andre finansielle instrumenter, driver handel med finansielle instrumenter og annen beslektet virksomhet, samt konsulenttjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 290,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 290,000
Equity
NOK −745,000
Est. value
NOK 2.2m

Financial health · 2024

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

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

Who owns GLOBAL HUS 2.0 AS?

SKORPEFJELL AS
GLOBAL HUS 2.0 AS
NOK 0 rev. · NOK 290,000 profit

GLOBAL HUS 2.0 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GLOBAL HUS 2.0 AS

Who owns GLOBAL HUS 2.0 AS?

SKORPEFJELL AS is the largest registered owner, with 100.0%.

What is the revenue of GLOBAL HUS 2.0 AS?

GLOBAL HUS 2.0 AS had revenue of NOK 0 in 2024.

Where is GLOBAL HUS 2.0 AS based?

GLOBAL HUS 2.0 AS has its business address in Hafrsfjord.

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.