biztrac. BETA
COMPANY REGISTER PROFILE
834012642 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

ROBO EIENDOM AS

Org. no. 834012642 Limited company (AS) Øygarden Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 306,000
Equity NOK 70,000
Incorporated 2024
Share capital NOK 30,000

ROBO EIENDOM AS is registered as a limited company in Øygarden, Vestland with organisation number 834012642. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i eiendom, herunder kjøp, salg og utleie.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 306,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 306,000
▲ +648 %
Equity
NOK 70,000
▲ +187 %
Est. value
NOK 486,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
15.4%
Very good
Return on total assets
Solidity
5.9%
Weak
Equity as a share of total capital

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

Who owns ROBO EIENDOM AS?

ROBO EIENDOM AS
NOK 1.2m rev. · NOK 306,000 profit

ROBO EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ROBO EIENDOM AS

Who owns ROBO EIENDOM AS?

TALR EIENDOM AS is the largest registered owner, with 50.0%.

What is the revenue of ROBO EIENDOM AS?

ROBO EIENDOM AS had revenue of NOK 1.2m in 2025.

Who is the general manager of ROBO EIENDOM AS?

Tony Andre Lyngøy Rong is registered as general manager of ROBO EIENDOM AS.

Where is ROBO EIENDOM AS based?

ROBO EIENDOM AS has its business address in Rong.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.