BIZTRAC BETA
Sports and recreation education

GOALIE ON ADVENTURE AS

Org. no. 929612698 Limited company (AS) Stavanger Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 205,000
Operating profit NOK 84,000
Equity NOK −113,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−113k kr).
  • Nylig endring 2026-04-17 Adresseendring registrert 2026-04-17.

GOALIE ON ADVENTURE AS is registered as a limited company in Stavanger, Rogaland with organisation number 929612698. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Import og salg av sportsartikler og klær på nett.”. The most recent filed accounts, for the 2024 financial year, show NOK 205,000 in revenue and NOK 84,000 in operating profit.

Key figures · 2024

Revenue
NOK 205,000
Operating profit
NOK 84,000
Equity
NOK −113,000
Est. value
NOK 443,000

Financial health · 2024

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

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

Who owns GOALIE ON ADVENTURE AS?

ANDERS KRISTIANSEN
GOALIE ON ADVENTURE AS
NOK 205,000 rev. · NOK 84,000 profit

GOALIE ON ADVENTURE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GOALIE ON ADVENTURE AS

Who owns GOALIE ON ADVENTURE AS?

ANDERS KRISTIANSEN is the largest registered owner, with 100.0%.

What is the revenue of GOALIE ON ADVENTURE AS?

GOALIE ON ADVENTURE AS had revenue of NOK 205,000 in 2024.

Where is GOALIE ON ADVENTURE AS based?

GOALIE ON ADVENTURE AS has its business address in Hundvåg.

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.