BIZTRAC BETA
Rental and operating of own or leased real estate

GØS HOLDING AS

Org. no. 989052799 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 831,000
Operating profit NOK −102,000
Equity NOK 22.5m
Incorporated 2005
Share capital NOK 500,000

Signals

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

GØS HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 989052799. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Eie, utvikle og drive fast eiendom samt hva dermed står i forbindelse, herunder deltagelse i andre selskap og administrasjon av andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 831,000 in revenue and NOK −102,000 in operating profit.

Key figures · 2024

Revenue
NOK 831,000
Operating profit
NOK −102,000
Equity
NOK 22.5m
Est. value
NOK 17.2m

Financial health · 2024

Liquidity
32.75
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
99.0%
Very good
Equity as a share of total capital

Who owns GØS HOLDING AS?

KRISTIN ØSTLIE NILSEN
GØS HOLDING AS
NOK 831,000 rev. · NOK −102,000 profit

GØS HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does GØS HOLDING AS own?

GØS HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about GØS HOLDING AS

Who owns GØS HOLDING AS?

KRISTIN ØSTLIE NILSEN is the largest registered owner, with 90.0%.

What is the revenue of GØS HOLDING AS?

GØS HOLDING AS had revenue of NOK 831,000 in 2024.

Where is GØS HOLDING AS based?

GØS 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.