BIZTRAC BETA
Computer consultancy and computer facilities management activities

EPLECHECK AS

Org. no. 920332013 Limited company (AS) Drammen Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 280,000
Operating profit NOK −17,000
Equity NOK 32,000
Incorporated 2018
Share capital NOK 31,000

Signals

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

EPLECHECK AS is registered as a limited company in Drammen, Buskerud with organisation number 920332013. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2018. Registered share capital is NOK 31,000, divided into 31337 shares. The company's stated purpose is: “Kursvirksomhet samt yte konsulenttjenester og det som har tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 280,000 in revenue and NOK −17,000 in operating profit.

Key figures · 2024

Revenue
NOK 280,000
Operating profit
NOK −17,000
Equity
NOK 32,000
Est. value
NOK 529,000

Financial health · 2024

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

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

Who owns EPLECHECK AS?

TOMMY MIKALSEN
EPLECHECK AS
NOK 280,000 rev. · NOK −17,000 profit

EPLECHECK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about EPLECHECK AS

Who owns EPLECHECK AS?

TOMMY MIKALSEN is the largest registered owner, with 50.0%.

What is the revenue of EPLECHECK AS?

EPLECHECK AS had revenue of NOK 280,000 in 2024.

Who is the general manager of EPLECHECK AS?

Bjørn Djupvik is registered as general manager of EPLECHECK AS.

Where is EPLECHECK AS based?

EPLECHECK AS has its business address in Drammen.

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.