BIZTRAC BETA
COMPANY REGISTER PROFILE
922187290 ORG. NO. 8 SECTIONS
Active UPDATED 02.09.2026
Other activities of other membership organisations

RYGGMARGSBROKK- OG HYDROCEPHALUSFORENINGEN, FYLKESLAG FOR ROGALAND (RH ROGALAND)

Org. no. 922187290 Association/club/organisation (FLI) Stavanger Incorporated 1995 Active
Ownership graph ↗
Incorporated 1995

RYGGMARGSBROKK- OG HYDROCEPHALUSFORENINGEN, FYLKESLAG FOR ROGALAND (RH ROGALAND) is registered as a association/club/organisation in Stavanger, Rogaland with organisation number 922187290. The business is classified under other activities of other membership organisations (NACE 94.992). The company was incorporated in 1995.

Former names: RYGGMARGSBROKK OG HYDROCEPHALUSFORENINGEN, FYLKESLAG ROGALAND OG AGDER. (ROAG)

Who owns RYGGMARGSBROKK- OG HYDROCEPHALUSFORENINGEN, FYLKESLAG FOR ROGALAND (RH ROGALAND)?

No shareholders are registered for RYGGMARGSBROKK- OG HYDROCEPHALUSFORENINGEN, FYLKESLAG FOR ROGALAND (RH ROGALAND) in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about RYGGMARGSBROKK- OG HYDROCEPHALUSFORENINGEN, FYLKESLAG FOR ROGALAND (RH ROGALAND)

Where is RYGGMARGSBROKK- OG HYDROCEPHALUSFORENINGEN, FYLKESLAG FOR ROGALAND (RH ROGALAND) based?

RYGGMARGSBROKK- OG HYDROCEPHALUSFORENINGEN, FYLKESLAG FOR ROGALAND (RH ROGALAND) has its business address in Stavanger.

Property

Business address c/o Marianne Gausel Ravnøy Valheimveien 25, 4020 Stavanger
Cadastral unit 1103-16/1616/0/0
Building Stort frittliggende boligbygg på 5 etg el mer · 17 units

5 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.