biztrac. BETA
COMPANY REGISTER PROFILE
919461438 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Marine fishing

LIEHOLMEN AS

Org. no. 919461438 Limited company (AS) Øygarden Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 8.2m
Operating profit NOK −1.3m
Equity NOK −7.3m
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−7,3 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,3 mill kr).

LIEHOLMEN AS is registered as a limited company in Øygarden, Vestland with organisation number 919461438. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Fiske og fangst, herunder eie og drive fiskefartøy, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.2m in revenue and NOK −1.3m in operating profit.

Key figures · 2025

Revenue
NOK 8.2m
▲ +166 %
Operating profit
NOK −1.3m
▲ +59 %
Equity
NOK −7.3m
▼ −47 %

Financial health · 2025

Liquidity
0.80
Weak
Current assets ÷ current liabilities
Profitability
-5.1%
Not satisfactory
Return on total assets
Solidity
-23.0%
Weak
Equity as a share of total capital

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

Who owns LIEHOLMEN AS?

LIEHOLMEN AS has 9 registered shareholders:

All shareholders and roles →

Frequently asked questions about LIEHOLMEN AS

Who owns LIEHOLMEN AS?

LARSTEIN AS is the largest registered owner, with 48.0%.

What is the revenue of LIEHOLMEN AS?

LIEHOLMEN AS had revenue of NOK 8.2m in 2025.

Who is the general manager of LIEHOLMEN AS?

Anders Lie Skålevik is registered as general manager of LIEHOLMEN AS.

Where is LIEHOLMEN AS based?

LIEHOLMEN AS has its business address in Straume.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.