BIZTRAC BETA
COMPANY REGISTER PROFILE
834844362 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

HR THRIVE INVEST AS

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

Signals

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

HR THRIVE INVEST AS is registered as a limited company in Øygarden, Vestland with organisation number 834844362. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 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 gjøre seg interessert i andre foretagende.”.

Who owns HR THRIVE INVEST AS?

HR THRIVE INVEST AS

HR THRIVE INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HR THRIVE INVEST AS own?

HR THRIVE INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HR THRIVE INVEST AS

Who owns HR THRIVE INVEST AS?

HEINE ROTNEIM is the largest registered owner, with 100.0%.

Who is the general manager of HR THRIVE INVEST AS?

Heine Rotneim is registered as general manager of HR THRIVE INVEST AS.

Where is HR THRIVE INVEST AS based?

HR THRIVE INVEST AS has its business address in Knarrevik.

Property

Business address Søre Knappen 24, 5355 Knarrevik
Cadastral unit 4626-39/248/0/0
Building Enebolig · 2 units

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.