BIZTRAC BETA
Rental and operating of own or leased real estate

LISTI HOLDING AS

Org. no. 912898016 Limited company (AS) Grimstad Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 15,000
Operating profit NOK −28,000
Equity NOK 12.9m
Incorporated 2013
Share capital NOK 107,000

Signals

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

LISTI HOLDING AS is registered as a limited company in Grimstad, Agder with organisation number 912898016. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 107,000, divided into 30000 shares. The company's stated purpose is: “Eierinteresser i andre selskaper, kjøp, eie og salg av eiendom, kjøp, eie og salg av verdipapir samt hva herved er beslektet.”. The most recent filed accounts, for the 2025 financial year, show NOK 15,000 in revenue and NOK −28,000 in operating profit.

Key figures · 2025

Revenue
NOK 15,000
Operating profit
NOK −28,000
Equity
NOK 12.9m
Est. value
NOK 10.1m

Financial health · 2025

Liquidity
1.02
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
78.8%
Very good
Equity as a share of total capital

Who owns LISTI HOLDING AS?

EGIL PEDERSEN
LISTI HOLDING AS
NOK 15,000 rev. · NOK −28,000 profit

LISTI HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LISTI HOLDING AS own?

LISTI HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LISTI HOLDING AS

Who owns LISTI HOLDING AS?

EGIL PEDERSEN is the largest registered owner, with 100.0%.

What is the revenue of LISTI HOLDING AS?

LISTI HOLDING AS had revenue of NOK 15,000 in 2025.

Where is LISTI HOLDING AS based?

LISTI HOLDING AS has its business address in Grimstad.

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.