BIZTRAC BETA
Camping grounds and recreational vehicle parks

LAUKVIK FISKECAMP AS

Org. no. 912100243 Limited company (AS) Senja Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 4.1m
Operating profit NOK 854,000
Equity NOK 3.7m
Incorporated 2013
Share capital NOK 600,000

LAUKVIK FISKECAMP AS is registered as a limited company in Senja, Troms with organisation number 912100243. The business is classified under camping grounds and recreational vehicle parks (NACE 55.300). The company was incorporated in 2013. Registered share capital is NOK 600,000, divided into 800 shares. The company's stated purpose is: “Drift av fiskecamp med utleie av hytter, båter og næringslokaler. Selskapet skal i tillegg kunne delta i investeringer, også kunne delta i andre selskap med tilsvarende virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.1m in revenue and NOK 854,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.1m
Operating profit
NOK 854,000
Equity
NOK 3.7m
Est. value
NOK 4.6m

Financial health · 2025

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

Who owns LAUKVIK FISKECAMP AS?

EIVIND NILSEN
LAUKVIK FISKECAMP AS
NOK 4.1m rev. · NOK 854,000 profit

LAUKVIK FISKECAMP AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LAUKVIK FISKECAMP AS

Who owns LAUKVIK FISKECAMP AS?

EIVIND NILSEN is the largest registered owner, with 85.0%.

What is the revenue of LAUKVIK FISKECAMP AS?

LAUKVIK FISKECAMP AS had revenue of NOK 4.1m in 2025.

Who is the general manager of LAUKVIK FISKECAMP AS?

Eivind Nilsen is registered as general manager of LAUKVIK FISKECAMP AS.

Where is LAUKVIK FISKECAMP AS based?

LAUKVIK FISKECAMP AS has its business address in Botnhamn.

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.