BIZTRAC BETA
COMPANY REGISTER PROFILE
915056687 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Activities of excursion and event organisers

GOLOFOTEN AS

Org. no. 915056687 Limited company (AS) Moskenes Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 24,000
Operating profit NOK 4,000
Equity NOK −59,000
Incorporated 2015
Share capital NOK 50,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−59k kr).

GOLOFOTEN AS is registered as a limited company in Moskenes, Nordland with organisation number 915056687. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2015. Registered share capital is NOK 50,000, divided into 500 shares. The company's stated purpose is: “Reiseliv og fritidsaktiviteter, opplevelser, guiding, og reiseledervirksomhet”. The most recent filed accounts, for the 2025 financial year, show NOK 24,000 in revenue and NOK 4,000 in operating profit.

Key figures · 2025

Revenue
NOK 24,000
Operating profit
NOK 4,000
▲ +124 %
Equity
NOK −59,000
▲ +7 %

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
0.8%
Not satisfactory
Return on total assets
Solidity
-10.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns GOLOFOTEN AS?

GOLOFOTEN AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about GOLOFOTEN AS

Who owns GOLOFOTEN AS?

TORBJØRN TORSKE PROSJEKTUTVIKLING AS is the largest registered owner, with 39.4%.

What is the revenue of GOLOFOTEN AS?

GOLOFOTEN AS had revenue of NOK 24,000 in 2025.

Who is the general manager of GOLOFOTEN AS?

Eirik Bræin Gikling is registered as general manager of GOLOFOTEN AS.

Where is GOLOFOTEN AS based?

GOLOFOTEN AS has its business address in Reine.

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.