BIZTRAC BETA
Uoppgitt

RUBUS EIENDOM AS

Org. no. 930180580 Limited company (AS) Gjerdrum Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −12,000
Equity NOK 602,000
Incorporated 2022
Share capital NOK 300,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).

RUBUS EIENDOM AS is registered as a limited company in Gjerdrum, Akershus with organisation number 930180580. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 300,000, divided into 300000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte delta med kapital i ulike prosjekter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK 602,000
Est. value
NOK 474,000

Financial health · 2025

Liquidity
22.36
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
76.8%
Very good
Equity as a share of total capital

Who owns RUBUS EIENDOM AS?

PRO HOLDING AS
RUBUS EIENDOM AS
NOK 0 rev. · NOK −12,000 profit

RUBUS EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RUBUS EIENDOM AS

Who owns RUBUS EIENDOM AS?

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

What is the revenue of RUBUS EIENDOM AS?

RUBUS EIENDOM AS had revenue of NOK 0 in 2025.

Who is the general manager of RUBUS EIENDOM AS?

Robert Øksnes is registered as general manager of RUBUS EIENDOM AS.

Where is RUBUS EIENDOM AS based?

RUBUS EIENDOM AS has its business address in Gjerdrum.

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.