BIZTRAC BETA
Rental and operating of own or leased real estate

ROBOTVEGEN 32 S11 AS

Org. no. 935784298 Limited company (AS) Time Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −73,000
Equity NOK −43,000
Incorporated 2025
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−43k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−73k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ROBOTVEGEN 32 S11 AS is registered as a limited company in Time, Rogaland with organisation number 935784298. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å eie, utvikle og leie ut fast eiendom, samt hva hermed står i forbindelse, herunder å delta i andre selskaper samt handel med aksjer og verdipapirer.”.

Key figures · 2025

Operating profit
NOK −73,000
Equity
NOK −43,000

Financial health · 2025

Liquidity
14.27
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-2.2%
Weak
Equity as a share of total capital

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

Who owns ROBOTVEGEN 32 S11 AS?

BRUMO AS
ROBOTVEGEN 32 S11 AS
· NOK −73,000 profit

ROBOTVEGEN 32 S11 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROBOTVEGEN 32 S11 AS

Who owns ROBOTVEGEN 32 S11 AS?

BRUMO AS is the largest registered owner, with 100.0%.

Who is the general manager of ROBOTVEGEN 32 S11 AS?

Terje Ree is registered as general manager of ROBOTVEGEN 32 S11 AS.

Where is ROBOTVEGEN 32 S11 AS based?

ROBOTVEGEN 32 S11 AS has its business address in Bryne.

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.