BIZTRAC BETA
Business and other management consultancy activities

RUBI PROSJEKTLEDELSE AS

Org. no. 914566320 Limited company (AS) Bærum Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −171,000
Equity NOK 9.5m
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−171k kr).

RUBI PROSJEKTLEDELSE AS is registered as a limited company in Bærum, Akershus with organisation number 914566320. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Konsulenttjenester innen prosjektledelse, økonomi og administrasjon. I tillegg investerer selskapet i aksjer og andre finansielle instrumenter herunder deltagelse i andre selskaper.”.

Key figures · 2024

Operating profit
NOK −171,000
Equity
NOK 9.5m
Est. value
NOK 18.0m

Financial health · 2024

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

Who owns RUBI PROSJEKTLEDELSE AS?

PAUL TORGERSEN
RUBI PROSJEKTLEDELSE AS
· NOK −171,000 profit

RUBI PROSJEKTLEDELSE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does RUBI PROSJEKTLEDELSE AS own?

RUBI PROSJEKTLEDELSE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about RUBI PROSJEKTLEDELSE AS

Who owns RUBI PROSJEKTLEDELSE AS?

PAUL TORGERSEN is the largest registered owner, with 50.0%.

Who is the general manager of RUBI PROSJEKTLEDELSE AS?

Paul Torgersen is registered as general manager of RUBI PROSJEKTLEDELSE AS.

Where is RUBI PROSJEKTLEDELSE AS based?

RUBI PROSJEKTLEDELSE AS has its business address in Vøyenenga.

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.