biztrac. BETA
COMPANY REGISTER PROFILE
820546512 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Other specialised construction activities n.e.c.

EF CLICK SYSTEM AS

Org. no. 820546512 Limited company (AS) Skien Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −94,000
Equity NOK 190,000
Incorporated 2018
Share capital NOK 35,000

Signals

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

EF CLICK SYSTEM AS is registered as a limited company in Skien, Telemark with organisation number 820546512. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2018. Registered share capital is NOK 35,000, divided into 1165 shares. The company's stated purpose is: “Produksjon og utvikling av armeringsprodukter samt beslektede produkter og legging av disse. Selskapet kan også yte konsulent og prosjekteringstjenester hovedsakelig innenfor segmentet for infrastruktur og bygg og anlegg. Selskapet kan også drive investering i, aktiv forvaltning av og salg av verdipapireier, eiendom og selskaper.”.

Key figures · 2025

Operating profit
NOK −94,000
▼ −67 %
Equity
NOK 190,000
▼ −33 %
Est. value
NOK 195,000

Financial health · 2025

Liquidity
0.99
Weak
Current assets ÷ current liabilities
Profitability
-11.1%
Not satisfactory
Return on total assets
Solidity
23.6%
Good
Equity as a share of total capital

Who owns EF CLICK SYSTEM AS?

EF CLICK SYSTEM AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about EF CLICK SYSTEM AS

Who owns EF CLICK SYSTEM AS?

BR UTVIKLING AS is the largest registered owner, with 28.3%.

Who is the general manager of EF CLICK SYSTEM AS?

Nils Petter Tornøe is registered as general manager of EF CLICK SYSTEM AS.

Where is EF CLICK SYSTEM AS based?

EF CLICK SYSTEM 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.