BIZTRAC BETA
Manufacture of other fabricated metal products n.e.c.

SMARTSHIFT ROBOTICS AS

Org. no. 990833168 Limited company (AS) Ringerike Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 5.7m
Operating profit NOK −1.3m
Equity NOK 124,000
Incorporated 2007
Share capital NOK 169,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,3 mill kr).

SMARTSHIFT ROBOTICS AS is registered as a limited company in Ringerike, Buskerud with organisation number 990833168. The business is classified under manufacture of other fabricated metal products n.e.c. (NACE 25.990). The company was incorporated in 2007. Registered share capital is NOK 169,000, divided into 154 shares. The company's stated purpose is: “Vareproduksjon og handel og hva som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.7m in revenue and NOK −1.3m in operating profit.

Key figures · 2024

Revenue
NOK 5.7m
Operating profit
NOK −1.3m
Equity
NOK 124,000
Est. value
NOK 2.4m

Financial health · 2024

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

Who owns SMARTSHIFT ROBOTICS AS?

BUIND HOLDING AS
SMARTSHIFT ROBOTICS AS
NOK 5.7m rev. · NOK −1.3m profit

SMARTSHIFT ROBOTICS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SMARTSHIFT ROBOTICS AS

Who owns SMARTSHIFT ROBOTICS AS?

BUIND HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SMARTSHIFT ROBOTICS AS?

SMARTSHIFT ROBOTICS AS had revenue of NOK 5.7m in 2024.

Who is the general manager of SMARTSHIFT ROBOTICS AS?

Kjell Buind is registered as general manager of SMARTSHIFT ROBOTICS AS.

Where is SMARTSHIFT ROBOTICS AS based?

SMARTSHIFT ROBOTICS AS has its business address in Hønefoss.

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.