BIZTRAC BETA
Wholesale of wood, construction materials and sanitary equipment

JEST HOLDING AS

Org. no. 815262972 Limited company (AS) Lier Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −15,000
Equity NOK 2,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−15k kr).

JEST HOLDING AS is registered as a limited company in Lier, Buskerud with organisation number 815262972. The business is classified under wholesale of wood, construction materials and sanitary equipment (NACE 46.830). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eie aksjer og andeler i andre selskaper samt andre investeringer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −15,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −15,000
Equity
NOK 2,000
Est. value
NOK 2,000

Financial health · 2025

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

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

Who owns JEST HOLDING AS?

JØRN EIRIK GUSTAVSEN
JEST HOLDING AS
NOK 0 rev. · NOK −15,000 profit

JEST HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JEST HOLDING AS own?

JEST HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JEST HOLDING AS

Who owns JEST HOLDING AS?

JØRN EIRIK GUSTAVSEN is the largest registered owner, with 100.0%.

What is the revenue of JEST HOLDING AS?

JEST HOLDING AS had revenue of NOK 0 in 2025.

Where is JEST HOLDING AS based?

JEST HOLDING AS has its business address in Gullaug.

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.