BIZTRAC BETA
Construction of residential and non-residential buildings

LIØYBYGG AS

Org. no. 913141431 Limited company (AS) Harstad Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 582,000
Operating profit NOK −1,000
Equity NOK −54,000
Incorporated 2013
Share capital NOK 100,000

Signals

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

LIØYBYGG AS is registered as a limited company in Harstad, Troms with organisation number 913141431. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2013. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Byggevirksomhet, salg av innredninger og byggevarer.”. The most recent filed accounts, for the 2025 financial year, show NOK 582,000 in revenue and NOK −1,000 in operating profit.

Key figures · 2025

Revenue
NOK 582,000
Operating profit
NOK −1,000
Equity
NOK −54,000

Financial health · 2025

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

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

Who owns LIØYBYGG AS?

JAN HELGE LINAKER
LIØYBYGG AS
NOK 582,000 rev. · NOK −1,000 profit

LIØYBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LIØYBYGG AS

Who owns LIØYBYGG AS?

JAN HELGE LINAKER is the largest registered owner, with 100.0%.

What is the revenue of LIØYBYGG AS?

LIØYBYGG AS had revenue of NOK 582,000 in 2025.

Who is the general manager of LIØYBYGG AS?

Jan Helge Linaker is registered as general manager of LIØYBYGG AS.

Where is LIØYBYGG AS based?

LIØYBYGG AS has its business address in Harstad.

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.