BIZTRAC BETA
Visual arts creation activities

DISCOVER LOFOTEN AS

Org. no. 920829309 Limited company (AS) Vågan Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 670,000
Equity NOK 512,000
Incorporated 2018
Share capital NOK 45,000

DISCOVER LOFOTEN AS is registered as a limited company in Vågan, Nordland with organisation number 920829309. The business is classified under visual arts creation activities (NACE 90.120). The company was incorporated in 2018. Registered share capital is NOK 45,000, divided into 1000 shares. The company's stated purpose is: “Drive hovedsakelig med kunst, foto og guiding samt utstilling. Guiding, opplæring og workshop i felten samt opplæring på lightroom. Haveørn safari, natursafari med Båt til et annet selskap, buss eller minibuss”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 670,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 670,000
Equity
NOK 512,000
Est. value
NOK 2.2m

Financial health · 2024

Liquidity
7.12
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.5%
Good
Equity as a share of total capital

Who owns DISCOVER LOFOTEN AS?

ODD-PETTER TANKE JENSEN
DISCOVER LOFOTEN AS
NOK 1.8m rev. · NOK 670,000 profit

DISCOVER LOFOTEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DISCOVER LOFOTEN AS

Who owns DISCOVER LOFOTEN AS?

ODD-PETTER TANKE JENSEN is the largest registered owner, with 100.0%.

What is the revenue of DISCOVER LOFOTEN AS?

DISCOVER LOFOTEN AS had revenue of NOK 1.8m in 2024.

Who is the general manager of DISCOVER LOFOTEN AS?

Odd-Petter Tanke Jensen is registered as general manager of DISCOVER LOFOTEN AS.

Where is DISCOVER LOFOTEN AS based?

DISCOVER LOFOTEN AS has its business address in Kabelvåg.

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.