BIZTRAC BETA
Retail sale of household articles and equipment n.e.c.

KEO HORTEN AS

Org. no. 923875182 Limited company (AS) Horten Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 14.7m
Operating profit NOK −842,000
Equity NOK −4.9m
Incorporated 2019
Share capital NOK 200,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−4,9 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−842k kr).

KEO HORTEN AS is registered as a limited company in Horten, Vestfold with organisation number 923875182. The business is classified under retail sale of household articles and equipment n.e.c. (NACE 47.559). The company was incorporated in 2019. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Kjøp og salg av interiørprodukter med vekt på kjøkken, bad og garderobeinnredninger. Videre skal selskapet kunne delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.7m in revenue and NOK −842,000 in operating profit.

Key figures · 2024

Revenue
NOK 14.7m
Operating profit
NOK −842,000
Equity
NOK −4.9m

Financial health · 2024

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

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

Who owns KEO HORTEN AS?

STORGATA EIENDOM AS
KEO HORTEN AS
NOK 14.7m rev. · NOK −842,000 profit

KEO HORTEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KEO HORTEN AS

Who owns KEO HORTEN AS?

STORGATA EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of KEO HORTEN AS?

KEO HORTEN AS had revenue of NOK 14.7m in 2024.

Where is KEO HORTEN AS based?

KEO HORTEN AS has its business address in Horten.

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.