BIZTRAC BETA
Wholesale of wood, construction materials and sanitary equipment

LIA HOLDING AS

Org. no. 988903361 Limited company (AS) Porsgrunn Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −31,000
Equity NOK 4.0m
Incorporated 2005
Share capital NOK 2.5m

Signals

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

LIA HOLDING AS is registered as a limited company in Porsgrunn, Telemark with organisation number 988903361. The business is classified under wholesale of wood, construction materials and sanitary equipment (NACE 46.830). The company was incorporated in 2005. Registered share capital is NOK 2.5m, divided into 2500 shares. The company's stated purpose is: “Konsulentvirksomhet, deltakelse i andre selskaper, generell investeringsvirksomhet, herunder handel med verdipapirer, investering i selskaper, eiendom og aktiva.”.

Key figures · 2024

Operating profit
NOK −31,000
Equity
NOK 4.0m
Est. value
NOK 12.8m

Financial health · 2024

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

Who owns LIA HOLDING AS?

ODDBJØRN LIA
LIA HOLDING AS
· NOK −31,000 profit

LIA HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LIA HOLDING AS own?

LIA HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LIA HOLDING AS

Who owns LIA HOLDING AS?

ODDBJØRN LIA is the largest registered owner, with 80.0%.

Who is the general manager of LIA HOLDING AS?

Oddbjørn Lia is registered as general manager of LIA HOLDING AS.

Where is LIA HOLDING AS based?

LIA HOLDING AS has its business address in Langangen.

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.