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

SAGAHOLDING AS

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

Signals

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

SAGAHOLDING AS is registered as a limited company in Nordreisa, Troms with organisation number 936197213. 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 30000 shares. The company's stated purpose is: “Tilby administrativ bedriftsrådgivning og konsulenttjenester, inkludert, men ikke begrenset til, forretningsplanlegging, strategi, organisasjonsutvikling, personalledelse og effektivisering av arbeidsprosesser.”.

Who owns SAGAHOLDING AS?

SAGAHOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SAGAHOLDING AS own?

SAGAHOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SAGAHOLDING AS

Who owns SAGAHOLDING AS?

HENRIK ANDRE LUND HENRIKSEN is the largest registered owner, with 100.0%.

Who is the general manager of SAGAHOLDING AS?

Henrik Andre Lund Henriksen is registered as general manager of SAGAHOLDING AS.

Where is SAGAHOLDING AS based?

SAGAHOLDING AS has its business address in Storslett.

Property

Business address Mælen 13, 9151 Storslett
Cadastral unit 5544-13/162/0/0
Building Enebolig · 1 unit

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.