biztrac. BETA
COMPANY REGISTER PROFILE
921057911 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 03.10.2026
⚠KEN TALLEST AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Other non-specialised retail sale

KEN TALLEST AS

Org. no. 921057911 Limited company (AS) Oslo Incorporated 2018 In liquidation
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 29,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

KEN TALLEST AS is registered as a limited company in Oslo, Oslo with organisation number 921057911. The business is classified under other non-specialised retail sale (NACE 47.120). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Salg av klær og andre varer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK 0
▲ +100 %
Equity
NOK 29,000
▲ +0 %

Financial health · 2025

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

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

Who owns KEN TALLEST AS?

KEN TALLEST AS has 2 registered shareholders:

The company is not in the Tax Administration's shareholder register for 2025. The list shows the owners at the end of 2024.

All shareholders and roles →

Frequently asked questions about KEN TALLEST AS

Who owns KEN TALLEST AS?

Kenneth Ikechukwu Odumegwu is the largest registered owner, with 50.0%.

What is the revenue of KEN TALLEST AS?

KEN TALLEST AS had revenue of NOK 0 in 2025.

Where is KEN TALLEST AS based?

KEN TALLEST 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.