BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

YUMS AS

Org. no. 931714023 Limited company (AS) Horten Incorporated 2023 Active
Ownership graph ↗
Revenue 2023 NOK 1.1m
Operating profit NOK −49,000
Equity NOK 5,000
Incorporated 2023
Share capital NOK 60,000

Signals

3 flags
  • Driftsunderskudd 2023 Siste driftsresultat er negativt (−49k kr).
  • Utdatert regnskap Siste registrerte regnskap er fra 2023.
  • Nylig endring 2026-06-23 Under avvikling registrert 2026-06-23.

YUMS AS is registered as a limited company in Horten, Vestfold with organisation number 931714023. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2023. Registered share capital is NOK 60,000, divided into 60000 shares. The company's stated purpose is: “Nettbutikk med fysiske butikker av kioskvarer som godteri, snacks og drikke.”. The most recent filed accounts, for the 2023 financial year, show NOK 1.1m in revenue and NOK −49,000 in operating profit.

Key figures · 2023

Revenue
NOK 1.1m
Operating profit
NOK −49,000
Equity
NOK 5,000
Est. value
NOK 350,000

Financial health · 2023

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

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

Who owns YUMS AS?

No shareholders are registered for YUMS AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about YUMS AS

What is the revenue of YUMS AS?

YUMS AS had revenue of NOK 1.1m in 2023.

Who is the general manager of YUMS AS?

Jesper Christian Utter Ronander is registered as general manager of YUMS AS.

Where is YUMS AS based?

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