BIZTRAC BETA
Wholesale of clothing and footwear

KLEO AS

Org. no. 983837476 Limited company (AS) Salangen Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 177,000
Equity NOK −857,000
Incorporated 2001
Employees 7
Share capital NOK 200,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−857k kr).

KLEO AS is registered as a limited company in Salangen, Troms with organisation number 983837476. The business is classified under wholesale of clothing and footwear (NACE 46.420). The company was incorporated in 2001 and has 7 registered employees. Registered share capital is NOK 200,000, divided into 200000 shares. The company's stated purpose is: “Manufakturforretning, kjøp og salg av klær samt det som står i forbindelse med dette. Selskapet skal også kunne delta i andre virksomheter med økonomisk formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 177,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK 177,000
Equity
NOK −857,000
Est. value
NOK 726,000

Financial health · 2025

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

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

Who owns KLEO AS?

SIMO INVEST AS
KLEO AS
NOK 2.1m rev. · NOK 177,000 profit

KLEO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KLEO AS

Who owns KLEO AS?

SIMO INVEST AS is the largest registered owner, with 75.0%.

What is the revenue of KLEO AS?

KLEO AS had revenue of NOK 2.1m in 2025.

Who is the general manager of KLEO AS?

Siv Renate Sæbø is registered as general manager of KLEO AS.

Where is KLEO AS based?

KLEO AS has its business address in Sjøvegan.

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.