BIZTRAC BETA
Manufacture of corrugated paper, paperboard and containers of paper and paperboard

ESKER & STANSER AS

Org. no. 957946348 Limited company (AS) Stavanger Incorporated 1990 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK −166,000
Equity NOK 3,000
Incorporated 1990
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−166k kr).

ESKER & STANSER AS is registered as a limited company in Stavanger, Rogaland with organisation number 957946348. The business is classified under manufacture of corrugated paper, paperboard and containers of paper and paperboard (NACE 17.210). The company was incorporated in 1990. Registered share capital is NOK 100,000. The company's stated purpose is: “Eskeproduksjon.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK −166,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK −166,000
Equity
NOK 3,000
Est. value
NOK 649,000

Financial health · 2024

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

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

Who owns ESKER & STANSER AS?

JO LEIN
ESKER & STANSER AS
NOK 1.2m rev. · NOK −166,000 profit

ESKER & STANSER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ESKER & STANSER AS

Who owns ESKER & STANSER AS?

JO LEIN is the largest registered owner, with 100.0%.

What is the revenue of ESKER & STANSER AS?

ESKER & STANSER AS had revenue of NOK 1.2m in 2024.

Who is the general manager of ESKER & STANSER AS?

Jo Lein is registered as general manager of ESKER & STANSER AS.

Where is ESKER & STANSER AS based?

ESKER & STANSER AS has its business address in Hafrsfjord.

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.