BIZTRAC BETA
Computer programming activities

YETI MOVE AS

Org. no. 832138592 Limited company (AS) Drammen Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 16.0m
Operating profit NOK −1.4m
Equity NOK 11.4m
Incorporated 2023
Employees 14
Share capital NOK 1.3m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,4 mill kr).
  • Nylig endring 2026-06-15 Aksjekapital registrert 2026-06-15.

YETI MOVE AS is registered as a limited company in Drammen, Buskerud with organisation number 832138592. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2023 and has 14 registered employees. Registered share capital is NOK 1.3m, divided into 1251541 shares. The company's stated purpose is: “Utvikling, salg og levering av autonome systemer for snøbrøyting, og slike andre formål som selskapet kan utnytte slik teknologi kommersielt.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.0m in revenue and NOK −1.4m in operating profit.

Key figures · 2024

Revenue
NOK 16.0m
Operating profit
NOK −1.4m
Equity
NOK 11.4m
Est. value
NOK 32.0m

Financial health · 2024

Liquidity
2.24
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
73.8%
Very good
Equity as a share of total capital

Who owns YETI MOVE AS?

YETI INVEST AS
YETI MOVE AS
NOK 16.0m rev. · NOK −1.4m profit

YETI MOVE AS has 2 registered shareholders:

All shareholders and roles →

Group structure

YETI MOVE AS er morselskap for 2 datterselskaper:

Frequently asked questions about YETI MOVE AS

Who owns YETI MOVE AS?

YETI INVEST AS is the largest registered owner, with 90.8%.

What is the revenue of YETI MOVE AS?

YETI MOVE AS had revenue of NOK 16.0m in 2024.

Where is YETI MOVE AS based?

YETI MOVE AS has its business address in Drammen.

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.