BIZTRAC BETA
Retail sale of second-hand goods

LOPPO PORSGRUNN AS

Org. no. 835871142 Limited company (AS) Skien Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −11,000
Equity NOK 19,000
Incorporated 2025
Employees 7
Share capital NOK 30,000

Signals

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

LOPPO PORSGRUNN AS is registered as a limited company in Skien, Telemark with organisation number 835871142. The business is classified under retail sale of second-hand goods (NACE 47.790). The company was incorporated in 2025 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tilrettelegge for mer gjenbruk og sirkulær økonomi. Utleie av standplass for salg av hovedsakelig brukte klær, interiør, leker, sportsutstyr, møbler og lignende produkter som naturlig hører innunder.”.

Key figures · 2025

Operating profit
NOK −11,000
Equity
NOK 19,000
Est. value
NOK 24,000

Financial health · 2025

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

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

Who owns LOPPO PORSGRUNN AS?

LOPPO NORGE AS
LOPPO PORSGRUNN AS
· NOK −11,000 profit

LOPPO PORSGRUNN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LOPPO PORSGRUNN AS

Who owns LOPPO PORSGRUNN AS?

LOPPO NORGE AS is the largest registered owner, with 100.0%.

Who is the general manager of LOPPO PORSGRUNN AS?

Espen Furulund is registered as general manager of LOPPO PORSGRUNN AS.

Where is LOPPO PORSGRUNN AS based?

LOPPO PORSGRUNN AS has its business address in Skien.

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.