BIZTRAC BETA
COMPANY REGISTER PROFILE
936117228 ORG. NO. 8 SECTIONS
Active UPDATED 02.09.2026
Scheduled long distance passenger transport in coastal waters

HAVILA PHOENIX OPERATION AS

Org. no. 936117228 Limited company (AS) Herøy Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.

HAVILA PHOENIX OPERATION AS is registered as a limited company in Herøy, Møre og Romsdal with organisation number 936117228. The business is classified under scheduled long distance passenger transport in coastal waters (NACE 50.102). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie og drift av skip og alt som står i forbindelse med det.”.

Former names: NFH 250824 AS

Who owns HAVILA PHOENIX OPERATION AS?

HAVILA PHOENIX OPERATION AS

HAVILA PHOENIX OPERATION AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAVILA PHOENIX OPERATION AS

Who owns HAVILA PHOENIX OPERATION AS?

HAVILA SUBSEA & RENEWABLES AS is the largest registered owner, with 100.0%.

Where is HAVILA PHOENIX OPERATION AS based?

HAVILA PHOENIX OPERATION AS has its business address in Fosnavåg.

Property

Business address Mjølstadnesvegen 24, 6092 Fosnavåg
Cadastral unit 1515-22/59/0/0
Building Kontor- og administrasjonsbygning, rådhus · 1 unit

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