BIZTRAC BETA
Activities of financing conduits

GLOBAL EIENDOM UTBETALING NORGE 2007 AS

Org. no. 989026291 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −483,000
Equity NOK 10.2m
Incorporated 2005
Share capital NOK 644,000

Signals

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

GLOBAL EIENDOM UTBETALING NORGE 2007 AS is registered as a limited company in Oslo, Oslo with organisation number 989026291. The business is classified under activities of financing conduits (NACE 64.220). The company was incorporated in 2005. Registered share capital is NOK 644,000, divided into 64371154 shares. The company's stated purpose is: “Investere i, eie, drive og realisere fast eiendom, direkte eller indirekte gjennom deltakelse i andre selskaper, og alt som står i forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −483,000
Equity
NOK 10.2m
Est. value
NOK 13.7m

Financial health · 2024

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 GLOBAL EIENDOM UTBETALING NORGE 2007 AS?

AUDREY SCANDINAVIAN MIDCO
GLOBAL EIENDOM UTBETALING NORGE 2007 AS
· NOK −483,000 profit

GLOBAL EIENDOM UTBETALING NORGE 2007 AS has 3 registered shareholders:

All shareholders and roles →

Which companies does GLOBAL EIENDOM UTBETALING NORGE 2007 AS own?

GLOBAL EIENDOM UTBETALING NORGE 2007 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GLOBAL EIENDOM UTBETALING NORGE 2007 AS

Who owns GLOBAL EIENDOM UTBETALING NORGE 2007 AS?

AUDREY SCANDINAVIAN MIDCO is the largest registered owner, with 50.0%.

Where is GLOBAL EIENDOM UTBETALING NORGE 2007 AS based?

GLOBAL EIENDOM UTBETALING NORGE 2007 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.