BIZTRAC BETA
Joinery installation

ELTEKA AS

Org. no. 917646716 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 257,000
Operating profit NOK 6,000
Equity NOK −86,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−86k kr).

ELTEKA AS is registered as a limited company in Oslo, Oslo with organisation number 917646716. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Yte tjenester innen elektriske ledninger installasjon, reparasjon herunder andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 257,000 in revenue and NOK 6,000 in operating profit.

Key figures · 2025

Revenue
NOK 257,000
Operating profit
NOK 6,000
Equity
NOK −86,000
Est. value
NOK 30,000

Financial health · 2025

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

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

Who owns ELTEKA AS?

JONAS VIRVILAS
ELTEKA AS
NOK 257,000 rev. · NOK 6,000 profit

ELTEKA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ELTEKA AS

Who owns ELTEKA AS?

JONAS VIRVILAS is the largest registered owner, with 100.0%.

What is the revenue of ELTEKA AS?

ELTEKA AS had revenue of NOK 257,000 in 2025.

Who is the general manager of ELTEKA AS?

Jonas Virvilas is registered as general manager of ELTEKA AS.

Where is ELTEKA AS based?

ELTEKA AS has its business address in Oslo.

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.