BIZTRAC BETA
Repair and maintenance of computers and communication equipment

EIKTEC AS

Org. no. 936704646 Limited company (AS) Øvre Eiker Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 25,000
Operating profit NOK 6,000
Equity NOK 29,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-12-02.

EIKTEC AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 936704646. The business is classified under repair and maintenance of computers and communication equipment (NACE 95.100). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Tilby tjenester innen elektronikk og data, reparasjon, gjenbruk, kjøp og salg og andre datarelaterte tjenester. Prosjekter med utvikling og formidling av kunnskap innen elektronikk og teknologi. Prosjekter og tjenester innen bedriftsservice.”. The most recent filed accounts, for the 2025 financial year, show NOK 25,000 in revenue and NOK 6,000 in operating profit.

Key figures · 2025

Revenue
NOK 25,000
Operating profit
NOK 6,000
Equity
NOK 29,000
Est. value
NOK 36,000

Financial health · 2025

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

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

Who owns EIKTEC AS?

RODRIGO CORTES
EIKTEC AS
NOK 25,000 rev. · NOK 6,000 profit

EIKTEC AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EIKTEC AS

Who owns EIKTEC AS?

RODRIGO CORTES is the largest registered owner, with 100.0%.

What is the revenue of EIKTEC AS?

EIKTEC AS had revenue of NOK 25,000 in 2025.

Where is EIKTEC AS based?

EIKTEC AS has its business address in Vestfossen.

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.