BIZTRAC BETA
Marine fishing

NORD-LENANGEN KYSTREKER AS

Org. no. 919472189 Limited company (AS) Lyngen Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 7.8m
Operating profit NOK −302,000
Equity NOK 214,000
Incorporated 2017
Share capital NOK 1.0m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−302k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

NORD-LENANGEN KYSTREKER AS is registered as a limited company in Lyngen, Troms with organisation number 919472189. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2017. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Å eie og drive fiske, fiskefartøy, samt delta i andre selskaper med økonomisk formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.8m in revenue and NOK −302,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.8m
Operating profit
NOK −302,000
Equity
NOK 214,000
Est. value
NOK 3.8m

Financial health · 2024

Liquidity
0.69
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.1%
Weak
Equity as a share of total capital

Who owns NORD-LENANGEN KYSTREKER AS?

LYNGEN REKER AS
NORD-LENANGEN KYSTREKER AS
NOK 7.8m rev. · NOK −302,000 profit

NORD-LENANGEN KYSTREKER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORD-LENANGEN KYSTREKER AS

Who owns NORD-LENANGEN KYSTREKER AS?

LYNGEN REKER AS is the largest registered owner, with 100.0%.

What is the revenue of NORD-LENANGEN KYSTREKER AS?

NORD-LENANGEN KYSTREKER AS had revenue of NOK 7.8m in 2024.

Where is NORD-LENANGEN KYSTREKER AS based?

NORD-LENANGEN KYSTREKER AS has its business address in Svensby.

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.