BIZTRAC BETA
Business and other management consultancy activities

ROBLO INVEST AS

Org. no. 812499262 Limited company (AS) Lillestrøm Incorporated 2013 Active
Ownership graph ↗
Operating profit NOK −52,000
Equity NOK −16.6m
Incorporated 2013
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−16,6 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−52k kr).

ROBLO INVEST AS is registered as a limited company in Lillestrøm, Akershus with organisation number 812499262. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investerings- og rådgivningsselskap, med dertil hørende virksomhet. Investeringene vil bestå av aksjer, eiendom og andre omsettelige verdipapirer.”.

Key figures · 2024

Operating profit
NOK −52,000
Equity
NOK −16.6m

Financial health · 2024

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-84.8%
Weak
Equity as a share of total capital

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

Who owns ROBLO INVEST AS?

RONNY BLOMSETH
ROBLO INVEST AS
· NOK −52,000 profit

ROBLO INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ROBLO INVEST AS own?

ROBLO INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ROBLO INVEST AS

Who owns ROBLO INVEST AS?

RONNY BLOMSETH is the largest registered owner, with 100.0%.

Who is the general manager of ROBLO INVEST AS?

Ronny Blomseth is registered as general manager of ROBLO INVEST AS.

Where is ROBLO INVEST AS based?

ROBLO INVEST AS has its business address in Lillestrøm.

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.