BIZTRAC BETA
Marine fishing

LITLFLESA AS

Org. no. 914859387 Limited company (AS) Vågan Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 417,000
Operating profit NOK −87,000
Equity NOK −561,000
Incorporated 2015
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−561k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−87k kr).

LITLFLESA AS is registered as a limited company in Vågan, Nordland with organisation number 914859387. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Fiske og fangst, samt annen virksomhet som naturlig faller inn under dette, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 417,000 in revenue and NOK −87,000 in operating profit.

Key figures · 2025

Revenue
NOK 417,000
Operating profit
NOK −87,000
Equity
NOK −561,000

Financial health · 2025

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

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

Who owns LITLFLESA AS?

Finn Levi Stokvik
LITLFLESA AS
NOK 417,000 rev. · NOK −87,000 profit

LITLFLESA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LITLFLESA AS

Who owns LITLFLESA AS?

Finn Levi Stokvik is the largest registered owner, with 51.0%.

What is the revenue of LITLFLESA AS?

LITLFLESA AS had revenue of NOK 417,000 in 2025.

Who is the general manager of LITLFLESA AS?

Robert Ian Ormerod is registered as general manager of LITLFLESA AS.

Where is LITLFLESA AS based?

LITLFLESA AS has its business address in Henningsvær.

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.