BIZTRAC BETA
Sports activities n.e.c.

KARSTEN GEFLE AS

Org. no. 998821215 Limited company (AS) Ålesund Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −8,000
Equity NOK 80,000
Incorporated 2012
Share capital NOK 30,000

Signals

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

KARSTEN GEFLE AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 998821215. The business is classified under sports activities n.e.c. (NACE 93.190). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Profesjonell skikjøring, konsulenttjenester i forbindelse med hotelldrift, markedsføring og aktiviteter samt planlegging og gjennomføring av disse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 80,000
Est. value
NOK 100,000

Financial health · 2024

Liquidity
0.73
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
35.2%
Weak
Equity as a share of total capital

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

Who owns KARSTEN GEFLE AS?

KARSTEN GEFLE
KARSTEN GEFLE AS
NOK 0 rev. · NOK −8,000 profit

KARSTEN GEFLE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KARSTEN GEFLE AS own?

KARSTEN GEFLE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KARSTEN GEFLE AS

Who owns KARSTEN GEFLE AS?

KARSTEN GEFLE is the largest registered owner, with 100.0%.

What is the revenue of KARSTEN GEFLE AS?

KARSTEN GEFLE AS had revenue of NOK 0 in 2024.

Where is KARSTEN GEFLE AS based?

KARSTEN GEFLE AS has its business address in Ålesund.

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.