BIZTRAC BETA
Retail sale of sports equipment

TURKONGEN AS

Org. no. 936706142 Limited company (AS) Kristiansand Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −3,000
Equity NOK 73,000
Incorporated 2025
Share capital NOK 83,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−3k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-11-06.

TURKONGEN AS is registered as a limited company in Kristiansand, Agder with organisation number 936706142. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2025. Registered share capital is NOK 83,000, divided into 30000 shares. The company's stated purpose is: “Nettbutikk med produkter innen friluftsliv, tur og fritid, med fokus på utstyr for utendørsbruk.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK 73,000
Est. value
NOK 92,000

Financial health · 2025

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

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

Who owns TURKONGEN AS?

ALEKSANDER EYE FÆRAVAAG
TURKONGEN AS
NOK 0 rev. · NOK −3,000 profit

TURKONGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TURKONGEN AS

Who owns TURKONGEN AS?

ALEKSANDER EYE FÆRAVAAG is the largest registered owner, with 100.0%.

What is the revenue of TURKONGEN AS?

TURKONGEN AS had revenue of NOK 0 in 2025.

Who is the general manager of TURKONGEN AS?

Aleksander Eye Færavaag is registered as general manager of TURKONGEN AS.

Where is TURKONGEN AS based?

TURKONGEN AS has its business address in Kristiansand S.

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.