BIZTRAC BETA
Wholesale of information and communication equipment

ROBINROBOT AS

Org. no. 928624919 Limited company (AS) Nesodden Incorporated 2022 Active
Ownership graph ↗
Revenue 2023 NOK 0
Operating profit NOK −18,000
Equity NOK 170,000
Incorporated 2022
Share capital NOK 500,000

Signals

2 flags
  • Driftsunderskudd 2023 Siste driftsresultat er negativt (−18k kr).
  • Utdatert regnskap Siste registrerte regnskap er fra 2023.

ROBINROBOT AS is registered as a limited company in Nesodden, Akershus with organisation number 928624919. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 2022. Registered share capital is NOK 500,000, divided into 500000 shares. The company's stated purpose is: “Selge varer og tjenester innen datautstyr og utleie av datautstyr og annet som naturlig sammenfaller med dette samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2023 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2023

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK 170,000
Est. value
NOK 212,000

Financial health · 2023

Liquidity
-4.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
116.2%
Very good
Equity as a share of total capital

Who owns ROBINROBOT AS?

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

Frequently asked questions about ROBINROBOT AS

What is the revenue of ROBINROBOT AS?

ROBINROBOT AS had revenue of NOK 0 in 2023.

Who is the general manager of ROBINROBOT AS?

Robin Heder is registered as general manager of ROBINROBOT AS.

Where is ROBINROBOT AS based?

ROBINROBOT AS has its business address in Fjellstrand.

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.