BIZTRAC BETA
COMPANY REGISTER PROFILE
936117236 ORG. NO. 8 SECTIONS
Active UPDATED 02.09.2026
Business and other management consultancy activities

RIFT MANAGEMENT AS

Org. no. 936117236 Limited company (AS) Stavanger Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.

RIFT MANAGEMENT AS is registered as a limited company in Stavanger, Rogaland with organisation number 936117236. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Salg av konsulenttjenester knyttet til management-ekspertise og prosjektledelse.”.

Former names: NFH 250825 AS

Who owns RIFT MANAGEMENT AS?

RIFT MANAGEMENT AS has 3 registered shareholders:

All shareholders and roles →

Which companies does RIFT MANAGEMENT AS own?

RIFT MANAGEMENT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RIFT MANAGEMENT AS

Who owns RIFT MANAGEMENT AS?

SKAULEN AS is the largest registered owner, with 33.3%.

Who is the general manager of RIFT MANAGEMENT AS?

Andre Ølberg is registered as general manager of RIFT MANAGEMENT AS.

Where is RIFT MANAGEMENT AS based?

RIFT MANAGEMENT AS has its business address in Stavanger.

Property

Business address Frida Hansens vei 5, 4016 Stavanger
Cadastral unit 1103-22/38/0/0
Building Annet kulturhus · 1 unit

63 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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