BIZTRAC BETA
Operation of marine fish farms

LANGNES LAKS AS

Org. no. 923403639 Limited company (AS) Alta Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 125,000
Operating profit NOK 851,000
Equity NOK 8.2m
Incorporated 2019
Share capital NOK 1.1m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LANGNES LAKS AS is registered as a limited company in Alta, Finnmark with organisation number 923403639. The business is classified under operation of marine fish farms (NACE 03.211). The company was incorporated in 2019. Registered share capital is NOK 1.1m, divided into 1104314 shares. The company's stated purpose is: “Drive landbasert oppdrett av fisk og annet som naturlig faller sammen med dette, herunder delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender samt salg av konsulenttjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 125,000 in revenue and NOK 851,000 in operating profit.

Key figures · 2025

Revenue
NOK 125,000
Operating profit
NOK 851,000
Equity
NOK 8.2m
Est. value
NOK 5.6m

Financial health · 2025

Liquidity
0.07
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.3%
Good
Equity as a share of total capital

Who owns LANGNES LAKS AS?

LBA AS
LANGNES LAKS AS
NOK 125,000 rev. · NOK 851,000 profit

LANGNES LAKS AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about LANGNES LAKS AS

Who owns LANGNES LAKS AS?

LBA AS is the largest registered owner, with 94.2%.

What is the revenue of LANGNES LAKS AS?

LANGNES LAKS AS had revenue of NOK 125,000 in 2025.

Where is LANGNES LAKS AS based?

LANGNES LAKS AS has its business address in Alta.

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.