BIZTRAC BETA
Activities of excursion and event organisers

HOV LOFOTEN AS

Org. no. 992614307 Limited company (AS) Vågan Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 135,000
Operating profit NOK −6,000
Equity NOK 2.0m
Incorporated 2008
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−6k kr).

HOV LOFOTEN AS is registered as a limited company in Vågan, Nordland with organisation number 992614307. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å eie aksjer i eiendomsselskap, utvikle og selge eiendom, utvikle og tilby opplevelser innenfor reiseliv, og annen virksomhet som faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 135,000 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK 135,000
Operating profit
NOK −6,000
Equity
NOK 2.0m
Est. value
NOK 1.1m

Financial health · 2024

Liquidity
0.67
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
93.1%
Very good
Equity as a share of total capital

Who owns HOV LOFOTEN AS?

FRODE JAKOB HOV
HOV LOFOTEN AS
NOK 135,000 rev. · NOK −6,000 profit

HOV LOFOTEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HOV LOFOTEN AS own?

HOV LOFOTEN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HOV LOFOTEN AS

Who owns HOV LOFOTEN AS?

FRODE JAKOB HOV is the largest registered owner, with 100.0%.

What is the revenue of HOV LOFOTEN AS?

HOV LOFOTEN AS had revenue of NOK 135,000 in 2024.

Where is HOV LOFOTEN AS based?

HOV LOFOTEN AS has its business address in Gimsøysand.

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

Report a problem

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