BIZTRAC BETA
Retail sale of clothing

EPLESKRINET AS

Org. no. 919060743 Limited company (AS) Kristiansand Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK −603,000
Equity NOK 377,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

EPLESKRINET AS is registered as a limited company in Kristiansand, Agder with organisation number 919060743. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av barneklær og sko, med fokus på netthandel, samt delta i andre liknende virksomheter, også investering i verdipapirer og eiendom. Selskapet kan også drive annen handel med andre typer varer.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK −603,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
Operating profit
NOK −603,000
Equity
NOK 377,000
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns EPLESKRINET AS?

EMKATT AS
EPLESKRINET AS
NOK 2.5m rev. · NOK −603,000 profit

EPLESKRINET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EPLESKRINET AS

Who owns EPLESKRINET AS?

EMKATT AS is the largest registered owner, with 100.0%.

What is the revenue of EPLESKRINET AS?

EPLESKRINET AS had revenue of NOK 2.5m in 2025.

Who is the general manager of EPLESKRINET AS?

Vibeke Hagerup Lærum is registered as general manager of EPLESKRINET AS.

Where is EPLESKRINET AS based?

EPLESKRINET AS has its business address in Kristiansand S.

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.