BIZTRAC BETA
Retail sale of motor vehicle parts and accessories

CUSTOM TURKEY PERFORMANCE AS

Org. no. 921136706 Limited company (AS) Asker Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 40,000
Operating profit NOK 28,000
Equity NOK 4,000
Incorporated 2018
Share capital NOK 30,000

CUSTOM TURKEY PERFORMANCE AS is registered as a limited company in Asker, Akershus with organisation number 921136706. The business is classified under retail sale of motor vehicle parts and accessories (NACE 47.820). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 600 shares. The company's stated purpose is: “Nettbutikk.”. The most recent filed accounts, for the 2025 financial year, show NOK 40,000 in revenue and NOK 28,000 in operating profit.

Key figures · 2025

Revenue
NOK 40,000
Operating profit
NOK 28,000
Equity
NOK 4,000
Est. value
NOK 95,000

Financial health · 2024

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

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

Who owns CUSTOM TURKEY PERFORMANCE AS?

NICOLAI HORN
CUSTOM TURKEY PERFORMANCE AS
NOK 40,000 rev. · NOK 28,000 profit

CUSTOM TURKEY PERFORMANCE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CUSTOM TURKEY PERFORMANCE AS own?

CUSTOM TURKEY PERFORMANCE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CUSTOM TURKEY PERFORMANCE AS

Who owns CUSTOM TURKEY PERFORMANCE AS?

NICOLAI HORN is the largest registered owner, with 100.0%.

What is the revenue of CUSTOM TURKEY PERFORMANCE AS?

CUSTOM TURKEY PERFORMANCE AS had revenue of NOK 40,000 in 2025.

Where is CUSTOM TURKEY PERFORMANCE AS based?

CUSTOM TURKEY PERFORMANCE AS has its business address in Asker.

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.