BIZTRAC BETA
Retail sale of other new goods

ENGLESHOP AS

Org. no. 929370112 Limited company (AS) Horten Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 111,000
Operating profit NOK −74,000
Equity NOK −454,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−454k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−74k kr).

ENGLESHOP AS is registered as a limited company in Horten, Vestfold with organisation number 929370112. The business is classified under retail sale of other new goods (NACE 47.780). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av interiørprodukter med engler, stener og kursvirksomhet på nett og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andres selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 111,000 in revenue and NOK −74,000 in operating profit.

Key figures · 2025

Revenue
NOK 111,000
Operating profit
NOK −74,000
Equity
NOK −454,000

Financial health · 2025

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

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

Who owns ENGLESHOP AS?

TERESE CARLEM JEGARD
ENGLESHOP AS
NOK 111,000 rev. · NOK −74,000 profit

ENGLESHOP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ENGLESHOP AS

Who owns ENGLESHOP AS?

TERESE CARLEM JEGARD is the largest registered owner, with 100.0%.

What is the revenue of ENGLESHOP AS?

ENGLESHOP AS had revenue of NOK 111,000 in 2025.

Where is ENGLESHOP AS based?

ENGLESHOP AS has its business address in Åsgårdstrand.

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.