BIZTRAC BETA
Retail sale of clothing

QOMO AS

Org. no. 815438302 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 9.2m
Operating profit NOK −759,000
Equity NOK −356,000
Incorporated 2015
Employees 7
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−356k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−759k kr).

QOMO AS is registered as a limited company in Oslo, Oslo with organisation number 815438302. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2015 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Salg av hovedsaklig klær og hva herved står i forbindelse. Selskapet kan også investere i aksjer/andeler i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.2m in revenue and NOK −759,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.2m
Operating profit
NOK −759,000
Equity
NOK −356,000

Financial health · 2024

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

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

Who owns QOMO AS?

SÆTHER-FREDRIKSEN INVEST AS
QOMO AS
NOK 9.2m rev. · NOK −759,000 profit

QOMO AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about QOMO AS

Who owns QOMO AS?

SÆTHER-FREDRIKSEN INVEST AS is the largest registered owner, with 59.0%.

What is the revenue of QOMO AS?

QOMO AS had revenue of NOK 9.2m in 2024.

Who is the general manager of QOMO AS?

Kaja Sæther is registered as general manager of QOMO AS.

Where is QOMO AS based?

QOMO 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.