BIZTRAC BETA
Retail sale of cultural and recreational goods n.e.c.

KONG TIKI RECORDS AS

Org. no. 986500995 Limited company (AS) Oslo Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 26,000
Operating profit NOK −20,000
Equity NOK −1.2m
Incorporated 2004
Share capital NOK 300,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,2 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−20k kr).

KONG TIKI RECORDS AS is registered as a limited company in Oslo, Oslo with organisation number 986500995. The business is classified under retail sale of cultural and recreational goods n.e.c. (NACE 47.690). The company was incorporated in 2004. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Handel og distribusjonsviskomhet samt annen virksomhet i tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 26,000 in revenue and NOK −20,000 in operating profit.

Key figures · 2025

Revenue
NOK 26,000
Operating profit
NOK −20,000
Equity
NOK −1.2m

Financial health · 2025

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

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

Who owns KONG TIKI RECORDS AS?

JENS-PETTER WIIG
KONG TIKI RECORDS AS
NOK 26,000 rev. · NOK −20,000 profit

KONG TIKI RECORDS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KONG TIKI RECORDS AS

Who owns KONG TIKI RECORDS AS?

JENS-PETTER WIIG is the largest registered owner, with 50.0%.

What is the revenue of KONG TIKI RECORDS AS?

KONG TIKI RECORDS AS had revenue of NOK 26,000 in 2025.

Where is KONG TIKI RECORDS AS based?

KONG TIKI RECORDS 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.